When adaptive fits, and when it does not
The choice comes before any framework. An adaptive approach pays for its extra ceremonies when requirements are expected to change, the customer can give feedback often, and the product can be delivered in usable slices. A fixed bridge design, a regulator who signs off once at the end, or a supplier contract priced on the full scope all pull toward a predictive plan instead.
Structure matters as well. The outline asks about suitability for virtual, colocated, matrix and hierarchical organizations. A dedicated, colocated team with a product owner who can make decisions on the spot is the easy case. A matrix organization where people split their week across projects can still run iterations, but it pays in context switching and slower feedback.
OPAs and EEFs
The outline also names the organizational process assets (OPAs) and enterprise environmental factors (EEFs) that help adaptive work. An OPA is something the organization already owns and can reuse: templates, lessons learned, a working agreement from a previous team. An EEF is a condition the project lives in: culture, regulation, market pressure, the tools people are allowed to install. A culture that treats every visible problem as a failure is an EEF, and a poor one for showing unfinished work every two weeks.
Many organizations land on hybrid: predictive governance and funding around adaptive delivery. The three life cycles are defined side by side on life cycles and portfolios, and the control side of the predictive half is on cost and schedule variance.
How the four frameworks differ
| Aspect | Scrum | Kanban | XP | SAFe |
|---|---|---|---|---|
| Rhythm | Sprints of fixed length, one month or less | Continuous flow; teams set their own review and planning cadences | Short iterations, often one week, plus small frequent releases | Planning intervals (PIs; formerly program increments) that group several team iterations |
| Roles | Product owner, scrum master, developers | None prescribed; existing roles stay | A customer working with the team, programmers, a coach | Team roles plus program and portfolio roles |
| Main control | A sprint goal inside a timebox | Work-in-progress (WIP) limits on the board | Engineering practices: pairing, test-first, continuous integration | Shared planning and alignment across many teams |
| Typical scale | One team | One team or a service | One team | Many teams on one product or portfolio |
| Where it starts | A new team with a product to build | Work already in progress, visualized as it is | A codebase that needs sturdier habits | An organization coordinating many agile teams |
What the outline expects you to be able to do
- Say whether a project suits predictive, adaptive or hybrid delivery, and justify it with requirement stability, feedback frequency and risk.
- Name the pros and cons of an adaptive approach for a given organizational structure.
- Tell an OPA from an EEF in a scenario.
- Match Scrum’s accountabilities, events and artifacts to their purposes; the sprint mechanics are on iterations, backlog and agile tracking.
- Read a Kanban board and its WIP limits; the flow metrics that come off it are on the agile tracking page.
- Recognize XP practices by name: pair programming, test-driven development, continuous integration, collective code ownership.
- Explain when a single-team framework runs out and a scaled one such as SAFe comes up.
- Connect a scenario to the agile values behind it: individuals and interactions, working software, customer collaboration, responding to change.
Cards on this topic
The scenarios describe a team with a problem: flow, quality, coordination across teams, or an unclear role. The framework names come second.
Practice cards here are written for study, not taken from PMI. The real CAPM mixes multiple choice with drag-and-drop, hot spot, comic-strip and video items.
Card 01 of 25 · 0 done · 0 right
To do 25
Doing
Card 01 of 25
During Sprint Planning a development team lists five unrelated objectives for the upcoming sprint, each one tied to a different stakeholder. The team believes this shows responsiveness to everyone. What should the Scrum Master advise?
Note on A
Five unrelated objectives spread the team’s focus and make it hard to know whether the sprint succeeded.
Note on B
Splitting the objectives across sprints still leaves each sprint without a single unifying goal.
Note on C
Correct: A single Sprint Goal gives the sprint focus and coherence, and the selected items support that goal.
Note on D
Individual ownership fragments the team and undermines collaboration toward one shared outcome.
Card 02 of 25
An organization currently has six agile teams working simultaneously on a single complex software product. Recently, the teams have been experiencing severe integration bottlenecks during their sprints. Which scaling framework explicitly focuses on solving integration challenges specifically for 3 to 9 teams?
Note on A
Disciplined Agile is a toolkit for choosing ways of working, not a framework focused on integrating the work of a few teams on one product.
Note on B
A scrum of scrums is a coordination meeting rather than a framework built around an integration team for three to nine teams.
Note on C
Correct: Nexus extends Scrum for roughly three to nine teams on one product and adds an integration team to manage integration and dependencies.
Note on D
The Scaled Agile Framework covers many layers up to the portfolio, rather than focusing narrowly on integration for a small group of teams.
Card 03 of 25
During methodology planning, leadership expresses a desire for centralized control over multiple teams, but the agile teams insist that maintaining team autonomy and empirical process control is their highest priority. To best support the teams’ priorities, which approach should be selected?
Note on A
Correct: LeSS and Nexus keep Scrum’s empirical control and team autonomy at scale, adding only light coordination.
Note on B
Predictive phases replace empirical control with up-front plans, which conflicts with the teams’ stated priority.
Note on C
The Scaled Agile Framework adds more structured roles and program-level planning, which leans toward the central control leadership wants.
Note on D
A strict program hierarchy centralizes control and limits team autonomy.
Card 04 of 25
A stakeholder insists that a specific feature be moved to the top of the Product Backlog. Who has the authority to order the Product Backlog?
Note on A
The Scrum Team works together on the backlog, but ordering it is the Product Owner’s accountability.
Note on B
Correct: The Product Owner is accountable for ordering the Product Backlog and can weigh the stakeholder’s request against other needs.
Note on C
Stakeholders can request changes, but they must go through the Product Owner.
Note on D
The Scrum Master supports the process but does not order the Product Backlog.
Card 05 of 25
A team composed of generalizing specialists who can each contribute across several disciplines is preferred over a group of narrow specialists. What is the primary benefit of this cross-functional composition for Agile delivery?
Note on A
Cross-functional teams still rely on external stakeholders, suppliers, and support at times.
Note on B
Generalizing specialists keep a deep skill while helping in others; members do not become identical.
Note on C
Correct: Members who can contribute across disciplines reduce handoffs and waiting on scarce specialists, which improves flow.
Note on D
Staying in one discipline is how narrow specialists work, which is the opposite of the composition described.
Card 06 of 25
A regulated program uses Scrum to deliver a claims-processing platform. An external auditor requires predictable evidence of progress and quality at fixed intervals and asks the program for documentation. Delivering comprehensive predictive reports would consume most of the team’s capacity, and the regulator has not mandated a particular development approach. What is the best approach?
Note on A
Correct: A done increment meeting the definition of done gives regular, objective evidence of progress and quality without heavy extra reporting.
Note on B
Adding a phase-gate review to every sprint imposes predictive controls that the regulator has not required.
Note on C
Detailed earned value reporting at every audit would take the capacity the team needs for delivery and is not mandated.
Note on D
Freezing every requirement contradicts the adaptive approach and is not needed to give the auditor evidence.
Card 07 of 25
During Sprint Planning, a distributed team is debating how many items to take into the sprint. The Scrum Master notices the conversation drifting into detailed technical design and helps refocus the group on the Sprint Goal and the team’s capacity. What best describes the Scrum Master’s role in this event?
Note on A
Estimating the work belongs to the Developers, not the Scrum Master.
Note on B
Self-managing Developers decide who does which work, so the Scrum Master does not assign tasks.
Note on C
Correct: The Scrum Master facilitates events and coaches the team to keep them focused and productive.
Note on D
Selecting items is done by the Scrum Team, with the Product Owner explaining value, not by the Scrum Master.
Card 08 of 25
A team’s main problem is poor code quality, with frequent regressions after every release. Which framework’s practices target this problem MOST directly?
Note on A
Correct: Extreme Programming targets technical quality directly through practices such as test-first development, pair programming, refactoring, and continuous integration.
Note on B
The Scaled Agile Framework coordinates many teams; it does not focus on engineering practices for code quality.
Note on C
Scrum structures roles, events, and artifacts but does not prescribe engineering practices to prevent regressions.
Note on D
Kanban improves flow and visibility of work, not the technical practices that drive code quality.
Card 09 of 25
A software company recently adopted a scaled framework with heavy program governance to coordinate multiple teams. However, after several months, the teams are conducting all required ceremonies but release frequency and delivery speed have not improved. What is the most likely root cause of this failure?
Note on A
Adding another governance board increases oversight but would not speed up releases that are blocked by technical practices.
Note on B
More documentation of team metrics does not remove the bottlenecks that slow delivery.
Note on C
Correct: Scaling ceremonies without automated testing, integration, and deployment practices leaves releases slow, so the technical foundation is the likely cause.
Note on D
Linking increments to strategy improves alignment but does not explain why delivery speed stayed flat.
Card 10 of 25
According to the Scrum Guide, who is accountable for instilling quality by adhering to the Definition of Done?
Note on A
The Scrum Master coaches the team on Scrum but is not the one who builds quality into the increment.
Note on B
Stakeholders give feedback on the increment but are not responsible for meeting the Definition of Done.
Note on C
The product owner manages value and the backlog, while meeting the Definition of Done is the Developers’ accountability.
Note on D
Correct: The Developers are accountable for instilling quality by working to the Definition of Done.
Card 11 of 25
A development team reports that it is blocked by a technical dependency outside its control and cannot complete the sprint goal on time. Which role is responsible for helping remove this impediment?
Note on A
The developers raise the impediment and may resolve some themselves, but an obstacle outside their control calls for the Scrum Master’s help.
Note on B
The Product Owner manages value and the backlog; removing impediments is not that role’s main responsibility.
Note on C
A sponsor may help in some cases, but in Scrum the role that helps remove impediments is the Scrum Master.
Note on D
Correct: The Scrum Master helps the team remove impediments to its progress, especially those it cannot resolve on its own.
Card 12 of 25
An agile team delivers in two-week increments but struggles with long wait times because work moves sequentially among specialists such as analysts, developers, testers, and database administrators. The team is self-organizing, yet each item waits in a queue at every specialist boundary. What should the Scrum Master recommend to improve flow?
Note on A
A coordinator for handoffs adds another layer to the queues instead of reducing them.
Note on B
Correct: Building broader skills lets team members pick up work across specialties, which reduces queues and handoffs.
Note on C
Routing work by shortest queue keeps the same specialist handoffs, so the waits remain.
Note on D
Shorter sprints do not change how work moves between specialists, so the queues stay the same.
Card 13 of 25
A Scrum Team holds a 15-minute Daily Scrum each morning, but several developers treat it as a status report delivered to the Scrum Master. What is the primary purpose of the Daily Scrum?
Note on A
Turning the Daily Scrum into a status report to the Scrum Master is the problem the scenario describes.
Note on B
Demonstrating work to stakeholders happens in the Sprint Review.
Note on C
Correct: The Daily Scrum lets the Developers inspect progress toward the Sprint Goal and adapt their plan for the next day.
Note on D
The Definition of Done is not reviewed daily with the Product Owner; the Daily Scrum is for the Developers.
Card 14 of 25
A product team working under an adaptive approach merges code into a shared repository several times each day. Every merge automatically triggers a build and a suite of automated tests before the increment is demonstrated to stakeholders. Why does this continuous integration practice matter to the project?
Note on A
Correct: Each merge is built and tested automatically, so integration defects show up within hours, while they are still cheap to fix.
Note on B
Continuous integration supports the Definition of Done by testing every merge; it does not replace the quality bar the team agreed.
Note on C
Backlog refinement is a separate, ongoing activity; integrating code often says nothing about how well the backlog is refined.
Note on D
Continuous integration does the opposite: it tests on every merge so that testing is never pushed to the end of the release.
Card 15 of 25
For the last four sprints, the team has listed improvement actions during the retrospective and stored them in a shared document. The same problems, such as environment outages and unclear acceptance criteria, continue to appear. The team agrees the retrospectives themselves are productive discussions. What should the Scrum Master do?
Note on A
Correct: Putting at least one improvement action into the next sprint backlog makes it visible, owned, and actually worked on.
Note on B
Longer discussions do not help; the problem is that agreed actions are never carried out.
Note on C
Storing actions in a shared place is what the team already does, and it has not led to change.
Note on D
Improvement belongs to the whole team; handing the actions to one person outside the sprint keeps them out of the team’s plan.
Card 16 of 25
A Kanban team has a large number of items in progress but consistently misses delivery dates, and blockers are discovered late. The team lead proposes introducing WIP limits. What is the primary purpose of setting WIP limits in Kanban?
Note on A
WIP limits cap the amount of work in a stage; they do not assign ownership of stages.
Note on B
WIP limits govern work in progress, not changes to the backlog; Kanban accepts new work as capacity frees up.
Note on C
Correct: Limiting work in progress exposes bottlenecks and blockers sooner and improves flow and delivery predictability.
Note on D
Kanban usually has no sprints, and WIP limits improve flow and focus rather than promising a large rise in output.
Card 17 of 25
Which commitment is associated with the Product Backlog?
Note on A
Correct: In Scrum each artifact carries a commitment, and the Product Backlog’s is the Product Goal, the long-term objective that its items move the product toward.
Note on B
The Sprint Goal is the commitment of the Sprint Backlog; it gives the team one objective for the current sprint, not for the whole product.
Note on C
A product roadmap is a useful planning view, but it is not a Scrum artifact and not one of the three commitments.
Note on D
The Definition of Done is the commitment of the Increment; it sets the quality bar that work must meet to count as done.
Card 18 of 25
A project manager has been assigned to lead a newly formed cross-functional Agile team that is expected to self-organize around its own work and commit to its own sprint backlog items. What is the most appropriate role for this project manager?
Note on A
Correct: A self-organizing team benefits from a servant leader who coaches, supports, and removes impediments rather than directing the work.
Note on B
Assigning tasks and tracking utilization undermines the team’s self-organization and ownership of its work.
Note on C
Servant leadership is active support; staying uninvolved leaves the team without help with obstacles and alignment.
Note on D
Approving all estimates and commitments takes ownership away from the team that does the work.
Card 19 of 25
A Kanban team needs regular replenishment of work and periodic delivery planning but does not use Scrum ceremonies. Which practice should it adopt?
Note on A
Correct: Kanban uses its own cadences, such as replenishment and delivery planning meetings, held at a rhythm that suits the team.
Note on B
Scrum events are not required, and the team has stated it does not use Scrum ceremonies.
Note on C
A once-a-year planning session is far too infrequent for regular replenishment.
Note on D
Ad hoc meetings do not provide the regular rhythm the team needs.
Card 20 of 25
A Kanban team observes that its Testing column holds 11 items when the WIP limit is 6, while several developers are idle. What should the team do first?
Note on A
Starting new features adds more work to a system that is already over its limit.
Note on B
Raising the limit to match the pileup hides the bottleneck instead of fixing it.
Note on C
Escalating for more resources skips what the team can do now with its idle developers.
Note on D
Correct: When a column is over its WIP limit, the team stops starting and helps finish existing items, so idle developers swarm on testing.
Card 21 of 25
A team wants to improve how its members collaborate internally, and it also needs stakeholder feedback on the increment it has just built and released for inspection. Which pairing correctly matches each ceremony to its purpose?
Note on A
Correct: The Sprint Review inspects the increment with stakeholders and adapts the backlog, while the Retrospective improves how the team works.
Note on B
The purposes are swapped; process improvement is the Retrospective’s job and backlog adaptation comes from the Review.
Note on C
The Retrospective does not accept the increment, and the Review is not mainly about internal collaboration.
Note on D
The Review does not focus on team process, and the Retrospective does not inspect the product increment.
Card 22 of 25
An agile team has worked 60-hour weeks for three sprints to hit a release date, and quality is falling. Which Agile Manifesto principle is being violated?
Note on A
Correct: Agile principles call for a sustainable pace that the team can maintain indefinitely, and long overtime that hurts quality violates it.
Note on B
The team is still delivering toward the release, so frequent delivery is not what is being broken.
Note on C
Simplicity is about avoiding unnecessary work, which is not the problem described here.
Note on D
Nothing in the scenario involves rejecting changing requirements.
Card 23 of 25
One team assigns work to developers as soon as it is requested, creating large queues. Another team starts work only when capacity becomes free. Why is the pull-based approach generally preferred?
Note on A
Pull systems aim to limit work in progress, not maximize it.
Note on B
Correct: Pulling work only when capacity frees up limits WIP, shortens queues, and makes flow more predictable.
Note on C
Push and pull produce different flow results; push usually builds larger queues.
Note on D
Push systems tend to increase multitasking and waiting time, not reduce them.
Card 24 of 25
A newly formed agile team argues that using a work breakdown structure (WBS) is strictly forbidden in an adaptive environment and refuses to decompose epics visually. How should the project manager address this assumption?
Note on A
Correct: Agile teams can adapt predictive tools, such as a lightweight breakdown of epics, when they help the team understand the work.
Note on B
An unprioritized feature list loses the ordering by value that adaptive approaches depend on.
Note on C
Forcing a traditional WBS on every iteration overcorrects and ignores the need to tailor tools to the approach.
Note on D
Adaptive approaches still plan, just more often and in smaller pieces, so planning artifacts are not eliminated.
Card 25 of 25
A Scrum Team is refining how it manages its artifacts. Each sprint, the developers pull the highest-priority items from the ordered product list, forecast what can realistically be delivered, and create a plan they will adapt daily as new learning emerges. Who owns the resulting Sprint Backlog?
Note on A
Correct: The Developers own the Sprint Backlog, because it is their plan for delivering the sprint’s work, adapted daily.
Note on B
The Scrum Master supports the team and its process but does not own the Sprint Backlog.
Note on C
A project manager is not a Scrum role, and the Sprint Backlog belongs to the people doing the work.
Note on D
The Product Owner orders the Product Backlog; the Sprint Backlog is the Developers’ plan.
Done 0
Adopting a framework makes a team agile in roughly the way buying running shoes makes a person a runner. The habits come later, and they are the part that counts.
Where to go next
Planning and tracking the iterations themselves is the next category, iterations, backlog and agile tracking. If you are weighing a Scrum certificate against the CAPM, CAPM vs CSM compares the two credentials.