Comments on: Traceability Matrix and Agile http://jrothman.com/blog/mpd/2008/07/traceability-matrix-and-agile.html Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk. Sat, 22 Nov 2008 02:07:01 +0000 http://wordpress.org/?v=2.6.1 By: Serhiy Yevtushenko http://jrothman.com/blog/mpd/2008/07/traceability-matrix-and-agile.html#comment-15873 Serhiy Yevtushenko Tue, 15 Jul 2008 07:32:18 +0000 http://jrothman.com/blog/mpd/?p=8462#comment-15873 I would like to mention other possibilities to add tracability to the agile projects: 1) Acceptance tests (And tools like FIT & Fitnesse). If you specify acceptance test for each stories, then it allows you to organize development around them, and supply requirements with acceptance tests. Also, agile development allows for reverse traceability - remove some part of code, and run all the tests. The tests that fail are affected by the code, which was removed. 2) Adding Issue-Tracking IDS to submits - allows you (with some tweaking& scripting of issue-tracking system) to see all submits, related to the issue (story) There are some tools and plugins to the issue-tracking systems, which allow you to see all the changes to codebase, related to the particular issue. I would like to mention other possibilities to add tracability to the agile projects:
1) Acceptance tests (And tools like FIT & Fitnesse). If you specify acceptance test for each stories, then it allows you to organize development around them, and supply requirements with acceptance tests.

Also, agile development allows for reverse traceability - remove some part of code, and run all the tests.
The tests that fail are affected by the code, which was removed.

2) Adding Issue-Tracking IDS to submits - allows you (with some tweaking& scripting of issue-tracking system) to see all submits, related to the issue (story)
There are some tools and plugins to the issue-tracking systems, which allow you to see all the changes to codebase, related to the particular issue.

]]> By: Dwayne Phillips http://jrothman.com/blog/mpd/2008/07/traceability-matrix-and-agile.html#comment-15720 Dwayne Phillips Mon, 14 Jul 2008 15:12:31 +0000 http://jrothman.com/blog/mpd/?p=8462#comment-15720 I am happy to see someone address systems engineering concepts such as traceability in the agile model. Of course you can trace in agile. It is one of those things that you just do. The choice of tool depends on the size and complexity of the project and product. I am happy to see someone address systems engineering concepts such as traceability in the agile model. Of course you can trace in agile. It is one of those things that you just do. The choice of tool depends on the size and complexity of the project and product.

]]> By: Bob http://jrothman.com/blog/mpd/2008/07/traceability-matrix-and-agile.html#comment-15661 Bob Mon, 14 Jul 2008 02:38:35 +0000 http://jrothman.com/blog/mpd/?p=8462#comment-15661 In a regulated environment "lightweight" Agile is probably not sufficient. There are more issues than just finding the right tool. This is an interesting topic within medical device software development that I've discussed in the past. <a href="http://rdn-consulting.com/blog/2007/07/22/agile-development-in-a-fda-regulated-setting/" rel="nofollow">Agile development in a FDA regulated setting</a> In a regulated environment “lightweight” Agile is probably not sufficient. There are more issues than just finding the right tool. This is an interesting topic within medical device software development that I’ve discussed in the past.

Agile development in a FDA regulated setting

]]> By: Carlton Nettleton http://jrothman.com/blog/mpd/2008/07/traceability-matrix-and-agile.html#comment-15358 Carlton Nettleton Fri, 11 Jul 2008 17:29:47 +0000 http://jrothman.com/blog/mpd/?p=8462#comment-15358 Not to "rain on your parade", but I have yet to see an organization who is really concerned about traceability (government or regulated industries) ever adopt this lightweight tactic. You have GOT to have a tool, or that is what they claim. Given that, what would you say is the "root cause" we could address in these environments that would help us get to something more lightweight? Not to “rain on your parade”, but I have yet to see an organization who is really concerned about traceability (government or regulated industries) ever adopt this lightweight tactic. You have GOT to have a tool, or that is what they claim.

Given that, what would you say is the “root cause” we could address in these environments that would help us get to something more lightweight?

]]>