Top down decomposition and validation. Bottom up verification. Saving Changes...
Gordon AlexanderSenior Principal - Global Programme Director| IndepndentChelmsford, Essex, United Kingdom
As Tamar said the requirements traceability matrix is the best way to manage the requirements from concept to completion. This should contain the original requirements, signed off by the users business and the project team acceptance.
Every change whether it is a removal of a requirement, an addition or an amendment needs to be logged with who raised the change, who approved it (business, IT, Products etc.) and when it was communicated to the team. This document in particular the change sheet should be used at regular business/stakeholder updates with the impact of the change in timescale/cost etc. With this in mind, that each change will have an impact whether positive or negative, it is important that these are communicated to everyone, just as per a normal project change mechanism.
A piece of advice from experience, always have an approver who is not the person who raised the change even if its the sponsor and he tells you he can approve it.
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
The question of tools drives me to think in terms of JIRA . It's a good tool to manage not only your requirements , but also manage and run your sprints and iterations.
JIRA lets your product owner sign off on the user stories and provides traceability of your requirements/user stories. Saving Changes...
