Planning  Incorrect.  While stakeholder management planning occurs in the Planning process group, the initial identification happens in Initiating.

Executing  Incorrect  The Executing process group focuses on implementing the project plan and engaging stakeholders, not identifying them.

Monitoring and Controlling  Incorrect.  Monitoring and Controlling involves tracking stakeholder engagement, not their initial identification.

The project is under budget and behind schedule  Incorrect. A negative CV indicates over budget, not under budget.

The project is under budget and ahead of schedule  Incorrect. A negative CV means over budget, not under budget.

The project is over budget and behind schedule  Incorrect. A positive SV means ahead of schedule, not behind.

Work Breakdown Structure (WBS)  Incorrect.  The WBS is a tool that breaks down the project scope into manageable deliverables, not a plan for managing scope.

Scope Statement  Incorrect.  The Scope Statement defines the project scope but does not detail how it will be managed or controlled.

Project Charter  Incorrect.  The Project Charter provides a high-level scope overview but does not include detailed scope management processes.

To assign new tasks to team members  Incorrect.  Task assignment occurs during sprint planning, not the daily stand-up.

To provide a status update to the project sponsor  Incorrect.  The stand-up is for the team, not for reporting to external stakeholders like the sponsor.

To finalize the sprint backlog  Incorrect.  The sprint backlog is finalized during sprint planning, not the daily stand-up.

Implement the change immediately to satisfy the stakeholder  Incorrect.  Implementing changes without evaluation risks scope creep and uncontrolled impacts.

Reject the change to avoid scope creep  Incorrect.  Rejecting the change outright dismisses potentially valuable requests without proper analysis.

Update the project schedule to accommodate the change  Incorrect.  Updating the schedule before evaluating the change through the change control process violates project management principles.

The path with the most activities  Incorrect.  The number of activities does not define the critical path; it’s about duration and dependencies.

The shortest sequence of activities to complete the project  Incorrect.  The critical path is not the shortest sequence; it’s the longest, as it sets the project duration.

The path with the least amount of float  Incorrect.  While the critical path typically has zero float, the definition focuses on it being the longest path, not just the least float.

Sprint Review  Incorrect.  The Sprint Review focuses on demonstrating completed work and gathering feedback, not backlog prioritization.

Daily Stand-up  Incorrect.  The Daily Stand-up addresses daily progress and impediments, not backlog management.

Sprint Retrospective  Incorrect.  The Sprint Retrospective focuses on process improvement, not backlog prioritization.

Fast-track the project schedule  Incorrect.  Fast-tracking (performing activities in parallel) is a schedule compression technique, but it’s premature without understanding the cause of the delay.

Crash the project schedule  Incorrect.  Crashing (adding resources to shorten duration) increases costs and should only be done after analyzing the issue.

Request additional funding from the sponsor  Incorrect.  Requesting funding is a potential response but not the first step; the cause must be identified before determining if funding is needed.

To define the detailed project schedule  Incorrect.  The project charter does not include a detailed project schedule; scheduling is developed later during the planning process (e.g., in the Schedule Management Plan)

To outline the project’s risk management plan  Incorrect.  The risk management plan is a separate document created during the planning process, not part of the project charter.

To document the project’s detailed budget  Incorrect.  While the charter may include high-level cost estimates, the detailed budget is developed in the Cost Management Plan, not the charter.

To document the project’s budget and cost estimates  Incorrect.  The risk register does not cover budget or cost estimates; those are part of the Cost Management Plan.

To track project milestones and deliverables  Incorrect.  Milestones and deliverables are tracked in the project schedule or WBS, not the risk register.

To outline the roles and responsibilities of the project team  Incorrect.  Roles and responsibilities are documented in the Resource Management Plan or RACI chart, not the risk register.

The speed at which the team delivers the final product  Incorrect.  Velocity measures work completed per sprint, not the speed of final product delivery.

The time taken to complete a single user story  Incorrect.  Velocity is aggregate for the sprint, not specific to a single user story.

The rate of stakeholder feedback during a sprint  Incorrect.  Velocity is unrelated to stakeholder feedback; it focuses on team output.

To reduce the number of tasks in the sprint backlog  Incorrect.  Kanban does not use a sprint backlog; it manages a continuous flow of work.

To increase the number of completed user stories  Incorrect.  Limiting WIP aims to improve flow, not directly increase completed stories.

To shorten the sprint duration  Incorrect.  Kanban does not use sprints, so shortening sprint duration is irrelevant.

It tracks stakeholder engagement levels  Incorrect.  EVM does not track stakeholder engagement; that’s part of Stakeholder Management.

It identifies critical path activities  Incorrect.  Critical path identification is part of schedule management, not EVM.

It forecasts resource allocation needs  Incorrect.  While EVM can inform resource needs indirectly, its primary purpose is performance measurement, not resource forecasting.

To facilitate daily stand-up meetings  Incorrect.  Facilitating daily stand-ups is typically the Scrum Master’s role.

To manage the project budget and schedule  Incorrect.  Managing budget and schedule is not the Product Owner’s primary responsibility; they focus on the product vision and backlog.

To coach the team on Agile practices  Incorrect.  Coaching on Agile practices is the Scrum Master’s role, not the Product Owner’s.

Risk Register  Incorrect. The Risk Register documents risks, not team roles.

Work Breakdown Structure (WBS)  Incorrect.  The WBS defines deliverables but does not specify who is responsible for them.

Stakeholder Register  Incorrect.  The Stakeholder Register identifies stakeholders and their interests, not task responsibilities.