Full Access PMI PMI-ACP Tutorials

The correct answer is C – Ensure that members begin to self-organize as small teams with efficiently distributed skills.

Agile emphasizes self-organizing teams. When teams are too large, splitting into smaller teams is a good practice (Scrum recommends 5–9 members per team). However, rather than top-down assignment, the Scrum Master should enable and support self-organization. Teams should be encouraged to form organically while ensuring knowledge-sharing and cross-functional capabilities.

From the PMI Agile Practice Guide:

“Agile leaders support team self-organization by creating an environment of trust and encouraging the team to determine how best to accomplish their work.”

(PMI Agile Practice Guide, Section 5.2 – Team Composition)

Mike Griffiths writes:

“Agile teams are self-organizing, and the role of the leader is to facilitate the conditions for that to occur, not to direct assignments.”

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

Why other options are less appropriate:

A suggests command-and-control behavior, which is contrary to Agile values.

B makes assumptions about comfort levels and may ignore skill diversity.

D disregards team input and imposes a solution, limiting buy-in and trust.

Answer: C

══════════════════════════════════════════════════

Agile emphasizesjust enough detailto start work and adapt through ongoing conversation. According to thePMI Agile Practice Guide (Section 5.2 Requirements and User Stories), stories should beclear enough for estimation and discussion, but not over-specified. The INVEST model (Independent, Negotiable, Valuable, Estimable, Small, Testable) supports this.

Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning)reiterates that stories should not contain exhaustive detail up front; rather, they evolve throughcollaborative dialoguewith the product owner.

Option Cis correct because it supports collaboration and adaptive planning.

Option AandBlead to over-specification and undermine agility.

Option Daddresses testing but doesn’t resolve confusion about appropriate story detail.

The correct answer is B – A product backlog should be created to list the project requirements from all of the project stakeholders.

In Agile, the product backlog serves as a living document where requirements, user stories, and stakeholder feedback are continuously refined. It is the central mechanism for capturing and prioritizing stakeholder needs and ensuring that business value is delivered incrementally.

From the PMI Agile Practice Guide:

“The product backlog is a prioritized list of work for the development team that is derived from stakeholder input, user stories, and emerging needs. It evolves as the project progresses and stakeholder feedback is incorporated.”

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

Mike Griffiths writes:

“Product backlogs provide transparency into stakeholder priorities. They enable the team to continuously align work with customer expectations and business needs.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Why the other options are incorrect:

A refers to the traditional project charter, which is not commonly updated throughout the agile life cycle.

C is a misunderstanding—the Agile Manifesto is a set of principles, not a project-specific document.

D misuses user stories; stories are used for functional requirements, not stakeholder profiles.

Answer: B

══════════════════════════════════════════════════

TheMoSCoW method(Must have, Should have, Could have, Won’t have) is aprioritization techniquecommonly used in agile to determine which stories deliver the most value. ThePMI Agile Practice Guide (Section 5.1: Prioritization Techniques)lists MoSCoW as one of the methods used by product owners and teams toprioritize backlog items.

Option Ais correct: MoSCoW is a proven agile prioritization method.

Option Bis used forestimation, not prioritization.

Option Cis not a standard agile prioritization method.