Free DASSM Practice Test Questions and Answers (2026)

The architecture owner leads architectural evolution, coaching, roadmap collaboration, and product supportability, but people performance management and rewards remain a line-management/HR responsibility, not that of the architecture owner.

A. Collaborative creation of the technical roadmap is an explicit architecture-owner duty.
B. Coaching on sound technical practices is part of the role’s leadership remit.
C. Supportability improvements fall under owning the architecture’s quality attributes.
E. Continuously evolving design/architecture is the core purpose of the role.

1. Ambler, S.; Lines, M. “Choose Your WoW!”, 2019, ch. 3 “People-First”, p. 121-123 (Architecture Owner responsibilities list).

2. University of Waterloo SE 690 course notes “Disciplined Agile Roles”, Winter 2021, slide 15.

When altering legacy code, the safest disciplined practice is to erect a characterization test first to lock in existing behaviour, then make the code change. This protects against unintended regressions and provides feedback for future refactoring. The practice draws on test-driven development principles and is explicitly advocated in Disciplined Agile’s technical excellence guidelines for sustaining quality in ageing code bases.

B. Wholesale rewrites are costly and risk recreating existing defects.
C. Delegating does not address safety or quality and evades responsibility.
D. Changing first removes the safety net and may inject regressions before tests exist.

1. PMI, “Choose Your WoW!” (2019), Sec. 8.5 Technical Excellence, “Safely Evolve Legacy Code”, p. 231.

2. Feathers, M. “Working Effectively with Legacy Code” (Prentice-Hall, 2004), Ch. 1, pp. xxvi-xxvii.

3. MIT OCW 6.005 “Software Construction”, Lec. 16 Legacy Code, slides 5-7.

In DA, governance supplies lightweight oversight—allocating funds, ensuring compliance, rewarding people, sharing knowledge, and defining decision processes. Granting a team “complete freedom” would eliminate necessary oversight and therefore is not part of governance.

A. Communities and forums are cited as governance enablers for knowledge sharing.
B. Governance boards decide on investment and funding.
C. Recognition systems are a people-governance responsibility.
E. Regulatory compliance is a core governance objective.
F. Explicit decision-making processes are a standard governance element.

1. PMI. Choose Your WoW, 2019, §17.3 “Lightweight Governance”, pp. 401-402.

2. PMI. Disciplined Agile Value Stream Consultant Guide, 2021, Ch. 8, pp. 146-148.

In Disciplined Agile, the entire team is accountable for delivering a quality solution in a timely manner. While roles like the Product Owner are accountable for maximizing value and the Team Lead for facilitating the process, the commitment to deliver the work is made by the team as a whole. Among the given choices, "Team members" best represents the collective group responsible for executing and delivering the committed work. They are the ones performing the tasks and are therefore directly accountable for the delivery of the product increment.

A. The Product Owner is accountable for maximizing the value of the product, not the timeliness of the team's delivery commitment.
B. The Team Lead is a servant leader, accountable for guiding the team in choosing their Way of Working (WoW), not for the delivery itself.
D. A Gold User is a stakeholder who provides feedback; they are not part of the delivery team and hold no accountability for delivery.
E. The Architecture Owner is accountable for guiding the team to a viable technical strategy, not for the overall product delivery timeline.

1. Ambler, S., & Lines, M. (2020). Choose Your WoW!: A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working. Project Management Institute. (p. 29, "The team is accountable to its stakeholders for delivering quality solutions in a timely manner.")

2. Project Management Institute. (2017). The DSDM Agile Project Framework Handbook. (Principle 4: Never Compromise Quality, which implies the team's accountability for the delivered product). Note: DSDM is a source for DA.

The DA Lean life cycle is a Kanban-based, continuous-flow approach. Work is pulled through the value stream as capacity is available; therefore, it explicitly operates without fixed-length, time-boxed iterations.

B. False – Contradicts DA guidance; Lean life cycle dispenses with iteration timeboxes in favour of flow pull.

1. PMI, Choose Your WoW!, 1st ed., 2019, p. 74-75 “Lean life cycle (continuous flow)”.

2. PMI, DASSM Courseware v2.0, Module 5, slide 9 “Lean/Kanban life cycle – no iteration timeboxes”.

Transparency in DA is practiced to foster trust, keep everyone informed, and boost morale. Delaying bad news is the antithesis of transparency, so option C is not a reason DA teams practice it.

A. Transparency ensures stakeholders “know what is happening,” matching DA principles.
B. Open information flow increases psychological safety and morale.
D. DA recognizes customers value and expect high transparency from delivery teams.

1. Ambler & Lines, “Choose Your WoW!”, PMI, 2020, p. 55 – Principle “Be open and honest” lists stakeholder awareness and morale benefits.

2. PMI DASSM Courseware v2.1, Module 3 “DA Mindset”, slide 11 – Customers expect transparency; hiding issues contradicts DA values.

3. Ambler & Lines, “Disciplined Agile Delivery: A Practitioner’s Guide”, 2012, p. 45 – Transparency improves trust and morale.

In Disciplined Agile, the process goal “Accelerate Value Delivery” is explicitly flagged as one that “will normally require significant tailoring” because teams must choose among a large set of decision points—e.g., limit work-in-process, manage queues, optimise cycle time, automate deployment, exploit DevOps practices, and many others. This breadth of choices makes it the goal that typically needs the most fine-tuning for a given context, more so than the other options shown.

A. Form team – Labelled “minimal tailoring likely”; decisions are generally one-time and straightforward.
B. Prove architecture early – Only moderate tailoring; comparatively few decision points.
D. Improve quality – Moderate tailoring; decision set is smaller and well-defined.

1. PMI. “Choose Your WoW!”, 1st ed., 2019, pp. 310-317 (“Accelerate Value Delivery” – banner: “Significant tailoring likely”).

2. PMI. DASSM Courseware v1.2, Module 3 “Process Goals & Decision Points”, slides 32-36 (tailoring levels table).

3. Ambler, S.W. & Lines, M. “Disciplined Agile Delivery: A Practitioner’s Guide”, Addison-Wesley, 2012, Ch. 19 (tailoring indicators).

Disciplined Agile recommends long-lived, stable product teams because they retain domain knowledge, minimize team-forming costs, and sustain flow of value over multiple releases, unlike temporary ad-hoc or project teams. (Choose Your WoW!, pp. 47-48; DA Principle “Organize Around Products/Services”.)

B. False – Project-based, short-lived teams incur repeated forming-storming costs and knowledge loss, decreasing throughput and quality.

• PMI. Choose Your WoW!, 2019, pp. 47-48 (“Stable Product Teams”).

• Ambler, S.; Lines, M. Disciplined Agile Delivery (2nd ed.), 2017, pp. 38-39 (long-standing teams benefits).

• MIT Sloan Course 15.351, “Managing Innovation Teams,” Lecture 3 slides, p. 6 (evidence on stable team performance).

In the DA toolkit, the Marketing process blade defines strategies and activities for positioning offerings and communicating with the external marketplace, ensuring effective interactions between the organization and its customers. (Choose Your WoW!, p. 350; DA Browser “Marketing” process blade overview.)

A. Portfolio management – prioritizes investment mix; it does not focus on external communications.
B. Product Management – owns product vision and roadmap; external promotion is delegated to Marketing.
C. Sales – executes transactions and manages accounts, not overarching market-interaction strategy.
D. Business Operations – concerns internal service delivery and support, not market outreach.

• PMI. Choose Your WoW!, 2019, pp. 350-352 (“Marketing Process Blade”).

• PMI DA Browser v5.3, “Marketing” summary, sect. Purpose.

• Ambler, S.; Lines, M. An Executive’s Guide to Disciplined Agile, 2020, p. 78 (interaction with marketplace via Marketing).

Traditional procurement frameworks assume fixed scope, long lead-times and sequential hand-offs; this lack of agility clashes with iterative delivery cadences, creating the chief procurement pain point for agile teams.

B. Vendor non-compliance can occur but is not cited in DA as the principal systemic issue.
C. DA teams collaborate with internal or external partners; no inherent preference for in-house only.
D. Contracting is still essential; DA describes several agile-compatible contract styles.

1. PMI. DASSM Participant Guide v1.1 (2021) Lesson 4, p. 62 – “A primary challenge is that existing procurement processes are not agile enough.”

2. Ambler, S. & Lines, M. Choose Your WoW! (PMI, 2019) Chap 13, p. 302 – Misalignment of traditional sourcing processes with iterative delivery.

Disciplined Agile Delivery defines twenty-one process goals mapped to life-cycle phases. During the Construction phase the primary architectural risk must be addressed; therefore “Prove Architecture Early” is a Construction-phase goal. It drives rapid spikes and prototypes once initial design is in place to secure viability before full-scale build. The other listed goals belong to Inception, not Construction.

B. “Explore Scope” is an Inception-phase goal (requirements framing).
C. “Develop Test Strategy” is an Inception-phase goal (quality planning).
D. “Form Team” is an Inception-phase goal (staffing and chartering).

1. Ambler, S. & Lines, M. Choose Your WoW!, PMI, 2019, fig. 6.1 & pp. 102-104 (Construction goals; “Prove Architecture Early”).

2. PMI. Disciplined Agile Delivery—Process Goals Overview poster, 2020 revision, column “Construction”.

“Context counts” is a core DA principle that instructs teams to tailor their way of working to their unique situation. Because this co-located team found that a daily stand-up added no value, skipping it exemplifies applying context-sensitive tailoring.

A. Being awesome – Principle concerns fostering a joyful, safe culture, not meeting selection.
B. Enterprise awareness – About optimizing for the broader organization, not local ceremony value.
D. Choice is good – Recognises having options, but the decisive factor here is contextual suitability, represented directly by C.

1. PMI, Choose Your WoW!, 1st ed., 2019, §3 “DA Mindset”, p. 35 “Context counts”.

2. PMI, DASSM Courseware v2.0, Module 1, slide 18 “Tailor events to context”.

Long-lived (stable) teams foster deep, sustained collaboration and psychological safety, enabling members to build trust and leverage shared knowledge—key drivers of higher performance in Disciplined Agile and Lean thinking.

A. “Projectized” reflects short-term team assembly; stability seeks the opposite.
B. Being “specifically resourced” describes staffing precision, not an inherent benefit.
E. Multi-tasking usually harms focus and flow; stable teams aim to minimize it.

1. Ambler, S.; Lines, M. “Choose Your WoW!”, 2020, Sec. 5.2, pp. 70-72 (Benefits of stable teams: trust, collaboration).

2. MIT Sloan, “Stable Teams and Performance” lecture notes 15.564, 2019, slide 12 (Trust & collaboration gains).

DA leadership is servant-oriented; a lead first engages the struggling member in an open conversation to uncover impediments and co-create ways forward, enabling the person and preserving team self-management.

A. Training may help later, but prescribing it without understanding root causes violates DA’s “Context Counts” principle.
C. Framing the issue as “failures” discourages psychological safety and learning.
D. Reassigning work without dialogue masks symptoms and hinders the member’s growth, contradicting DA’s “people-first” mindset.

1. Ambler, S.; Lines, M. “Choose Your WoW”, PMI Press, 2020, p. 26 (Servant Leadership, Build Empathy).

2. PMI. “DASSM Participant Guide”, v1.1, 2022, Module 2, slide 20 (Principle: Enable People to Own Their Process).

The DA principle “Be awesome” directs leaders to cultivate psychological safety, respect, and collaboration so the team can excel—exactly what the team lead is doing by building a cohesive, high-performing unit.

B. “Choice is good” is about providing many practices, not teamwork.
C. “Context counts” concerns situational tailoring, not team bonding.
D. “Optimize around products/services” focuses on value-stream alignment, not collaboration.
E. “Delight customers” stresses external value, not internal team dynamics.

1. PMI. Disciplined Agile Principles Poster, 2021, Principle 1 “Be awesome”.

2. Ambler & Lines. Choose Your WoW, 2019, pp. 19-20 (Principle descriptions).

All Disciplined Agile lifecycles—including Scrum-based and Agile—explicitly contain the three DAD phases: Inception (getting started), Construction (producing increments), and Transition (releasing). The internal cadence may vary, but the phases still exist conceptually.

B. Eliminating Inception or Transition ignores DAD’s phased delivery model adopted by Scrum/Agile lifecycles within DA.

1. PMI, Choose Your WoW!, 1st ed., 2019, Fig. 3-2 “Agile Lifecycle Phases”, p. 51.

2. Ambler, S.; Lines, M., Disciplined Agile Delivery, Pearson, 2012, Ch. 9, pp. 153-155.

The retrospective is a structured inspect-and-adapt event where the team reflects on its recent collaboration and delivery process, identifies improvement actions, and agrees on concrete experiments to enhance future teamwork and performance.

B – The Product Owner participates but the ceremony’s goal is team improvement, not evaluation by PO. C – Stakeholder requests are discussed during the Review; retrospectives do not prohibit new ideas. D – Backlog organization (story-mapping, prioritization) happens in refinement sessions, not in retrospectives.

1. PMI. “Choose Your WoW!”, Ch. 13.6 Retrospective, pp. 226-228, 2019.

2. PMI. “DASM Student Guide”, Lesson 6, Slide 14, 2021.

Guided Continuous Improvement (GCI) is DA’s practice of using the toolkit’s proven options to steer teams toward safe-to-try enhancements and away from high-risk experiments. GCI becomes essential when a team actively seeks help in discovering feasible improvement choices and wants empirical guidance on which alternatives carry unacceptable risk. In that situation GCI supplies decision filters and comparative trade-off data neither improvisation nor mere retrospection can provide, maximizing learning while minimizing failure cost.

A. No more opportunities left negates the premise of continuous improvement.
B. Method prison describes rigid adherence; GCI can help, but it is not the essential indicator.
D. Inability to find any ideas suggests coaching need, not specifically GCI’s option-filtering strength.

1. Ambler, S. & Lines, M. Choose Your WoW!, PMI, 2019, ch.3, pp. 35-38 (“Guided Continuous Improvement”).

2. Ambler, S. Disciplined Agile—Foundations eLearning, Lesson 4, slide “Why Guided Improvement?”.

3. Ambler, S. & Lines, M. Introduction to DA, PMI webinar 2021, time-stamp 18:40-20:05 (risk-reduction focus of GCI).

In Lean thinking, managers’ prime responsibility is to create and maintain an environment where people and teams can excel—removing impediments, enabling flow, and fostering respect and continuous improvement.

A. Documentation is a by-product; Lean minimizes unneeded docs.
B. MVPs are produced by teams, not supplied by managers.
D. Lean promotes decentralized decision-making closest to the work, not centralized regional control.

1. Womack, J.; Jones, D. “Lean Thinking,” 2nd ed., 2003, Ch. 7, pp. 230-233 (Management creates enabling environment).

2. Ambler, S.; Lines, M. “Choose Your WoW!”, 2020, Sec. 3.3, p. 55 (“Management’s role is to create an environment where people can be awesome”).

In Disciplined Agile, a Minimum Business Increment (MBI) is the smallest slice of functionality that delivers recognizable value to existing customers and can be released independently. When enhancing a mature product, MBIs let teams release discrete, value-focused changes without disrupting the whole system—more suitable than MVP, which targets brand-new products.

A. Continuous integration is a build practice, not a value-slicing technique.
B. A pull system governs work intake flow, not feature definition.
D. MVP validates new-product hypotheses; for established products, MBI is recommended.

1. PMI / Ambler & Lines, Choose Your WoW! 2nd ed., 2023, §6.3, p. 153: distinguishes MBI from MVP, recommending MBI for existing products.

2. PMI DASSM Courseware v3.0, Module 5, slides 12-13: “Use MBIs to add features to a stable product.”