Courseiva
Process — Managing Technical AspectsmediumMultiple SelectObjective-mapped

PMP Process — Managing Technical Aspects Practice Question

Your project is using a hybrid approach with both predictive and agile elements. The team is struggling with the daily standup because some members treat it as a status report for management. Which THREE actions should you take to improve the 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

Enforce the 15-minute timebox to keep the meeting efficient

Timeboxing the standup to 15 minutes maintains efficiency and prevents the meeting from becoming a lengthy status report. Option C is correct because coaching the team to emphasize impediments and collaboration aligns the standup with its true purpose: team coordination and problem-solving. Option D is correct because clearly communicating that the standup is for the team, not for management reporting, helps reset expectations. Option A is incorrect because canceling the daily standup removes a key communication cadence, and a weekly meeting is insufficient for timely coordination. Option E is incorrect because the standup should be facilitated by the team (often a rotating role), not by the product owner, whose presence is as an attendee to hear updates.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cancel the standup and replace it with a weekly status meeting

    Why it's wrong here

    Canceling the daily standup, a cornerstone of agile methodologies, and replacing it with a weekly status meeting would severely undermine the project's agile components. The daily standup provides crucial daily synchronization, rapid impediment identification, and immediate re-planning necessary for adaptive approaches. A weekly meeting lacks the frequency and immediacy required for a hybrid project to respond effectively to changes and maintain continuous flow.

  • Enforce the 15-minute timebox to keep the meeting efficient

    Why this is correct

    Enforcing the 15-minute timebox is a critical technique for maintaining the efficiency and focus of the daily standup. This constraint encourages team members to be concise, prioritize key updates, and defer detailed discussions to separate follow-up meetings. Adhering to the timebox prevents the standup from becoming a lengthy problem-solving session or a general discussion forum, ensuring it remains a quick coordination event.

  • Coach the team to focus on impediments and collaboration rather than individual status

    Why this is correct

    Coaching the team to shift their focus from merely reporting individual status to actively identifying impediments and fostering collaboration is essential for an effective standup. The primary goal is to highlight blockers that prevent progress and to coordinate efforts for the next 24 hours, rather than providing a detailed account of personal tasks. This approach transforms the meeting into a proactive problem-solving and synchronization forum, aligning with agile principles.

  • Reiterate that the standup is for the team to coordinate, not for management reporting

    Why this is correct

    Reiterating that the standup serves as a team coordination event, distinct from a management reporting session, is crucial for its effectiveness and psychological safety. The standup's purpose is for the development team to synchronize their work, identify dependencies, and plan their immediate activities, not to provide progress updates to external stakeholders. This clarification empowers the team to own the meeting and fosters an environment of transparency among peers, rather than one of accountability to superiors.

  • Ask the product owner to run the standup to keep it focused

    Why it's wrong here

    Asking the Product Owner to run the daily standup is generally inappropriate as it deviates from the self-organizing principles of agile teams. The standup is a meeting *for* the development team, facilitated by the Scrum Master or a team member, to coordinate their work and plan for the next 24 hours. While the Product Owner can attend to answer questions, their leadership role is typically focused on product vision and backlog management, not facilitating the team's internal daily synchronization.

About these practice questions

Courseiva writes every PMP question from scratch — 800 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.