Re: Test driven development?
From: Guy Macon (http://www.guymacon.com)
Date: 08/17/04
- Next message: Unbeliever: "Re: Logic Analyzer Recommendations?"
- Previous message: Paul Carpenter: "Re: Embedded OSD (Not STV5370A)"
- In reply to: Doug Dotson: "Re: Test driven development?"
- Next in thread: Scott Moore: "Re: Test driven development?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 17 Aug 2004 02:14:30 -0700
Doug Dotson <dougdotson@NOSPAMcablespeed.NOSPAMcom> says...
>
>"Mike Turco" <miketurco@yahoo-nospam4me.com> wrote...
>
>> Requirements need to be made clear up front.
>
>This never happens. Requirements change, thus the failure of the
>Waterfall approach to project management. Project management
>must be able to adapt to changing requirements.
It is the responsibility of the project manager to tell the people
who are changing the requirwements how much money and time doing
so will cost, and to reject the proposed requirements change unless
they sign off in writing that they accept the additional time/money
costs.
- Next message: Unbeliever: "Re: Logic Analyzer Recommendations?"
- Previous message: Paul Carpenter: "Re: Embedded OSD (Not STV5370A)"
- In reply to: Doug Dotson: "Re: Test driven development?"
- Next in thread: Scott Moore: "Re: Test driven development?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|