Scenario practice questions

In a daily standup, a developer mentions that a task is taking longer than expected due to an unfamiliar technology. The sprint goal may be at risk. As a Scrum Master, what should you do FIRST?

Trap 1: Assign the task to a more experienced developer

In Scrum, the Development Team is self-organizing and self-managing, meaning they collectively decide how to best accomplish the work. A Scrum Master's role is to facilitate, not dictate. Directly reassigning a task undermines the team's autonomy and their ability to collaboratively solve problems, which is crucial for fostering collective ownership and continuous improvement. This action bypasses the team's problem-solving capacity and the opportunity for internal knowledge transfer.

Trap 2: Escalate to the product owner to descope the task

Escalating to the Product Owner to descope the task is premature and misaligns with the Scrum Master's primary responsibility. The Scrum Master's role is to facilitate impediment removal, starting by empowering the Development Team to find solutions internally or by directly assisting them. Descoping is a last resort, typically considered after the team and Scrum Master have exhausted internal options, as it directly impacts the sprint goal and product value.

Trap 3: Add the issue to the risk register for future sprints

An issue actively impacting a task in the current sprint is an immediate impediment, not merely a future risk to be documented. The Scrum Guide mandates that the Scrum Master ensures impediments to the Development Team are removed as soon as possible to maintain flow and achieve the Sprint Goal. Adding it to a risk register for future consideration defers resolution and fails to address the current disruption, which is critical in agile frameworks.

A
Assign the task to a more experienced developer
Why wrong: In Scrum, the Development Team is self-organizing and self-managing, meaning they collectively decide how to best accomplish the work. A Scrum Master's role is to facilitate, not dictate. Directly reassigning a task undermines the team's autonomy and their ability to collaboratively solve problems, which is crucial for fostering collective ownership and continuous improvement. This action bypasses the team's problem-solving capacity and the opportunity for internal knowledge transfer.
B
Escalate to the product owner to descope the task
Why wrong: Escalating to the Product Owner to descope the task is premature and misaligns with the Scrum Master's primary responsibility. The Scrum Master's role is to facilitate impediment removal, starting by empowering the Development Team to find solutions internally or by directly assisting them. Descoping is a last resort, typically considered after the team and Scrum Master have exhausted internal options, as it directly impacts the sprint goal and product value.
C
Work with the developer and team to find a solution or pair with an expert
This option directly aligns with the Scrum Master's core responsibility as a servant-leader and impediment remover. By working collaboratively with the developer and the entire Development Team, the Scrum Master facilitates problem-solving and knowledge sharing. Suggesting pairing with an expert within the team is an excellent strategy for immediate skill transfer and resolving the impediment efficiently, empowering the team to overcome challenges collectively.
D
Add the issue to the risk register for future sprints
Why wrong: An issue actively impacting a task in the current sprint is an immediate impediment, not merely a future risk to be documented. The Scrum Guide mandates that the Scrum Master ensures impediments to the Development Team are removed as soon as possible to maintain flow and achieve the Sprint Goal. Adding it to a risk register for future consideration defers resolution and fails to address the current disruption, which is critical in agile frameworks.

Question 2mediummultiple choice

A project team is implementing a new software feature. During testing, a critical defect is found that could delay the release. The project manager needs to determine the root cause. Which tool or technique should be used?

Trap 1: Scatter diagram

A scatter diagram plots pairs of numerical data to determine if a correlation or relationship exists between two different variables, such as project cost and schedule deviation. While it can indicate the strength and direction of a relationship, it does not systematically break down a problem into its potential causal factors or identify the underlying reasons for a defect. Its primary utility is for correlation analysis, not for dissecting a problem to find its root cause.

Trap 2: Control chart

Control charts are statistical process control tools used to determine if a process is stable and in statistical control by monitoring performance over time against established upper and and lower control limits. They help identify out-of-control points or trends, signaling when a process needs investigation due to abnormal variation. However, a control chart itself does not perform the root cause analysis; it merely indicates when such an analysis might be necessary.

Trap 3: Delphi technique

The Delphi technique is a structured communication method used to obtain consensus from a panel of experts on a specific topic through a series of anonymous questionnaires and feedback rounds. While valuable for forecasting, risk identification, or decision-making where expert opinion is crucial, it is a group facilitation technique for opinion gathering, not a direct analytical tool for systematically dissecting a problem to identify its underlying causes. It relies on subjective expert judgment rather than objective causal analysis.

A
Scatter diagram
Why wrong: A scatter diagram plots pairs of numerical data to determine if a correlation or relationship exists between two different variables, such as project cost and schedule deviation. While it can indicate the strength and direction of a relationship, it does not systematically break down a problem into its potential causal factors or identify the underlying reasons for a defect. Its primary utility is for correlation analysis, not for dissecting a problem to find its root cause.
B
Control chart
Why wrong: Control charts are statistical process control tools used to determine if a process is stable and in statistical control by monitoring performance over time against established upper and and lower control limits. They help identify out-of-control points or trends, signaling when a process needs investigation due to abnormal variation. However, a control chart itself does not perform the root cause analysis; it merely indicates when such an analysis might be necessary.
C
Delphi technique
Why wrong: The Delphi technique is a structured communication method used to obtain consensus from a panel of experts on a specific topic through a series of anonymous questionnaires and feedback rounds. While valuable for forecasting, risk identification, or decision-making where expert opinion is crucial, it is a group facilitation technique for opinion gathering, not a direct analytical tool for systematically dissecting a problem to identify its underlying causes. It relies on subjective expert judgment rather than objective causal analysis.
D
Cause-and-effect diagram
A cause-and-effect diagram, also known as an Ishikawa or fishbone diagram, is a visual tool used for systematically exploring all potential factors that could contribute to a specific problem or defect. It categorizes potential causes into major branches (e.g., Man, Machine, Material, Method, Measurement, Environment) to facilitate a comprehensive root cause analysis. This structured approach helps teams identify and investigate the underlying reasons for an issue, making it ideal for defect analysis and problem-solving.

Question 3easymultiple choice

During a daily standup, a developer mentions that a risk identified in the risk register has occurred and is causing a one-day delay. The risk response plan includes a mitigation strategy that can be implemented immediately. What should the project manager do FIRST?

Trap 1: Update the issue log and inform stakeholders of the delay

This action is premature as the *first* step when a risk materializes with a planned response. While updating logs and communicating are crucial project management activities, they typically follow the primary action of addressing the risk itself. The immediate priority when a risk event occurs and a response plan exists is to execute that plan to mitigate the impact, not merely document it as an issue or inform stakeholders of a potential delay before attempting to prevent or minimize it.

Trap 2: Escalate the issue to the sponsor for guidance

Escalating to the sponsor for guidance is an inappropriate immediate action when a predefined risk response plan already exists. Escalation is typically reserved for risks that are beyond the project manager's authority or resources, or for unidentified risks that have materialized without a pre-planned mitigation strategy. Relying on the sponsor for guidance at this stage would bypass the established risk management process and delay the necessary corrective action.

Trap 3: Conduct a new risk assessment to determine the best response

Conducting a new risk assessment at this juncture would be redundant and inefficient. The project team has already performed a thorough risk analysis and developed a specific response plan, which is documented in the risk register. Re-evaluating the situation would waste valuable time and resources, delaying the critical implementation of the pre-approved mitigation strategy and potentially exacerbating the impact of the materialized risk.

A
Update the issue log and inform stakeholders of the delay
Why wrong: This action is premature as the *first* step when a risk materializes with a planned response. While updating logs and communicating are crucial project management activities, they typically follow the primary action of addressing the risk itself. The immediate priority when a risk event occurs and a response plan exists is to execute that plan to mitigate the impact, not merely document it as an issue or inform stakeholders of a potential delay before attempting to prevent or minimize it.
B
Implement the planned risk response as documented in the risk register
When a previously identified risk materializes, the most appropriate and immediate action is to execute the specific risk response strategy already documented in the risk register. This proactive approach leverages the prior planning effort, ensuring that the project team is prepared to mitigate the impact of the risk event efficiently and effectively, thereby minimizing potential disruptions to project objectives.
C
Escalate the issue to the sponsor for guidance
Why wrong: Escalating to the sponsor for guidance is an inappropriate immediate action when a predefined risk response plan already exists. Escalation is typically reserved for risks that are beyond the project manager's authority or resources, or for unidentified risks that have materialized without a pre-planned mitigation strategy. Relying on the sponsor for guidance at this stage would bypass the established risk management process and delay the necessary corrective action.
D
Conduct a new risk assessment to determine the best response
Why wrong: Conducting a new risk assessment at this juncture would be redundant and inefficient. The project team has already performed a thorough risk analysis and developed a specific response plan, which is documented in the risk register. Re-evaluating the situation would waste valuable time and resources, delaying the critical implementation of the pre-approved mitigation strategy and potentially exacerbating the impact of the materialized risk.

Question 4easymultiple choice

A team member reports that a task is 50% complete but has consumed 70% of the budget. Which metric indicates that the project is over budget?

Trap 1: Budget at Completion (BAC)

Budget at Completion (BAC) represents the total planned value for the entire project or a specific work package, signifying the complete budget authorized at the project's outset. It is a static baseline figure reflecting the total financial commitment for all work to be accomplished. While crucial for overall financial planning and setting the project's financial ceiling, BAC does not provide insight into the current cost efficiency or performance of work already completed, making it unsuitable for assessing a task's ongoing cost status.

Trap 2: Estimate at Completion (EAC)

Estimate at Completion (EAC) is a forecast of the total cost required to complete all project work, typically updated based on current project performance and future projections. It represents a revised prediction of the final project cost, often calculated using various formulas depending on assumptions about future performance. EAC is a forward-looking projection of the project's ultimate financial outcome, not a metric that describes the current cost efficiency or performance of work already executed.

Trap 3: Schedule Performance Index (SPI)

The Schedule Performance Index (SPI) is an Earned Value Management (EVM) metric used to measure the efficiency of the project schedule. Calculated as Earned Value (EV) divided by Planned Value (PV), SPI indicates whether the project is ahead of or behind schedule relative to the baseline plan. While vital for tracking timeline progress and predicting schedule completion, SPI specifically addresses schedule performance and does not provide any information regarding the cost efficiency or financial status of the work completed.

A
Budget at Completion (BAC)
Why wrong: Budget at Completion (BAC) represents the total planned value for the entire project or a specific work package, signifying the complete budget authorized at the project's outset. It is a static baseline figure reflecting the total financial commitment for all work to be accomplished. While crucial for overall financial planning and setting the project's financial ceiling, BAC does not provide insight into the current cost efficiency or performance of work already completed, making it unsuitable for assessing a task's ongoing cost status.
B
Cost Performance Index (CPI)
The Cost Performance Index (CPI) is a critical Earned Value Management (EVM) metric that directly measures the cost efficiency of the work performed to date. Calculated as Earned Value (EV) divided by Actual Cost (AC), CPI indicates how much value is being received for each dollar spent. A CPI less than 1.0 signifies a cost overrun, meaning the project is spending more than planned for the work accomplished, directly addressing the need to assess current cost performance.
C
Estimate at Completion (EAC)
Why wrong: Estimate at Completion (EAC) is a forecast of the total cost required to complete all project work, typically updated based on current project performance and future projections. It represents a revised prediction of the final project cost, often calculated using various formulas depending on assumptions about future performance. EAC is a forward-looking projection of the project's ultimate financial outcome, not a metric that describes the current cost efficiency or performance of work already executed.
D
Schedule Performance Index (SPI)
Why wrong: The Schedule Performance Index (SPI) is an Earned Value Management (EVM) metric used to measure the efficiency of the project schedule. Calculated as Earned Value (EV) divided by Planned Value (PV), SPI indicates whether the project is ahead of or behind schedule relative to the baseline plan. While vital for tracking timeline progress and predicting schedule completion, SPI specifically addresses schedule performance and does not provide any information regarding the cost efficiency or financial status of the work completed.

Question 5hardmulti select

You are managing a large, distributed project using a hybrid methodology. The team is experiencing communication breakdowns and conflict between onshore and offshore members. Which THREE actions should you take to improve team collaboration and performance? (Choose three)

Trap 1: Separate the team into onshore and offshore sub-teams with their…

Segregation may increase silos and conflict.

Trap 2: Increase the frequency of status reporting

More reporting may not improve collaboration and could increase administrative burden.

A
Establish regular video conference meetings for synchronous collaboration
Video calls enhance non-verbal communication and build relationships.
B
Separate the team into onshore and offshore sub-teams with their own leads
Why wrong: Segregation may increase silos and conflict.
C
Create a team charter with agreed-upon communication norms
A team charter establishes expectations and reduces misunderstandings.
D
Increase the frequency of status reporting
Why wrong: More reporting may not improve collaboration and could increase administrative burden.
E
Celebrate team milestones and individual achievements publicly
Recognition fosters a positive team culture and motivation.