PMP Process — Managing Technical Aspects Practice Question
During a sprint retrospective, the team identifies that the daily standup meetings are taking too long and not focusing on impediments. Which TWO actions would help improve the effectiveness of the daily standup?
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
✓
Time-box the standup to 15 minutes and use a talking stick.
Effective daily standups are time-boxed (e.g., 15 minutes) and focus on progress, plans, and impediments. Using a visual board helps keep the discussion focused.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Time-box the standup to 15 minutes and use a talking stick.
Why this is correct
Time-boxing the Daily Scrum to 15 minutes is a core Scrum principle, ensuring the meeting remains concise and focused on immediate coordination for the next 24 hours. Utilizing a talking stick can further enhance this by enforcing a single speaker, promoting active listening, and preventing individuals from dominating the discussion or veering off-topic, thereby maintaining efficiency and adherence to the time-box.
- ✗
Hold the standup without the scrum master to save time.
Why it's wrong here
Holding the Daily Scrum without the Scrum Master is counterproductive and undermines the team's ability to effectively self-organize and address impediments. The Scrum Master's presence is vital for facilitating the meeting, coaching the Development Team on Scrum practices, and actively working to remove any identified impediments that hinder the team's progress toward the Sprint Goal. Their absence would likely lead to the very issues of disorganization and inefficiency the team is trying to resolve.
- ✗
Extend the standup to 30 minutes to allow more detailed discussion.
Why it's wrong here
Extending the Daily Scrum to 30 minutes fundamentally misunderstands its purpose and often leads to decreased efficiency and focus. The Daily Scrum is designed for quick synchronization and identification of impediments, not for detailed problem-solving or extensive discussions, which should occur in separate, dedicated meetings. A longer time-box encourages tangents, reduces the time available for actual work, and can transform the meeting into an inefficient status report rather than a dynamic planning session for the Development Team.
- ✓
Focus each team member's update on progress, plan, and impediments.
Why this is correct
Focusing each team member's update on what they did yesterday, what they will do today, and any impediments they face is a highly effective structure for the Daily Scrum. This classic three-question format ensures updates are concise, relevant to the Sprint Goal, and immediately highlight progress, upcoming work, and any blockers. It fosters transparency, facilitates quick adjustments to the Sprint Backlog, and helps the Development Team maintain collective focus without delving into unnecessary details.
- ✗
Replace the standup with a written status report.
Why it's wrong here
Replacing the Daily Scrum with a written status report eliminates the critical benefits of real-time, interactive communication and immediate coordination. The Daily Scrum is specifically designed for face-to-face (or virtual equivalent) synchronization, allowing team members to quickly understand each other's progress, identify dependencies, and collectively adapt their plan for the next 24 hours. A written report lacks the immediacy, dynamic interaction, and non-verbal cues necessary for agile teams to effectively self-organize and resolve emerging issues promptly.
Go deeper
Related to this question
Learn chapter
Leading Teams and Empowering Team Members
Key term
Sprint Retrospective
A Sprint Retrospective is a time-boxed meeting at the end of a Scrum sprint where the team reflects on their process and identifies improvements for the next sprint.
Key term
Daily Standup
A short, time-boxed daily meeting where team members share progress, plans, and blockers to stay aligned.
About these practice questions
One of 800 original PMP 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI 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 PMP exam.