Overview
Disciplined Agile Overview introduces DA as a decision framework rather than a method. Scrum tells a team what to do; DA helps a team decide what to do by laying out the decisions every team faces, the options available for each, and the trade-offs of each option. It draws on Lean thinking (flow, limiting work in progress, eliminating waste) and agile practice (short feedback cycles, collaboration, working solutions) and adds a mindset of principles, promises and guidelines. The phrase you will meet everywhere is way of working, or WoW: the combination of lifecycle, practices and roles a team actually uses.
Candidates must understand why DA exists. Context counts: team size, distribution, compliance and complexity differ, so one prescribed process fits few teams well. Every later module builds on this idea. The knowledge base supplies the options, the Team Canvas exposes the context, value acceleration turns choices into an improvement backlog, and the scenarios practice tailoring for real teams.
How it's tested
Questions on this module are short scenarios and concept checks. A team, a leader or an executive proposes something, and you judge whether it reflects the DA mindset. Expect 'which principle does this illustrate', 'what is the BEST next step for this team' and 'which lifecycle is the most appropriate starting point'. The right answer respects the team's context and leaves room to evolve.
-
Name the principle
A behavior is described, such as a team adopting a technique from outside its usual method, and you identify the DA principle it reflects, here choice is good.
-
Mandate versus choice
Someone proposes one standard process for every team; you pick the answer that sets guardrails and lets each team choose within them.
-
Pick a starting lifecycle
A team's work pattern is described and you choose the lifecycle that fits it best, knowing the team will tailor it later.
A director wants all twelve teams to run identical two-week sprints so reports look alike. Ask what DA says about context: teams differ in size, work type and constraints, so a single mandated process trades effectiveness for uniformity. The DA answer sets common governance (shared milestones and outcome measures) while each team chooses its own WoW. An answer that enforces identical sprints, or one that drops all governance, both miss the point.
Module topics 3
Official module topics from the PMI outline, in outline order.
1.1 The DA decision frameworkDecisions, options and trade-offs instead of prescriptions.
- What it means
- DA organizes process knowledge as decisions a team must make, called process goals, each broken into decision points with ranked options and their trade-offs. A goal diagram shows these visually.
- What to understand
- No option is best everywhere; options listed with an arrow are ordered so that those near the top are generally more effective but often harder to adopt. The framework tells you what to consider, then the team picks what fits its context and situation today.
- How it shows up
- A scenario asks how a team should decide on a practice, and the correct answer is to review the options and trade-offs for that decision point in the team's context.
- Common confusion
- Treating the top-ranked option as mandatory; DA expects a team to choose what it can adopt now and move up over time.
1.2 Lean and agile foundations of DAThe mindset of principles, promises and guidelines.
- What it means
- DA's mindset combines Lean and agile thinking in eight principles (delight customers, be awesome, context counts, be pragmatic, choice is good, optimize flow, organize around products/services, enterprise awareness), seven promises and eight guidelines.
- What to understand
- Principles state the philosophy, promises are commitments a team makes to the people it works with (such as make all work and workflow visible and keep workloads within capacity), and guidelines are practical advice (such as validate our learnings). Optimize flow and keep workloads within capacity carry the Lean side; delight customers and validate our learnings carry the agile side.
- How it shows up
- A behavior is described, such as a team refusing to start new work until something finishes, and you name the principle or promise it reflects.
- Common confusion
- Mixing up promises and principles: making work visible is a promise; context counts is a principle.
1.3 Choosing and evolving a team's way of workingStart with a lifecycle, then improve through experiments.
- What it means
- A team chooses a starting lifecycle (Agile, Lean, Continuous Delivery: Agile, Continuous Delivery: Lean, Exploratory or Program) and then evolves its WoW through guided continuous improvement: small, measured experiments informed by the DA toolkit.
- What to understand
- Choosing is not a one-time event. The team owns its WoW, adjusts it when the context changes, and uses retrospectives plus the toolkit to find a better option instead of inventing one from scratch. Enterprise awareness means its choices must still fit organizational guardrails.
- How it shows up
- A team's chosen practice stops working after a change in context, and you choose the response that runs a targeted experiment rather than a full process reset or no change.
- Common confusion
- Believing a team picks a lifecycle once and is locked in; DA expects teams to change lifecycle when their situation changes.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Way of working (WoW)
WoW is the combination of lifecycle, practices, roles and tools that a specific team actually uses to get its work done, as opposed to a method described in a book.
- Remember
- Each team owns and evolves its WoW within organizational guardrails; DA never prescribes one WoW for all teams.
- Tested as
- Most scenario answers ask what a team should do to its WoW, so the term frames the whole course.
- Trap
- Assuming WoW means the team can do anything it likes, ignoring the enterprise awareness principle and shared governance.
-
Context counts
This principle says every team faces a unique situation shaped by factors such as team size, geographic distribution, domain and technical complexity, skills and regulatory compliance.
- Remember
- Effective process depends on context, so the same practice can be right for one team and wrong for another.
- Tested as
- It is the reason DA rejects one-size-fits-all mandates, and it sits behind most 'BEST approach' answers.
- Trap
- Picking the answer that copies what worked for another team without checking whether the contexts match.
-
Choice is good
This principle says teams should be able to choose from many techniques, drawn from Scrum, Kanban, XP, SAFe, Lean and others, because having options lets them fit process to context.
- Remember
- DA is agnostic: it includes practices from many sources and ranks them by trade-off rather than brand.
- Tested as
- Scenarios where a team borrows a practice from another framework test whether you see this as legitimate.
- Trap
- Treating a team that uses Kanban boards inside a Scrum-based lifecycle as 'not doing it right'.
-
Be pragmatic
This principle says teams should aim to be as effective as they can in their situation, not as 'pure agile' as possible.
- Remember
- Effectiveness beats purity; a regulated team keeping a required document is pragmatic, not un-agile.
- Tested as
- Appears when an option sounds more agile but ignores a real constraint.
- Trap
- Choosing the most agile-sounding answer over the one that actually works for the stated constraint.
-
Process goal
A process goal is a high-level outcome a team must address, such as Explore Scope or Improve Quality, with decision points and options beneath it.
- Remember
- Goals state what a team needs to achieve, not how; the how comes from the options the team chooses.
- Tested as
- Questions about how DA structures its guidance expect goal, decision point and option in that order.
- Trap
- Calling a process goal a mandatory activity or ceremony.
-
Goal diagram
A goal diagram shows a process goal, its decision points and the options for each, with an arrow beside lists whose options are ordered by effectiveness.
- Remember
- The arrow means options toward the top are generally more effective, not that only the top option is acceptable.
- Tested as
- Used to test whether you can read DA guidance and pick a realistic next step.
- Trap
- Assuming every list is ordered; options without an arrow are alternatives with no ranking.
-
DA lifecycles
DA Delivery offers six lifecycles: Agile (Scrum-based), Lean (Kanban-based), Continuous Delivery: Agile, Continuous Delivery: Lean, Exploratory (Lean Startup style) and Program (a team of teams).
- Remember
- Lifecycles are starting points chosen for context, and a team can move from one to another as it matures.
- Tested as
- Scenarios describe a work pattern and ask which lifecycle fits it best.
- Trap
- Choosing Agile for unpredictable, continuously arriving work where Lean fits better.
-
Phases and milestones
DA delivery lifecycles run through Inception, Construction and Transition, with risk-based milestones such as Stakeholder Vision, Proven Architecture, Continued Viability, Sufficient Functionality and Production Ready.
- Remember
- Milestones reduce risk and support lightweight governance; they are not phase-gate document sign-offs.
- Tested as
- Governance questions ask which milestone confirms that the team should keep going or that the architecture works.
- Trap
- Equating Inception with a long upfront requirements phase; DA keeps it short, often a week or two.
-
Guided continuous improvement (GCI)
GCI is a team improving its WoW through small experiments, using the DA toolkit to find options likely to work instead of trial and error alone.
- Remember
- Identify a problem, choose a candidate option from the toolkit, try it, measure, then keep or drop it.
- Tested as
- The default answer when a team wants to fix a process problem.
- Trap
- Choosing a big-bang process overhaul when a targeted experiment would do.
-
Enterprise awareness
This principle says teams act in the interest of the whole organization, reusing existing assets, following shared guidance and working with enterprise groups such as architecture and finance.
- Remember
- Team autonomy sits inside organizational guardrails.
- Tested as
- Appears when a team's local optimization would harm other teams or ignore shared standards.
- Trap
- Treating any shared standard as a violation of team self-organization.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Principles vs. promises vs. guidelines
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Principles | The eight philosophical foundations of the DA mindset, such as context counts and optimize flow | State why DA works the way it does | Listing 'make all work visible' as a principle; it is a promise |
| Promises | Seven commitments a team makes to the people it works with, such as keep workloads within capacity | Describe behaviors others can rely on | Treating promises as optional advice |
| Guidelines | Eight practical recommendations, such as validate our learnings and adopt measures to improve outcomes | Advise how to act on the principles and promises | Confusing a guideline with a mandatory rule |
Prescriptive framework vs. DA decision framework
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Prescriptive framework (for example, Scrum) | Defines specific roles, events and artifacts to adopt | Tells the team what to do | Thinking DA rejects Scrum; DA's Agile lifecycle builds on it |
| DA decision framework | Lays out decisions, options and trade-offs drawn from many sources | Helps the team decide what to do in its context | Expecting DA to name one correct practice for every situation |
Agile vs. Lean lifecycle
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Agile lifecycle | Iteration-based, building on Scrum, with planning and demos each iteration | Work is batched into time-boxes | Using it where work arrives unpredictably and cannot wait for the next iteration |
| Lean lifecycle | Flow-based, building on Kanban, pulling work as capacity frees up within work-in-progress (WIP) limits | No iterations; ceremonies happen when needed | Assuming Lean means no planning or no cadence at all |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Standardize every team
- What candidates pick
- Mandating one process across all teams for consistency.
- Why it looks right
- Consistency sounds efficient and easier to govern.
- Why it's wrong
- Context counts and choice is good: identical processes ignore real differences in team size, work type and constraints.
Clue to watch for The scenario mentions teams with different kinds of work or constraints; govern outcomes, not practices.
-
Purist agile answer
- What candidates pick
- Dropping a compliance artifact because 'agile values working software over documentation'.
- Why it looks right
- It quotes familiar agile language.
- Why it's wrong
- Be pragmatic: a regulatory need is part of the context, and DA expects the team to meet it efficiently, not ignore it.
Clue to watch for Words like audit, regulator or compliance mean the constraint stays.
-
Top option only
- What candidates pick
- The most advanced option in a goal diagram for a team just starting out.
- Why it looks right
- The arrow says it is the most effective.
- Why it's wrong
- More effective options are often harder to adopt; DA expects a team to start where it can succeed and improve over time.
Clue to watch for The team is new, lacks the skills, or has tooling gaps.
-
Big-bang process change
- What candidates pick
- Replacing the whole WoW after one bad retrospective.
- Why it looks right
- It looks decisive.
- Why it's wrong
- Guided continuous improvement favors one targeted experiment at a time so the team can see what works.
Clue to watch for A single, specific problem is named; address that problem.
-
Autonomy without guardrails
- What candidates pick
- Letting a team ignore an enterprise architecture standard because teams self-organize.
- Why it looks right
- Self-organization is a core agile idea.
- Why it's wrong
- Enterprise awareness means teams work within organizational guardrails and reuse existing assets.
Clue to watch for Another team, shared platform or enterprise group is affected by the decision.
-
Lifecycle as permanent
- What candidates pick
- Keeping the Agile lifecycle after the team's work becomes a steady stream of small requests.
- Why it looks right
- The team already knows the iteration rhythm.
- Why it's wrong
- Lifecycles are starting points; when context changes, moving to the Lean lifecycle may fit better.
Clue to watch for The scenario says the nature of incoming work has changed.
Answer framework
Use this sequence whenever a DA overview question asks what a team or leader should do about its way of working.
- Identify the team's context first: size, distribution, work type, skills and any regulatory or enterprise constraint named in the scenario.
- Name the DA principle at stake, usually context counts, choice is good, be pragmatic or enterprise awareness.
- Find the decision the team faces and treat the available answers as options with trade-offs, not as right and wrong rules.
- Prefer the option the team can adopt now that moves it toward a more effective practice, rather than the most advanced option.
- Reject answers that mandate one process for everyone, ignore a stated constraint, or overhaul the whole WoW when one targeted experiment would do.
Practice question
Want more like this? The DASM practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the mindset, because every later module assumes it. Learn the eight principles first, then the seven promises, then the eight guidelines, and for each one write a single sentence describing a team behavior that shows it. Being able to go from behavior to principle is more useful than reciting the lists.
Next, study the decision-framework structure: process goal, decision point, option, trade-off. Pick one goal diagram in the DA Browser, such as Improve Quality, and read it end to end, noticing which option lists carry an ordering arrow and which do not. Then learn the six lifecycles as answers to the question 'what kind of work does this team do?' rather than as diagrams to memorize.
Commonly underestimated areas are enterprise awareness, which limits autonomy, and be pragmatic, which can make a less 'agile' option correct. Afterwards, practice short scenarios that ask for the BEST next step, and explain to yourself which principle rules out each wrong answer before moving on to the knowledge base module.
FAQ
Is Disciplined Agile a replacement for Scrum?
No. DA is a toolkit that includes Scrum practices, notably in its Agile lifecycle, alongside Kanban, XP, Lean and others. It helps a team decide when Scrum practices fit and what to add or change.
How much weight does this module carry?
PMI does not publish module weights, and its DASM page now describes an eLearning course without a listed exam. The ideas in this module still underpin every scenario in the later modules.
Do I need to memorize all the principles, promises and guidelines?
You should know the eight principles well enough to match a behavior to each one, and recognize the promises and guidelines. Matching is what scenarios test, not recitation.
What does 'choose your WoW' mean in practice?
A team picks a starting lifecycle and practices that suit its context, then keeps improving them through small experiments. It does not mean starting from a blank page every time.
Does DA allow organization-wide standards?
Yes. Enterprise awareness means teams work within guardrails such as security, architecture or compliance standards. DA objects to mandating identical practices, not to shared outcomes and constraints.
What kind of questions should I expect on this module?
Short scenarios that ask which principle applies, the BEST response to a process mandate, or which lifecycle is the most appropriate starting point for a described team.
How long should I spend here?
Plan for about two to three hours, including reading one goal diagram end to end. It is time well spent because later modules reuse this vocabulary constantly.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
Test your Domain 1 knowledge
You have just worked through the DA mindset, the decision framework and how a team chooses its lifecycle. Check whether you can apply them to short team scenarios.