5.1 Collect Requirements

 

Back to Process Group Mappings
5.1. Collect Requirements The process of defining and documenting the stakeholder needs to meet the project objectives   Simple Version: Collect the list of things to do before the project can be deemed done.
PMI	Agile PMBOK, Agile Difference, Comment
Inputs Project charter Stakeholder register   Tools and Techniques Interviews Focus groups Facilitated workshops Group creativity techniques Group decision making techniques Questionnaire and surveys Observations Prototypes   Outputs Requirements documentation Requirements management plan Requirements traceability matrix	Inputs Project charter Stakeholder register   Tools and Techniques Interviews Focus groups Facilitated workshops / JADs Group creativity techniques Group decision making techniques Questionnaire and surveys Observations Prototypes   Outputs Requirements documentation Candidate Story List / Epics Requirements management plan Requirements traceability matrix   There can sometimes be a disconnect here between agile and traditional approaches, but it can be avoided. Agile projects recognize that it is unlikely to be possible to gather all the requirements accurately up front. Instead it is more likely that the true requirements will evolve over the course of the project as functionality is built and evaluated by the business. So, while it is appropriate to gather requirements early in the project, do not assume that this will be the end of the process, perhaps 50-70% of the requirements can be determined up front, the remainder will evolve and be uncovered throughout the project.