SAB5#38_Collect_Requirements

SAB5#38_Collect_Requirements

1. Stakeholders Management Plan

2. Requirements Management Plan

3. Stakeholders Register

4. Scope Management Plan

5. Project Charter

6. Reviewing Historical records

   • Historical records and lessons learned  can indicate what  the requirements were on similar projects and help identify relevant process and expectation 

7. Interview

   • This technique may also be referred to as "expert interviews" on the exam. The team or project manager interviews project stakeholders to elicit their requirements. Interviews can also be conducted via e-mal, phone calls or virtual collaboration tools.

8. Focus group

   • This technique helps get a specific set of stakeholders or subject matter experts opinions and requirements for the product or an aspect of the project. They can discuss their ideas with each other, and the conversation is directed by a moderator.

9. Facilitated Workshops

   • This technique bring together stakeholders with different perspectives (e.g. product designer, end users) to talk about the product and, ultimately, define requirements.

10. Brainstorming

    • The purpose of brainstorming is to encourage participants to build on each other´s ideas. After all the ideas have been captured, the group can evaluate and rank them through the nominal group technique or multi-criteria decision analysis.

11. Nominal group technique

    • The meeting participants rank the most useful ideas generated during the brainstorming session.

12. Mind Maps

    • A mind map is a diagram of ideas or notes to help generate, classify or record information.

13. Multi-criteria Decision Analysis

    • Stakeholders quantify requirements using a decision matrix base on factors such as expected risk levels, time estimates, and cost and benefit estimates.

14. Affinity diagrams

    • In this technique, the ideas generated from any other requirements-gathering techniques are grouped by similarities or categories. This sorting makes it easier to see additional areas of scope (or risk) tht have not been identified.

15. Questionnaires and surveys

    • Typically used for large groups. The questions are asked in such a way as to elicit requirements from the respondents.

16. Observation

    • This technique involves job shadowing-watching a potential user of the product at work and, in some cases, participanting in the work to help identify requirements.

17. Prototypes

    • Is a model of the product. The prototype may be updated multiple times to incorporate the feedback until the requirements have been solidified for the product.

18. Benchmarking

    • Look at what the competition is doing. Benchmarking can be very time-consuming and costly. It  may alsoinhibit the team´s creativity.

19. Context diagrams

    • It shows the boundaries of the product scope by highlighting the product and its interfaces with people, process or systems.

20. Group decision making

    • Soliciting input on requirements from different stakeholders often result in conflicting requirements. It´s essencial to resolve these conflicts and review, analyze, accept or reject, and prioritize requirements before recording them in project documents.

21. Delphi technique

    • A request for information is sent to experts who participate anonymously. Their responses are compiled, and the results are sent back to the experts for further reviews until they reach agreement.
    • MUY IMPORTANTE: Recaba propuestas de los Subject Matter Expert (Expertos en la materia) . Mejor TECNICA para lograr un concenso.

22. Requirements documentation

    • The requirements are clear and unambiguous. The requirements documentation can contain various types of information, the acceptance criteria are the most important.

23. Resolving Competing Requirements

    • You should help resolve competing requirements by accepting those that best comply with following: The business case, the project charter, the project scope statement, the project constraints.

24. Requirements Traceability Matrix

    • This helps link the requirements to the objectives and/or other requirements to ensure the strategic goals are accomplished. The matrix is used throughout the project in analyzing proposed changes to the project or product scope. Each requirement is assigned to someone to manage.

25. Balancing Stakeholders' requirements

    • Make sure the requirements can be met within the project objectives. If they cannot, then you need to look for options to adjust the competing demands of scope, time, cost, quality, resources, risk and customer satisfaction.

26. Process group: Planning Knowledge Area: Scope Management

27. This is the process of defining and documenting, and managing stakeholders needs and requirements to meet the project objetives.

Images and files in the map