SAFe-Agilist Establishing Team and Technical Agility Practice Question
An Agile team has a high velocity but is still missing their PI Objectives. What is the most likely cause?
⚠ Common exam trap
Candidates often assume the team needs more training or technical skills, failing to distinguish between 'output' (velocity) and 'outcomes' (PI Objectives) as the root cause of the misalignment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The team is prioritizing output over the outcomes defined by the PI Objectives.
Velocity measures output, but PI Objectives measure outcomes. If a team is busy but not meeting their goals, they are likely focused on the wrong work. This happens when the team is not aligned with the Program Board or the business value. It matters because high velocity without goal alignment is essentially 'fast failure,' delivering many features that do not contribute to the overall business strategy.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The team is not using the correct estimation technique for their stories.
Why it's wrong here
Estimation is an internal team metric and, while useful, does not dictate the success of PI Objectives. If the team is hitting their estimates but missing objectives, the problem is likely related to the content being delivered, not the accuracy of the team's sizing techniques or their estimation velocity.
- ✓
The team is prioritizing output over the outcomes defined by the PI Objectives.
Why this is correct
Focusing on completing stories without regard for their impact on PI Objectives is a common trap. The team must ensure their backlog is prioritized based on the value required to meet these objectives. High output without alignment to desired business outcomes results in wasted effort and failed PI commitments.
- ✗
The team is suffering from technical debt that slows down their delivery.
Why it's wrong here
Technical debt might affect velocity, but it wouldn't explain why a team with high velocity is missing objectives. If velocity is high, technical debt is likely under control or being managed. The disconnect lies in the alignment of the team’s work to the broader program goals, not their technical efficiency.
- ✗
The Scrum Master is not facilitating the daily stand-up efficiently.
Why it's wrong here
The daily stand-up is for team coordination and synchronization, not for driving high-level PI Objectives. While a poor stand-up can be inefficient, it is rarely the cause of missing strategic PI goals. The alignment between the team and the Program level happens through planning, not the daily execution of tasks.
About these practice questions
This SAFe-Agilist question is part of Courseiva's 315-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.