Re: [AM] Why Traceability?

Paul Oldfield wrote:

> There seemed to be some consensus reached that 
> traceability is a solution to a problem, one that may no
> longer hold true (as in no longer the best solution) in an 
> agile environment.

I spoke with an agile devotee recently who had been talking with 
a bunch of CMM assessors.  He was expecting a serious culture 
clash: he would want minimum documentation, they would want the 
maximum.  My friend was truly surprised at these assessors 
reaction.  They liked agile processes with automated tests!  Why? 
  Because traceability was easy.  The link between the 
requirement - specified as an executable test - and the code - 
again in an executable form - was utterly straightforward.  In a 
traditional waterfall approach, the path between a written 
requirement, via analysis, design and coding, to a test is a lot 
longer and there are many more opportunities to drop the shopping.

Not the reaction I expected from them, but it's reassuring that 
they just want to get the job done and get good software out there.

-- 
Hubert Matthews         http://www.oxyware.com/
Software Consultant     [email protected]

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
--^----------------------------------------------------------------