Requirements (and attendant changes) may come from numerous sources over the course of a project's life. What tools (technology or otherwise) do you find most helpful in gathering and managing project requirements? How do you avoid overlooking obscure sources and what rules are in place to ensure that all stakeholders understand what constitutes a formal requirement and what does not? Saving Changes...
Sort By:
Basit HabibProgram Manager| Basma Consultancy LimitedManchester, United Kingdom
I would be interested to know if there is any good tool available to have an effective Scope Management and RTM.
I mainly use excel to capture and monitor requirements to closure of the project, happy to share couple of templates I used in past projects if thats of any help. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I will write something obvious but I must do that: process is first. And process will impact in your whole organization at all enteprise architecture level. With focus on process you can determine the tool. Any tool could help you. For example, in my actual work, we use Microsoft Excel. And it works. Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Brainstorming is one of the simplest and useful tools for Requirements Gathering .
Have butcher's paper and a whiteboard marker and invite all your major stakeholders to the workshop (assuming that according to PMBOK you have already identified your stakeholders during the initiation phase and you are now in the Scoping phase)
Encourage active participation and make sure there is some sugar (cakes, pastries) to get the creative juices flowing.
There is a great possibility that one or more of the stakeholders may point you to their Subject Matter Experts who you can use to further refine the requirements. Saving Changes...
Keith, I think the answers to your questions will change relative to the project's size, scope and objective.
Requirement gathering for a business transformation initiative is different than how a construction project would get its requirements defined.
The same is true for stakeholder understanding of formal (and informal) requirements; it will depend on the nature of the project, the roles the stakeholders are playing and the org environment everything is happening in.
If you could provide a project example, I'm sure the community can give you some specific recommendations. Saving Changes...
S RajasekarSenior Project Manager| AllscriptsBangalore, Karnataka, India
1.Confluence is the best tool for requirements management
2. FreeMind / Mindmanager...
3. SharePoint/wiki
4.Word documents...
These are some of the common tools used for requirements management Saving Changes...
