Agile and Requirement Traceability
If you had the chance of working in an organization which has received SEI-CMMi certification then you would definitely be familiar with the concept of:
- Requirement Baselining
- Requirement Traceability Matrix (RTM)
If you are not familiar with these terms then the best place to look is Wikipedia.
Basically, the idea is to clearly write down what the software should do and freeze it. This process is called baselining. Then you create a matrix (RTM) which indicates how each individual requirement is addressed in the design document and then in the code.
Requirements Management (REQM) – A Process Area in CMMi Level 2
As you are aware that CMMi has five levels of maturity, 5 being the most mature. Requirement management is fundamental to CMMi as you need to master it even to achieve a maturity level of 2. RTM is an integral part of REQM.
So, if you are trying to use agile in such an organization, how would you do it?
The user stories can be treated as requirement but would you freeze it, version it and formally track the changes?
Would you be able to create an RTM without losing agility?