Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
The project success directly influenced by active stakeholder involvement in the discovery and decomposition of needs into requirements and by the care taken in determining, documenting, and managing the requirements of the product, service or results of the project. Requirements include conditions or capabilities that are to be met by the project or present in the product, service or result to satisfy an agreement or other formally imposed specification. Requirements become the foundation of the WBS, cost, schedule, quality planning and sometimes procurement are all based upon these requirements. The development of requirements begins with an analysis of the information contained in the project charter, the stakeholder register and stakeholder management plan.
Inputs
1) Scope management plan: provides clarity as to how project teams will determine which type of requirements need to be collected for the project.
2)Requirements management plan: provides the processes that will be used throughout the Collect Requirement process to define and document the stakeholder needs.
3)Stakeholder management plan: used to understand stakeholder communication requirements and the level of stakeholder engagement in order to assess and adapt to the level of stakeholder participation in requirement activities.
4) Project charter: used to provide the high level description of the product, service, or result of the project so that detailed requirements can be developed.
Tools & Techniques
1) Interview: Talking to stakeholders directly, typically performed by asking prepared and spontaneous questions and recording the responses.
2) Focus groups: trained moderator guides the group through an interactive discussion, designed to be more conversational than a one-to-one interview.
3) Facilitated workshop: focused sessions that bring key stakeholders together to define product requirements. Workshops are considered a primary technique for quickly defining cross-functional requirements and reconciling stakeholder differences. Because of their interactive group nature, well facilitated sessions can build trust, foster relationships, and improve communication among the participants, which can lead to increased stakeholder consensus. In addition issues can be discovered earlier and resolved more quickly than in individual sessions.
Joint application development (JAD)
- used in software development industry
- focus on bringing business subject matter experts and the development team together to improve software development process
Quality function deployment (QFD)
- helps determine critical characteristics for new product development
- starts by collection customer needs, also known as Voice of the Customer (VoC)
- collected needs are then objectively sorted and prioritized
4) Group creativity techniques: group activities can be organized to identify project and product requirements.
- Brainstorming - used to generate and collect multiple ideas, not include voting or prioritization.
- Nominal group technique - enhances brainstorming with a voting process used to rank most useful ideas
- Idea/mind mapping - ideas created through brainstorming are consolidated in a single map to reflect commonality and differences
- Affinity diagram - large numbers of ideas to be classified into groups for review and analysis
- Multicriteria decision analysis - utilizes a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas
5) Group decision making techniques: can be used to generate, classify and prioritize product requirements
- Unanimity - everyone agrees on a single course of action, one way to reach unanimity is the Delphi technique.
- Majority - more than 50%
- Plurality - largest block in a group decides, even if a majority is not achieved
- Dictatorship - one individual makes the decision
The experts answer questionnaires in two or more rounds. After each round, a facilitator provides an anonymous summary of the experts’ forecasts from the previous round as well as the reasons they provided for their judgments. Thus, experts are encouraged to revise their earlier answers in light of the replies of other members of their panel. It is believed that during this process the range of the answers will decrease and the group will converge towards the "correct" answer. Finally, the process is stopped after a pre-defined stop criterion.
(keywords: experts, questionnaire, anonymous)
6) Questionnaires and surveys: written set of questions designed to quickly accumulate information from large number of respondents, appropriate with varied audiences, when respondents are geographically dispersed and where statistical analysis is appropriate.
8) Prototypes: obtains early feedback on requirements by providing a working model of the expected product before actually building it. allows stakeholders to experiment with a model of the final product rather than being limited to discussing abstract representations of their requirements.
Outputs
1) Requirements documentation: describes how individual requirements meet the business need for the project. Requirements may start out at a high level and become progressively more detailed as more about the requirements is known.
2) Requirements traceability matrix: a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a meas to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. Finally it provides a structure for managing changes to the product scope.
Tracing includes Business needs, goals, objectives, project scope/WBS deliverables, etc.
댓글 없음:
댓글 쓰기