I recently came across a project working Agile with Rational Team Concert (RTC). This is great, they have all the tracking tools they need to monitor project velocity, and to manage which stories will go into which sprint. Job done. Short blog entry here…
Oh, just one thing. Who is ever in a project that couldn’t be working just a little better. Best practice, whatever that may mean, is too often an unachievable leap away for many reasons. Better practice is very often within the grasp of the project.
Agile stories were well documented, some better than others, but in general they fairly good, clear, understandable. The only problem is that they are in the description field of an RTC work item. This means that requirements cannot be referenced individually, and finding a single requirement can be a challenge. RTC, after all, is not a requirements management tool. I have proposed a step forward, towards best practice. Mid way through a project is not the time to leap to a different tool solution, but better practice can be achieved with little disruption. This step is one to a state of better practice. It is also a viable option for a new project starting out. Best practice, state of the art, is not what is required on all projects, and for many Agile IT projects, the rigor demanded of large defence project best practice is not only unnecessary, it can be positively harmful.
There is value to be gained from moving towards DOORS Next Generation (DNG), with a lightweight approach, the value gained should far outweigh the investment. Value comes in the forms of searchability, traceability and analysability.
My proposal is as follows:
Continue reading »