Collecting Requirement
Collect requirements * What is the common reason why projects fail?
If you take up a moment to Google up reasons for project failure, the common reason that you’d find in most of the results is lack of clarity in requirements.
Three out of five research findings have reasons related to requirements - * Unclear goals and objectives that change during the project * Incomplete requirements * Poor articulation of user requirements They all indicate the all-important step in ensuring success of a project – collecting the right requirements. * Inputs for Collect Requirements
At this stage of the project the documents already available are project charter and stakeholder register. And these two are the only inputs to this process.
Recall the contents of project charter. It contains, but not limited to, * short description of the project, * high level requirements * assigned project manager who is authorized to come up with budget, resource planning, decision on types of people based on skillset * milestones * ballpark budget figures * risks
The high level requirements are available at this stage to start collecting detailed requirements.
Next, you need to know whom to talk to and get detailed information about these high level requirements. And that information is available in Stakeholder register --This is a document that contains stakeholder information. * Tools and Techniques of Collect Requirements
Interviews
One on one
Focus group
Notice that there is only one odd color; he is the facilitator, while the blue ones are a group of employees (e.g. group of doctors, group of teachers, group of students, etc...)
Thus, focus group, focuses on one group to discuss different ideas from one group but different perspective.
Facilitated Workshop
Facilitated – Make easy
Workshop - Present a performance of work, using intensive group discussion and improvisation in order to explore aspects of a certain
If you take up a moment to Google up reasons for project failure, the common reason that you’d find in most of the results is lack of clarity in requirements.
Three out of five research findings have reasons related to requirements - * Unclear goals and objectives that change during the project * Incomplete requirements * Poor articulation of user requirements They all indicate the all-important step in ensuring success of a project – collecting the right requirements. * Inputs for Collect Requirements
At this stage of the project the documents already available are project charter and stakeholder register. And these two are the only inputs to this process.
Recall the contents of project charter. It contains, but not limited to, * short description of the project, * high level requirements * assigned project manager who is authorized to come up with budget, resource planning, decision on types of people based on skillset * milestones * ballpark budget figures * risks
The high level requirements are available at this stage to start collecting detailed requirements.
Next, you need to know whom to talk to and get detailed information about these high level requirements. And that information is available in Stakeholder register --This is a document that contains stakeholder information. * Tools and Techniques of Collect Requirements
Interviews
One on one
Focus group
Notice that there is only one odd color; he is the facilitator, while the blue ones are a group of employees (e.g. group of doctors, group of teachers, group of students, etc...)
Thus, focus group, focuses on one group to discuss different ideas from one group but different perspective.
Facilitated Workshop
Facilitated – Make easy
Workshop - Present a performance of work, using intensive group discussion and improvisation in order to explore aspects of a certain