Re your first point, I have worked in development for many years and the only reason I’ve ever had to do this is to argue with people about why we’re late. In agile development, the key stakeholders (especially the product owner) should have been involved throughout, so this risk is mitigated. In my experience of agile, I don’t think I’ve seen this need once as a result.

If any requirements are defered for a later release, they can simply be captured on the product backlog and a new user story written nearer the time of development.

It’s a very interesting point though. Has anyone else got a view on this?

Kelly.

First, when requirements keep getting modified due to iterative method of development, one may need to see how the final requirement has shaped up as compared to the initial one.

Secondly, as time and cost are fixed, some of the requirements may be differred for a later release.

Thanks.

You say “it’s important to track the requirements” – why is that?

Kelly.