Velocity is a tool for internal team improvement and forecasting, not external benchmarking. According to the PMI Agile Practice Guide (Section 5.4: Velocity and Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), tracking velocity over time helps teams assess the impact of process changes, refine estimates, and validate their continuous improvement efforts.

Option C is correct: it focuses on team-level improvement.

Option A uses velocity inappropriately for performance review, which goes against agile principles.

Option B promotes unhealthy comparisons across teams.

Option D is partially true, but stakeholder communication is secondary to internal use.

The correct answer is A — Lead the team and help them to constantly improve the processes in the project.

The Scrum Master is responsible for ensuring that retrospective action items are tracked and followed up on. While the team owns the improvement actions, the Scrum Master provides support, accountability, and facilitation to ensure that continuous improvement happens.

PMI Agile Practice Guide:

“The Scrum Master facilitates continuous improvement by helping the team reflect, identify actions, and ensure those actions are implemented.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths:

“Retrospectives are only effective if outcomes are tracked. The Scrum Master ensures improvement ideas are not forgotten and become part of the team’s evolution.”

(PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

B uses a confrontational tone—contrary to servant leadership.

C implies micro-management and contradicts self-organization.

D avoids responsibility for facilitating improvements.

Answer: A

—

When plotting performance and dependencies on the product roadmap, the product manager should consider features, stages of development, technology and infrastructure, dependencies, and risks. These components are critical for understanding how the product will evolve over time, the technical requirements, how different parts of the system depend on each other, and the potential risks that may arise. This approach ensures that the team can manage dependencies effectively, mitigate risks, and deliver the product in line with business goals and timelines.

In an agile environment, even a chaotic one, a release plan should focus on providing a high-level view of the product ' s objectives, the key features to be developed, and the iteration timelines. Including dependencies and specifying the responsible teams for each component ensures that expectations are set clearly for stakeholders while also providing the flexibility needed to adapt to changes. By outlining both the objectives and iteration details, the product owner ensures transparency and alignment with stakeholders while maintaining the iterative nature of agile development. This approach allows for informed decision-making without locking the team into overly rigid plans.

The correct answer is B – The entire team is responsible for quality, but each team member ' s role may vary as stated in the definition of done (DoD).

In Agile, quality is a shared responsibility. While specialists like QA may have defined roles, all team members are expected to contribute to maintaining and improving product quality. The Definition of Done (DoD) captures shared criteria for acceptance and completion.

From the PMI Agile Practice Guide:

“Agile teams are cross-functional and collectively accountable for quality. Specific roles may perform different tasks, but everyone contributes to ensuring the product meets the agreed-upon standards.”

(PMI Agile Practice Guide, Section 5.2 – Quality and Definition of Done)

Mike Griffiths clarifies:

“Quality is everyone’s responsibility. Teams should define what ' done ' means and ensure that all members understand and uphold those standards during development.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why other options fall short:

A implies all members must be involved in every component, which may not be efficient or realistic.

C incorrectly assigns surprises or gaps solely to QA.

D misrepresents the Product Manager ' s role and overemphasizes top-down functionality.

Answer: B

In an Agile environment, fostering a culture of collaboration and effective communication is key to success, especially when working with a diverse team. By creating a shared vision, the project manager aligns the team towards common goals, which helps reduce misunderstandings. Using techniques to increase empathy and positive interaction ensures that team members understand and respect each other ' s different perspectives. This approach promotes a collaborative environment where diverse ideas can be valued and conflicts can be addressed constructively.

The correct answer is C – The Product Owner, since their vision is the basis for the acceptance criteria.

The Product Owner is responsible for defining the product backlog items, including their acceptance criteria. They represent the customer and stakeholders, and ensure that the backlog items deliver business value. During backlog refinement, the PO provides clarity to the team when questions arise.

From the PMI Agile Practice Guide:

“The product owner defines and prioritizes the product backlog and is responsible for ensuring user stories and acceptance criteria are clear and understood by the team.”

(PMI Agile Practice Guide, Section 5.2 – Backlog Refinement)

Mike Griffiths states:

“The product owner is the central point for decisions related to backlog items. Their role is to ensure that requirements and acceptance criteria reflect the desired outcome and stakeholder expectations.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Value-Driven Delivery)

Other options are incorrect:

A (Sponsor) is too high-level and not involved in story-level discussions.

B (Scrum Master) facilitates the process, not the requirements.

D (Developer) implements the story but does not define acceptance.

Answer: C

The correct answer is C – Determine who is best qualified to address the challenges. Agile teams are self-organizing and empowered to make technical decisions. When challenges arise, the team collaboratively identifies who is best suited to resolve issues, rather than relying on external direction or top-down task assignment.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing. When challenges or new work arises, the team decides how to proceed, including task allocation based on skills and availability.”

(PMI Agile Practice Guide, Section 4.3 – Self-Organization)

Mike Griffiths also notes:

“Team members decide how work is divided and who tackles what. When technical complexity is involved, those with relevant expertise are encouraged to step in, with support from the rest of the team.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A violates the principle of team autonomy.

B delays delivery rather than solving the problem.

D incorrectly places the Product Owner in a team management role.

Answer: C

According to the PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement), managing stakeholder expectations starts with establishing a shared vision and involving stakeholders in key activities like iteration reviews. This ensures transparency, feedback, and alignment on progress and priorities.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the idea that a common vision and shared goals foster trust and improve stakeholder relationships.

Option A is correct: a shared vision and active involvement lead to better stakeholder alignment.

Option B and C are partially right but limit collaboration or dismiss stakeholder input.

Option D is inconsistent with agile’s emphasis on open, continuous communication.

The correct answer is D – Write tests that will be used to know when a story has been correctly developed. This practice aligns with Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD), which are common in agile environments. Agile promotes defining “done” through clear acceptance criteria and tests before coding begins.

From PMI Agile Practice Guide:

“Agile teams use test-first practices, such as TDD or ATDD, where acceptance tests are written before development begins. This ensures that functionality is built to meet agreed expectations.”

(PMI Agile Practice Guide, Section 5.5 – Agile Testing and Quality Strategies)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Defining acceptance criteria or tests before development is a core agile practice. It ensures the team understands what success looks like and builds quality in from the start.”

(Mike Griffiths, Chapter 6 – Problem Detection and Resolution)

Option A may be useful but is unrelated to the new requirements.

Option B is not standard—customers help define acceptance criteria but rarely write tests.

Option C skips an important quality control step and doesn’t align with test-first practices.

Answer: D

────────────────────────────────────────────