SAFe-Agilist Product Development Flow Practice Question
Why is 'Multitasking' considered a major enemy of flow in a SAFe ART?
⚠ Common exam trap
Candidates often focus on 'employee burnout' or 'lack of focus'. While true, the specific technical reason SAFe highlights is the 'cost of context switching' which directly impacts delivery throughput.
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
✓
It increases the cost of context switching.
Multitasking introduces significant context-switching costs, where the team loses time and focus whenever they shift between different tasks. This reduces overall productivity, increases the likelihood of errors, and extends the lead time for all items being worked on. In a flow-based system, it is much more efficient to focus on completing a single item before beginning another, as this ensures rapid progress and minimizes the time that work sits idle in a partially finished state.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It decreases the visibility of the work.
Why it's wrong here
Multitasking makes work visible on the board, but it creates a confusing mess where nothing appears to be moving. The issue is not visibility, but the lack of progress on any single item, which stalls the flow of value and creates a perception of being 'busy' while accomplishing very little.
- ✓
It increases the cost of context switching.
Why this is correct
Every time a developer switches tasks, they incur a 'switching tax'—the time required to reload the context of the previous task. This accumulated loss of time dramatically slows down completion rates and introduces waste, which is the primary reason multitasking is strictly discouraged in Lean-Agile product development workflows.
- ✗
It makes it harder to track team velocity.
Why it's wrong here
Velocity is simply a measure of points completed, regardless of how many tasks were in play. While multitasking makes velocity unpredictable, the real problem is the negative impact on the actual work and the cycle time, not the measurement tool used to track the team's historical performance capacity.
- ✗
It forces developers to learn more skills.
Why it's wrong here
Learning new skills is beneficial, but multitasking is not an efficient way to achieve it. Cross-skilling should be an intentional part of the team's development plan, whereas multitasking is an unplanned, reactive behavior that disrupts the flow and negatively impacts the quality and speed of current project deliverables.
About these practice questions
One of 315 original SAFe-Agilist practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.