What is the best Tool and Technique to collect requirements? Saving Changes...
Sort By:
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Shadav, think there is no 'best' tool for anything, it always depends on the specific project situation. The PMBoK lists 8 tools&techniques for collecting requirements, you may use one or more. A basic understanding is that each requirement comes from a stakeholder, so it is important to identify stakeholders first. Some requirements may change over time, even become obsolete, some may only be discovered during the project, so it is important to track them. Not all requirements can be fulfilled, some will contradict each other, there may be too many - so the project manager has to consider all and create a scope statement that describes which requirements will be fulfilled, and which not (out of scope). Key stakeholders will influence the priorities, e.g. in Scrum that is the product owner. Some stakeholders will complain, but better at this stage than at the end of the project. What the project manager defines as scope (= the project promise) depends on the balance of schedule and cost. BTW - this is also true in agile projects, the difference is how much change to the requirements you can handle. Saving Changes...
As I and others have stated hundreds of times before in this forum, there is no such thing as a "best" practice, tool or technique. There might be such a thing as a best practice or tool for a given context, but as soon as that context changes, that practice or tool is likely no longer the best.
Principles are evergreen, practices and tools are fleeting.
Kiron
...
1 reply by Abolfazl Yousefi Darestani
Mar 11, 2019 8:17 AM
Abolfazl Yousefi Darestani
...
Kiron,
There are some best "practices". You probably mean the best tool or technique. I totally agree with you that there is no "best technique/tool" for all type of projects and/or situation. However, best practice means a little bit different as you know.
As I and others have stated hundreds of times before in this forum, there is no such thing as a "best" practice, tool or technique. There might be such a thing as a best practice or tool for a given context, but as soon as that context changes, that practice or tool is likely no longer the best.
Principles are evergreen, practices and tools are fleeting.
Kiron
Kiron,
There are some best "practices". You probably mean the best tool or technique. I totally agree with you that there is no "best technique/tool" for all type of projects and/or situation. However, best practice means a little bit different as you know. Saving Changes...
I have used the IBM DOORs program in the past. I liked the fact that we were able to link and track all changes from our business requirements, high-level mandatory requirements, statement of requirements, statement of work, and contract. Access and changes are all tracked by individual, date, etc. Saving Changes...
