RE: [AM] Why Traceability?
Tina Erwee <[email protected]> Tue, 16 Mar 2004 14:49:42 +0200
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
Traceability for sake of getting paid - best reason there is. BTW How did this affect an agile approach? How detailed were the requirements? > -----Original Message----- > From: Ashley McNeile [mailto:[email protected]] > Sent: 16 March 2004 14:41 > To: [email protected] > Subject: Re: [AM] Why Traceability? > > > > Any idea what it's actually supposed to achieve, though? > > Recently I was doing some work at a government department, where the > delivery of IT solutions is often undertaken by external suppliers. > Contracts with a solution supplier are sometimes fixed-price > and scoped by a > requirements specification. Testing is used to verify delivery against > contract, and traceability between the requirements in the > contract and the > tests performed is the basis for determining the extent of > compliance (and > therefore whether/how much the supplier gets paid). > > Rgds > Ashley > > For more information about AM, visit the Agile Modeling Home > Page at www.agilemodeling.com > > > > For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h Or send an email to: [email protected] For Topica's complete suite of email marketing solutions visit: http://www.topica.com/?p=TEXFOOTER --^----------------------------------------------------------------