The correct answer is B – Ensure there is a balanced mix of people who are experts and members with broad experience based on the work to be performed and determine training needs.

Scrum encourages cross-functional, self-organizing teams with complementary skills. Building a balanced team that reflects both depth and breadth of experience ensures optimal delivery while enabling team learning.

From PMI Agile Practice Guide:

“Agile teams are cross-functional. The team may need T-shaped skills—members with deep expertise in one area and a willingness to broaden knowledge in other areas. Creating balanced teams with knowledge diversity leads to better collaboration and learning.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths adds:

“Team selection should prioritize diversity of skill sets and the ability to collaborate, not just performance history. The goal is a team that can deliver value collectively, not as individuals.”

(Mike Griffiths, Chapter 4 – Team Performance)

Why the other options are not suitable:

A may reduce team diversity and discourage healthy conflict resolution.

C may not be feasible in distributed environments and is not a strict requirement.

D focuses on individual velocity contributions, which contradicts Agile’s team-based delivery focus.

Answer: B

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

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

In Agile, ensuring that the product works without bugs or missing features can be achieved through continuous testing and validation of the product. Test-driven development (TDD) is an approach where tests are written before the code is developed. This helps ensure that each feature is fully tested as it is built, focusing on customer requirements from the start and preventing issues from accumulating. By using TDD, the product owner ensures the product is being tested incrementally, which reduces the risk of defects and aligns with customer expectations for a high-quality product upon release.