โ† All CPRE Flashcard Decks

Requirements Elicitation & Stakeholder Analysis Flashcards

9 cards from real CPRE practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 9 Requirements Elicitation & Stakeholder Analysis flashcards as text
  1. What is the main purpose of requirements elicitation?

    Answer: To gather and define stakeholder needs and constraints

    The main purpose of requirements elicitation is to gather and define stakeholder needs and constraints. This process involves discovering, reviewing, and understanding what users and other stakeholders expect from a system or product. It's a crucial foundational step to ensure that all relevant information is collected to accurately define the scope and functionalities of the solution.

  2. Which technique is commonly used in stakeholder analysis?

    Answer: Power-interest grids

    Power-interest grids are a commonly used technique in stakeholder analysis. This method categorizes stakeholders based on their level of power (influence) and interest in a project, helping to determine appropriate engagement strategies. By mapping stakeholders on this grid, project teams can effectively prioritize communication and management efforts to ensure project success.

  3. Why is it important to involve stakeholders early in the requirements process?

    Answer: To ensure accurate and complete requirements from the beginning

    Involving stakeholders early in the requirements process is crucial to ensure accurate and complete requirements from the beginning. Stakeholders are the primary source of information regarding their needs, expectations, and constraints. Early engagement helps to prevent misunderstandings, reduces the likelihood of costly rework, and fosters a shared understanding of the project goals, leading to a more successful outcome.

  4. Which method is suitable for eliciting requirements from a large user group?

    Answer: Surveys and questionnaires

    Surveys and questionnaires are highly suitable for eliciting requirements from a large user group. They allow for efficient collection of input from many individuals simultaneously, making them scalable compared to one-on-one methods like interviews. This approach helps in identifying common needs, preferences, and pain points across a broad audience, providing valuable data for requirements definition.

  5. What is a key challenge in stakeholder analysis?

    Answer: Identifying all relevant stakeholders, especially hidden ones

    A key challenge in stakeholder analysis is identifying all relevant stakeholders, especially hidden ones who may not be immediately obvious but still have an interest or influence. Overlooking critical stakeholders can lead to incomplete requirements, resistance, or project failure due to unmet expectations or unaddressed concerns. Thorough analysis is essential to uncover these individuals and understand their potential impact.

  6. Which of the following is a benefit of using workshops for requirements elicitation?

    Answer: They help build consensus and shared understanding

    A significant benefit of using workshops for requirements elicitation is that they help build consensus and shared understanding among stakeholders. By bringing diverse participants together in a focused, interactive environment, workshops facilitate direct communication and allow for immediate clarification of ideas. This collaborative setting helps resolve conflicting requirements in real-time, leading to stronger agreement on project goals.

  7. What is the role of a requirements engineer in stakeholder communication?

    Answer: To facilitate clear and structured communication with stakeholders

    The role of a requirements engineer in stakeholder communication is to facilitate clear and structured communication with stakeholders. They act as a crucial bridge between business needs and technical implementation, ensuring that information is accurately conveyed and understood by all parties. This involves actively listening, asking clarifying questions, and translating complex requirements into understandable terms, minimizing misunderstandings and aligning expectations.

  8. Why is prioritization of requirements important?

    Answer: To focus on high-value requirements first

    Prioritization of requirements is important to focus on high-value requirements first. Projects often have limited resources and time, making it essential to identify and address the most critical and impactful features early in the development cycle. This strategic approach helps manage scope, mitigate risks, and ensures that the most significant business value is delivered promptly, especially in iterative development methodologies.

  9. Which tool supports tracking stakeholder influence and interest?

    Answer: Stakeholder matrix

    A stakeholder matrix is a key tool that supports tracking stakeholder influence and interest. This matrix helps project managers and requirements engineers systematically categorize stakeholders based on their power, interest, and potential impact on the project. By using this tool, teams can develop tailored communication and engagement strategies, ensuring appropriate attention is given to those who can most affect the project's success.