Re: [AM] Why Traceability?

[email protected] wrote:

<snip />

> In the end, our client won a settlement, and we got a bonus, as well as 
> a long-term client. The real bonus was about six additional jobs because 
> our client told just about everyone about his "great new system".
>  
> That's the only time I've ever been required to provide that kind of 
> traceability. 

That's a neat story, Pete. It ought to be an article somewhere.

People tell me I'm too simplistic and not realistic, but I have observed 
that the primary need for traceability is to point the finger at 
someone, often in a court of law. Why, then, do I not need traceability?

Simple: I don't blame people and I stay out of court.

Now some will say, "That's not feasible where I live," and I have no 
choice but to believe them. That's why I don't live there with them. 
Those are places that don't meet the organizational requirements to be 
Agile. (They may be somewhat agile, but they probably can't be Agile.)

No harm done. Not everyone has to be Agile. I just want to be.
-- 
J. B. Rainsberger,
Diaspar Software Services
http://www.diasparsoftware.com :: +1 416 791-8603
Let's write software that people understand

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