RE: [AM] Why Traceability?

I was at a talk a few months ago where Ken Schwaber gave a quick
introduction to Scrum and its place in the Agile universe. I remember him
mentioning that Scrum was CMM level 2 and 3 compliant but now that I know a
little more about CMM, I'm having difficultly understanding how an Agile
process can be CMM compliant without losing its agility.

My difficulty arises from CMM's "Maintain Bidirectional Traceability of
Requirements" specific practice. As far as I can tell, you can't achieve
universal traceability without heavy documentation or tools, both of which
are discouraged in Agile processes. Automated tests (JUnit, NUnit, etc.)
certainly help agility and give great traceability but they aren't
appropriate (AFAIK) for testing user interfaces so user interface
requirements must be traced some other way, which brings us back to
documentation or tools.

How do people satisfy CMM's need for Bidirectional Traceability without
being crushed by documents or distracted by tools?

John Manuel

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