Hi all,
I was wondering... through the requirements gathering process, many documents are produced and then refined and new versions produced.
What system do you use to make sure all stakeholders are working with the latest version? Do misunderstandings happen because docs get mixed up? Tell me your stories!
In a perfect world you would generate baselined documents from an entrerprise repository of requirements so they would always be up to date. We don't live in that world so you can employ a versioning system that keeps track of changes but at no time should a document be released until it is baselined and then clearly labeled with the baselined version so it is clear what version of the requirements are being used.
Depending on what tools are available given the client I am working with:
In general anything with version control that all required stakeholders have access to.
Hi Fred,
Want to know how do we anwer below question in interview?
How do you manage requirements change?
Thanks.
Someone has to break the tie. If you have conflicts you can't do development of that part. That is part of the job. You list the conflicts as a risk to the project if they cannot agree. Under no circumstanses should you consider the requirements final for that part (release to code) until the conflict is resolved.
brought to you by enabling practitioners & organizations to achieve their goals using: