Courseiva

Disciplined Agile Foundations (DAF, PMI-authorized, replaces the retired DASM) (DAF) (DAF) — Questions 1–75

213 questions total · 3 pages · All types, answers revealed

Take a mock examExam hub

Page 1 of 3

Page 2
1
MCQmedium

You are assessing team performance. Which DA concept emphasizes that there is no 'one size fits all' approach?

A.Enterprise Awareness
B.Choice is Good
C.Context Counts
D.Optimizing Flow
AnswerC

Context Counts captures the Disciplined Agile principle that teams must tailor their way of working to their own situation, so no single prescribed method fits every team. This directly satisfies the stem's requirement for a concept rejecting a one-size-fits-all approach to assessing performance.

Why this answer

The DA concept 'Context Counts' emphasizes that there is no one-size-fits-all approach; teams must tailor their way of working to their specific context. This principle is central to DA, which rejects prescriptive methods and encourages teams to choose practices that fit their situation. Therefore, 'Context Counts' is the correct answer.

Exam trap

The trap is that candidates might confuse 'Context Counts' with 'Choice is Good' because both relate to flexibility, but 'Context Counts' specifically addresses the no-one-size-fits-all principle.

How to eliminate wrong answers

Option A is wrong because 'Enterprise Awareness' is about understanding the broader organizational ecosystem, not about tailoring to context. Option B is wrong because 'Choice is Good' is a related principle that supports having options, but it does not directly emphasize that context determines the best choice. Option D is wrong because 'Optimizing Flow' is about improving the flow of value delivery, not about the no-one-size-fits-all idea.

Full explanation →
2
MCQeasy

Which of the following best describes the 'Disciplined Agile Mindset' regarding process?

A.Be pragmatic and choose your way of working (WoW)
B.Copy the processes of the most successful competitors
C.Follow the Scrum guide verbatim
D.Focus exclusively on speed of delivery
AnswerA

The Disciplined Agile Mindset holds that teams should be pragmatic, choosing and evolving their way of working to fit context rather than adopting one prescribed process. This satisfies the stem by describing the mindset's stance that process should be tailored, not mandated.

Why this answer

The Disciplined Agile Mindset is built on principles such as 'Be Pragmatic', 'Choose Your WoW', and 'Deliver Consumable Solutions'. Regarding process, the mindset explicitly states that teams should be pragmatic and choose their way of working (WoW) — tailoring practices to their context rather than adopting a one-size-fits-all method. This is the core of DA's philosophy.

Exam trap

DAF often tests the misconception that DA is just another prescriptive framework like Scrum — candidates pick 'follow the Scrum guide verbatim' or 'copy competitors', missing that DA's defining feature is pragmatic, context-driven tailoring of the WoW.

How to eliminate wrong answers

Option B is wrong because copying competitors' processes ignores context — what works for one organisation may fail in another due to different culture, scale, or constraints, and DA explicitly rejects cookie-cutter adoption. Option C is wrong because following the Scrum guide verbatim is prescriptive and contradicts DA's 'Choose Your WoW' principle — DA draws from Scrum, Kanban, SAFe, and others but expects teams to tailor. Option D is wrong because focusing exclusively on speed of delivery ignores DA's balanced focus on value, quality, and sustainability — speed at the expense of quality or team health is an anti-pattern.

Full explanation →
3
MCQmedium

What is the primary benefit of 'Standardized Work' in a Lean environment?

A.It creates a baseline for improvement.
B.It reduces the need for skilled workers.
C.It eliminates the need for team collaboration.
D.It makes the work boring and repetitive.
AnswerA

Standardised work establishes the current best-known method as a documented baseline, making deviations visible so kaizen can target them. Without this agreed reference, improvements cannot be measured or sustained. It satisfies the stem's requirement for the primary benefit: a stable foundation against which every subsequent process change is compared and refined.

Why this answer

Standardized work provides a consistent baseline, which is necessary for measuring the impact of improvements (Kaizen).

Full explanation →
4
MCQhard

You are managing a program that spans multiple DA teams. Which process blade helps manage the dependency between these teams?

A.Team Development
B.Product Management
C.Coordinate Activities
D.Governance
AnswerC

Coordinate Activities is the process blade explicitly addressing how multiple teams align shared work, manage cross-team dependencies and resolve inter-team issues. It satisfies the stem's constraint of managing dependencies across several DA teams within one program.

Why this answer

In Disciplined Agile, the Coordinate Activities process blade exists specifically to manage dependencies, risks, and coordination across multiple teams, including across the enterprise. When a program spans multiple DA teams, Coordinate Activities provides the guidance for aligning their work, resolving cross-team dependencies, and coordinating releases — making it the correct blade for managing inter-team dependencies.

Exam trap

DAF often tests confusion between Team Development (single-team growth) and Coordinate Activities (multi-team dependency management) — candidates pick Team Development because 'coordination' sounds like a team activity, missing that the question specifies multiple teams.

How to eliminate wrong answers

Option A is wrong because Team Development focuses on growing the skills, culture, and effectiveness of a single team, not on coordinating work between multiple teams. Option B is wrong because Product Management is concerned with the product vision, backlog, and stakeholder value — it does not own cross-team dependency management. Option D is wrong because Governance addresses decision-making, compliance, and oversight structures (such as the IT governance framework), not the day-to-day coordination of dependencies between delivery teams.

Full explanation →
5
MCQmedium

Your team is currently struggling with high levels of work-in-process (WIP) that is causing delays. According to the Choose Your Way of Working (WoW) mindset, what is the first step you should take?

A.Stop all work until the backlog is re-prioritized.
B.Analyze the 'Coordinate Activities' process goal and select a practice to limit WIP.
C.Ask management to hire more staff to handle the current WIP.
D.Adopt a full Scrum framework immediately.
AnswerB

The Choose Your Way of Working mindset starts from the process goal, not the symptom. Analysing 'Coordinate Activities' and selecting a practice that explicitly limits WIP addresses the root cause of the delays, rather than applying an unaligned local fix.

Why this answer

According to the Choose Your Way of Working (WoW) mindset, when facing high WIP, the first step is to analyze the 'Coordinate Activities' process goal and select a practice to limit WIP. This goal addresses how teams coordinate their work, and limiting WIP is a key strategy to improve flow and reduce delays. The team should then choose a practice, such as Kanban's WIP limits, to address the issue.

Exam trap

DAF often tests the tendency to jump to solutions like hiring or adopting a framework without first analyzing the relevant process goal and selecting a tailored practice.

How to eliminate wrong answers

Option A is wrong because stopping all work is drastic and not a first step; it can be disruptive. Option C is wrong because hiring more staff may not address the root cause and can increase WIP further. Option D is wrong because adopting full Scrum immediately is not a targeted response; Scrum may not directly address WIP limits without additional practices.

Full explanation →
6
MCQeasy

A newly formed product team is deciding how to organize its work. The team lead suggests adopting a 'flow-based' strategy where work items are pulled continuously rather than committed to fixed-length iterations. Which Disciplined Agile principle best supports this choice?

A.Deliver value continuously by optimizing flow and eliminating waste.
B.Maximize utilization of all team members at all times.
C.Prefer predictive planning to reduce uncertainty.
D.Follow a single prescribed process for all teams.
AnswerA

This principle directly endorses continuous delivery and flow optimization, which aligns with pulling work as capacity allows. It is a core DA principle that guides teams to choose lifecycle approaches based on context, not dogma. The scenario's flow-based strategy is a valid DA way of working, so this principle is the best fit.

Why this answer

The team is choosing a flow-based strategy, which is one of several valid DA lifecycles. The principle of delivering value continuously and optimizing flow supports this choice, as it emphasizes pull systems, waste elimination, and adaptability. The other options reflect anti-patterns or misapplications of DA, such as over-planning, over-utilization, or rigid process adherence.

Exam trap

The trap here is assuming that DA mandates a specific lifecycle, when in fact it encourages teams to choose the approach that best fits their context.

Full explanation →
7
MCQeasy

What is the main benefit of having a 'cross-functional' team?

A.They work faster than specialized teams
B.They reduce dependencies on other teams
C.They can work on more projects at once
D.They don't need a team leader
AnswerB

Cross-functional teams hold all skills needed to deliver end-to-end, so they satisfy the stem by reducing dependencies on external teams. This cuts handoffs and waiting, letting the team complete work without queuing for specialist resources elsewhere.

Why this answer

A cross-functional team contains all the skills needed to deliver a working increment — analysis, development, testing, design, and often ops — so it does not have to wait on external specialists to complete its work. This directly reduces dependencies on other teams, which is the primary structural benefit in Disciplined Agile and other agile frameworks. Fewer handoffs means shorter feedback loops and less coordination overhead.

Exam trap

DAF often tests whether candidates confuse cross-functionality (skill coverage reducing dependencies) with speed or multi-tasking benefits — the exam wants the dependency-reduction rationale, not a productivity claim.

How to eliminate wrong answers

Option A is wrong because cross-functional teams are not inherently faster than specialized teams — specialization can be faster for narrow tasks; the benefit is autonomy and reduced handoffs, not raw speed. Option C is wrong because a cross-functional team is typically focused on one product or value stream, not juggling more projects; in fact, spreading a team across projects undermines the model. Option D is wrong because cross-functional teams still need leadership, coaching, and self-organization guidance — being cross-functional does not eliminate the need for a team leader or Scrum Master.

Full explanation →
8
MCQhard

During a release planning session, the stakeholders insist on a fixed-scope, fixed-date delivery. As a DA practitioner, how should you respond to this 'iron triangle' request?

A.Report the project as failing because it cannot be purely agile.
B.Accept the constraints and reduce the testing phase duration to meet the date.
C.Educate stakeholders on the tradeoffs by using a 'Range-Based' planning approach to show how scope can be flexed to hit the date.
D.Explain that agile methods do not allow for deadlines.
AnswerC

Range-based planning quantifies uncertainty by estimating scope in ranges rather than fixed points, exposing the schedule-scope tradeoff the stakeholders' fixed-date constraint creates. Educating them this way lets the team flex scope to protect the release date, satisfying the stem's fixed-date requirement while keeping delivery realistic.

Why this answer

As a DA practitioner, when stakeholders insist on fixed-scope, fixed-date delivery, the correct response is to educate them on the tradeoffs using a 'Range-Based' planning approach. This approach shows how scope can be flexed (e.g., using a minimum viable product or prioritised backlog) to meet the date, while maintaining quality and avoiding the pitfalls of the iron triangle.

Exam trap

DAF often tests the misconception that Agile cannot handle fixed dates or that the only response is to compromise quality — the trap is selecting an answer that either rejects the constraint outright or sacrifices testing/quality, rather than using range-based planning to flex scope.

How to eliminate wrong answers

Option A is wrong because reporting the project as failing is defeatist and incorrect — DA is pragmatic and can operate within constraints by adjusting other variables (scope, quality, or cost) rather than declaring failure. Option B is wrong because reducing testing duration to meet the date compromises quality and is a classic iron triangle mistake — DA would not sacrifice quality without explicit tradeoff discussions. Option D is wrong because Agile methods do allow for deadlines; they simply advocate for flexibility in scope or quality to meet them, and DA specifically provides guidance on how to handle fixed-date scenarios.

Full explanation →
9
MCQmedium

What is the primary purpose of 'Little's Law' in Lean?

A.To measure individual developer productivity.
B.To relate WIP, Throughput, and Cycle Time mathematically.
C.To determine the number of staff members needed.
D.To calculate the total project budget.
AnswerB

Little's Law states that average cycle time equals work in progress divided by throughput, giving a mathematical relationship between these three Lean metrics. This satisfies the stem by explaining the law's primary purpose: quantifying how WIP and throughput determine cycle time.

Why this answer

Little's Law states that the average number of items in a queuing system (WIP) equals the average arrival rate (Throughput) multiplied by the average time an item spends in the system (Cycle Time): WIP = Throughput × Cycle Time. In Lean and Kanban, this relationship is used to predict how reducing WIP or increasing throughput affects cycle time, making it a foundational flow metric.

Exam trap

DAF often tests the misconception that Little's Law measures individual productivity or staffing — candidates who pick 'measure developer productivity' confuse a system flow equation with a performance metric.

How to eliminate wrong answers

Option A is wrong because Little's Law is a system-level flow equation, not a measure of individual productivity — using it to evaluate individuals is a misuse and contradicts Lean's respect-for-people principle. Option C is wrong because staffing decisions involve capacity planning, skills, and cost factors; Little's Law relates flow variables, not headcount. Option D is wrong because budget calculation is a financial planning activity unrelated to the WIP/Throughput/Cycle Time relationship that Little's Law describes.

Full explanation →
10
MCQmedium

A team needs to improve their quality. Which process blade would provide the best guidance?

A.Quality Management
B.Coordinate Activities
C.Team Development
D.Financial Management
AnswerA

Quality Management provides guidance on quality strategies, testing approaches, and practices such as continuous integration and defect prevention. It directly satisfies the stem's requirement for the process blade offering the best guidance when a team needs to improve its quality.

Why this answer

The Quality Management process blade in Disciplined Agile provides guidance on quality strategies, practices, and techniques across the lifecycle, including test-driven development, continuous integration, code reviews, and defect prevention. When a team's goal is to improve quality, this is the blade explicitly designed to address that concern.

Exam trap

DAF often tests whether candidates can map a stated team problem to the correct process blade — quality issues map to Quality Management, not to coordination, team development, or financial blades that sound plausible but address different concerns.

How to eliminate wrong answers

Option B is wrong because Coordinate Activities focuses on how teams coordinate work and dependencies (e.g., coordination meetings, DevOps alignment), not on quality practices themselves. Option C is wrong because Team Development addresses growing team skills, roles, and interpersonal dynamics, which supports quality indirectly but does not provide quality-specific guidance. Option D is wrong because Financial Management covers budgeting, costing, and funding models, which are unrelated to improving product or process quality.

Full explanation →
11
MCQhard

You are analyzing why a project failed to deliver value. Which DA concept should you apply for post-mortem?

A.Blame the developers
B.Change all team members
C.Apply the 'Improve Process' goal
D.Restart the project with a new lead
AnswerC

Applying the 'Improve Process' goal fits a post-mortem because it examines how delivery work was planned and executed, surfacing the process failures that blocked value. Unlike product-focused goals, it targets the workflow itself, satisfying the stem's requirement to diagnose why the project failed to deliver value.

Why this answer

DA's 'Improve Process' goal is the framework's mechanism for retrospectives and process improvement, making it the right concept to apply when analyzing why a project failed to deliver value. It guides the team to inspect what happened, identify root causes, and adapt their way of working. This is a blameless, systems-thinking approach rather than a people-focused one.

Exam trap

DAF often tests whether candidates default to blame-oriented or restart-oriented responses instead of recognizing that DA's Improve Process goal is the correct, blameless, systems-thinking mechanism for post-mortem analysis.

How to eliminate wrong answers

Option A is wrong because blaming developers is a counterproductive, non-DA response that ignores systemic causes and destroys psychological safety. Option B is wrong because changing all team members is a disruptive, blame-oriented action that does not address the underlying process or environmental issues. Option D is wrong because restarting the project with a new lead is a costly, non-learning response that discards the opportunity to improve the way of working based on evidence.

Full explanation →
12
MCQmedium

When a team is working on multiple projects, what is the impact on their productivity?

A.It allows for better utilization of team members
B.It is the standard way of working in DAD
C.It increases the risk of delay and quality issues due to context switching
D.It increases their total output
AnswerC

Context switching between projects imposes cognitive reload costs and fragments focus, directly reducing throughput. Because attention must repeatedly reorient to different goals, specifications and stakeholders, the likelihood of errors rises and schedules slip. This satisfies the stem's productivity constraint by identifying the mechanism through which multitasking degrades both delivery speed and output quality.

Why this answer

When a team works on multiple projects simultaneously, context switching between different domains, stakeholders, and technical stacks degrades productivity. DA explicitly warns against this and recommends limiting work in progress so teams can focus on one primary initiative at a time. The result of over-allocation is longer cycle times, more defects, and higher risk of delay.

Exam trap

DAF often tests the myth that multi-project allocation improves utilization, so candidates who think in terms of resource-utilization metrics pick the wrong answer instead of recognizing the context-switching penalty.

How to eliminate wrong answers

Option A is wrong because the appearance of better utilization ignores the cognitive and coordination overhead of context switching, which reduces effective throughput. Option B is wrong because multi-project allocation is not the standard DA way of working; DA favors dedicated, stable teams aligned to value streams. Option D is wrong because total output typically falls, not rises, when a team is spread across multiple projects, due to switching costs and reduced focus.

Full explanation →
13
Multi-Selectmedium

Which TWO of the following are core pillars of a 'Disciplined Agile' mindset?

Select 2 answers
A.Always use a Scrum-based lifecycle
B.Be pragmatic
C.Context counts
D.Prioritize speed over quality
E.Follow the process guide precisely
AnswersB, C

Being pragmatic means choosing practices that work for the team's actual situation rather than dogmatically following a framework. This pillar underpins Disciplined Agile's guidance to adapt methods to context, making it a genuine core mindset element.

Why this answer

Option B (Be pragmatic) is correct because Disciplined Agile's core mindset explicitly includes 'Be pragmatic' as one of its guiding principles, encouraging teams to choose the approach that works best in their situation rather than dogmatically following one method. Option C (Context counts) is also correct because Disciplined Agile emphasizes that every team, organization, and problem is unique, so the choice of lifecycle, practices, and roles must fit the specific context. Option A is wrong because Disciplined Agile supports multiple lifecycles (Agile, Lean, Continuous Delivery, etc.), not only Scrum.

Option D is wrong because Disciplined Agile values quality and sustainable delivery, not sacrificing quality for speed. Option E is wrong because DA is deliberately flexible and tailorable, not a rigid process guide to be followed precisely.

Exam trap

DAF often tests whether candidates recognize that DA is explicitly anti-dogmatic — options that prescribe a single framework (Scrum) or rigid adherence to a guide are traps, because DA's pillars emphasize pragmatism and context sensitivity.

Full explanation →
14
MCQhard

Your organization is struggling with siloed teams. How does DA suggest breaking these silos?

A.Report all silos to HR
B.Force all teams to use the same tool
C.Mandate daily meetings for everyone
D.Implement cross-functional teams and coordination
AnswerD

Cross-functional teams directly dismantle silos by uniting members from different functions around shared objectives, while coordination mechanisms such as shared goals and regular communication ensure alignment across those groups. This satisfies the stem's requirement for breaking down siloed teams, as DA advocates restructuring collaboration rather than merely adding reporting layers.

Why this answer

Disciplined Agile suggests breaking down silos by implementing cross-functional teams and coordination mechanisms. Cross-functional teams bring together individuals with diverse skills to work on a shared goal, reducing handoffs and dependencies, while coordination practices (such as communities of practice, scrum of scrums, or DevOps) ensure alignment across teams.

Exam trap

DAF often tests the misconception that silos can be broken by mandating tools or meetings — the trap is selecting a superficial or coercive answer rather than the structural solution of cross-functional teams and coordination.

How to eliminate wrong answers

Option A is wrong because reporting silos to HR is not a DA-recommended approach — silos are an organisational design issue, not a disciplinary matter, and DA promotes structural and cultural solutions. Option B is wrong because forcing all teams to use the same tool does not break silos; it may even reinforce them if the tool doesn't address communication and collaboration patterns. Option C is wrong because mandating daily meetings for everyone is a superficial tactic that does not address the root causes of silos (e.g., functional departments, lack of shared goals) and can lead to meeting fatigue without improving collaboration.

Full explanation →
15
Multi-Selectmedium

Which TWO of the following are core principles of Disciplined Agile?

Select 2 answers
A.Top-down governance
B.Context Counts
C.Choice is Good
D.Individuals over everything
E.Follow the plan
AnswersB, C

Context Counts holds that no single method fits every situation; teams must tailor their way of working (WoW) to their unique environment, culture and constraints. This principle underpins Disciplined Agile's guidance to choose practices situationally rather than prescribe one universal process.

Why this answer

Disciplined Agile (DA) is built around the principle that "Context Counts" (option B), meaning that every team, organization, and situation is unique, so the way of working (WoW) must be tailored to the specific context rather than applying a one-size-fits-all method. It also embraces the principle that "Choice is Good" (option C), which encourages teams to have options and make informed decisions about their practices, lifecycle, and tooling instead of being forced into a single prescribed approach. Together these two principles reflect DA's pragmatic, flexible philosophy of guiding teams to choose and evolve their own way of working.

Option A (Top-down governance) is incorrect because DA favors lightweight, collaborative governance and self-organizing teams rather than command-and-control from the top. Option D (Individuals over everything) is not a DA principle; it loosely echoes the Agile Manifesto's "individuals and interactions over processes and tools," but it is not one of the DA core principles. Option E (Follow the plan) is incorrect because DA, like other agile approaches, values responding to change over rigidly adhering to a predefined plan.

Exam trap

DAF often tests whether candidates can distinguish DA's actual mindset principles (Context Counts, Choice is Good, Optimize Flow, Be Awesome) from generic agile-sounding phrases or traditional governance concepts that are not DA principles.

Full explanation →
16
Multi-Selectmedium

Which THREE of the following represent ways to reduce handoffs?

Select 3 answers
A.Automating the delivery pipeline to minimize manual intervention.
B.Co-locating team members who need to collaborate frequently.
C.Forming cross-functional teams that own features end-to-end.
D.Outsourcing non-core tasks to a specialized vendor.
E.Adding an extra layer of management to monitor transfers.
AnswersA, B, C

Automating the delivery pipeline removes the manual steps where work is passed between people or teams. Build, test and deployment stages execute without a human handing artefacts onward, so the transfer points that constitute handoffs simply cease to exist.

Why this answer

Option A is correct because automating the delivery pipeline (e.g., CI/CD with automated build, test, and deploy stages) removes the manual handoffs between development, QA, and operations that occur when artifacts are passed between people or teams. Option B is correct because co-locating team members who need to collaborate frequently replaces formal, asynchronous handoffs with direct, high-bandwidth communication, reducing the transfer of work between separate locations or groups. Option C is correct because cross-functional teams that own features end-to-end keep the skills needed for the whole value stream (dev, test, ops) within one team, eliminating the sequential handoffs to external specialist teams.

Option D does not belong because outsourcing to a vendor creates additional organizational boundaries and handoffs rather than reducing them. Option E does not belong because adding a management layer to monitor transfers adds coordination overhead and does not remove the handoffs themselves.

Exam trap

DAF often tests the misconception that any organizational change (outsourcing, adding management) reduces handoffs, when in fact only changes that eliminate transfers between parties — automation, co-location, cross-functional ownership — actually do so.

Full explanation →
17
MCQeasy

What is the core philosophy of 'Disciplined' in Disciplined Agile?

A.Working intentionally and making informed choices about your process.
B.Following rules without question.
C.Working as hard as possible at all times.
D.Using only one specific tool.
AnswerA

Disciplined Agile rejects one-size-fits-all methods: teams deliberately choose their way of working based on context, then evolve it. Working intentionally means consciously selecting practices and lifecycle rather than defaulting to a prescribed process, satisfying the philosophy's demand for informed, context-driven choice.

Why this answer

In Disciplined Agile (DA), 'Disciplined' means making conscious, context-driven choices about your way of working rather than blindly following a prescribed method. It emphasises intentionality — teams choose their process based on their context, and they do so with full awareness of the trade-offs. This is the core philosophy that distinguishes DA from prescriptive frameworks.

Exam trap

DAF often tests whether candidates understand that 'Disciplined' means intentional choice-making, not rigid adherence to rules — the trap is selecting an answer that equates discipline with strict rule-following or hard work.

How to eliminate wrong answers

Option B is wrong because DA explicitly rejects blind rule-following — it is a pragmatic, choice-driven toolkit, not a rigid methodology, and 'disciplined' refers to disciplined decision-making, not obedience. Option C is wrong because working as hard as possible is about effort, not discipline; DA values sustainable pace and smart process choices, not brute-force effort. Option D is wrong because DA is tool-agnostic and encourages teams to choose tools that fit their context; restricting to one specific tool contradicts the philosophy of informed choice.

Full explanation →
18
MCQhard

You are a coach in an organization trying to move to DA. What is the most effective way to help teams adopt the 'Choose Your WoW' mindset?

A.Create a standard process and enforce it.
B.Mandate that all teams use the 'Agile' lifecycle.
C.Take over their process decisions.
D.Provide teams with the DA toolkit and coach them on making context-sensitive choices.
AnswerD

Handing over the toolkit alone does not build judgement; coaching teams to weigh their own context against available practices develops the context-sensitive decision-making that Choose Your WoW requires. This satisfies the stem's need for the most effective adoption route rather than prescriptive practice selection.

Why this answer

'Choose Your WoW' (Way of Working) is a foundational DA principle meaning teams should tailor their process to their specific context rather than following a one-size-fits-all mandate. The most effective coaching approach is to equip teams with the DA toolkit (process goals, practices, lifecycle options) and guide them in making context-sensitive decisions themselves. This builds ownership and sustainable adoption, which is the essence of the DA mindset.

Exam trap

DAF often tests the misconception that standardization and enforcement equal good governance — candidates who come from traditional PM backgrounds may pick 'create a standard process' because it feels efficient, missing that DA's core value is team empowerment through guided choice.

How to eliminate wrong answers

Option A is wrong because creating and enforcing a standard process directly contradicts 'Choose Your WoW' — DA explicitly rejects prescriptive, one-size-fits-all processes. Option B is wrong because mandating the Agile lifecycle removes team choice; DA offers multiple lifecycles (Agile, Lean, Continuous Delivery, etc.) and teams should select based on context. Option C is wrong because taking over process decisions disempowers teams and undermines the coaching role, which is to guide rather than dictate.

Full explanation →
19
Multi-Selecthard

Which THREE of the following are components of DA's 'Enterprise Awareness'?

Select 3 answers
A.Considering broader organizational context
B.Focusing only on the team's output
C.Ignoring external dependencies
D.Recognizing organizational structure
E.Understanding business strategy
AnswersA, D, E

Enterprise awareness requires the team to look beyond its own project, weighing how decisions affect other teams, systems and goals across the organisation. Considering broader organisational context is therefore a core component, ensuring solutions align with enterprise-wide priorities rather than local optimisation.

Why this answer

Enterprise Awareness in Disciplined Agile (DA) means that teams understand and align with the wider organization rather than operating in isolation. Option A, considering broader organizational context, is correct because it captures the core idea of looking beyond the immediate team to how work fits into the larger enterprise. Option D, recognizing organizational structure, is correct because knowing reporting lines, governance, roles, and decision-making paths is essential for navigating the enterprise effectively.

Option E, understanding business strategy, is correct because teams must connect their work to the organization's goals, priorities, and value streams to make aligned decisions. Option B, focusing only on the team's output, is incorrect because that is the opposite of enterprise awareness, which explicitly requires looking beyond team boundaries. Option C, ignoring external dependencies, is incorrect because enterprise awareness demands identifying and managing dependencies on other teams, systems, and suppliers, not ignoring them.

Exam trap

DAF often tests the understanding of Enterprise Awareness by including distractors that focus narrowly on team-level concerns, tempting candidates to select them as valid components.

Full explanation →
20
Multi-Selectmedium

A Disciplined Agile team is reviewing its approach to governance. The team wants to ensure it is applying DA governance principles correctly. Which TWO of the following are core aspects of DA governance? (Choose two.)

Select 2 answers
A.Governance should prioritize comprehensive documentation over working software.
B.Governance should be applied only at the end of a project to verify compliance.
C.Governance should be based on trust and collaboration rather than command and control.
D.Governance should mandate a single set of detailed processes for all teams to follow.
E.Governance should focus on enabling teams to self-organize and make decisions within agreed boundaries.
AnswersC, E

DA governance emphasizes trust, collaboration, and empowerment. It moves away from command-and-control toward enabling teams to make decisions within agreed boundaries. This aspect is fundamental because it fosters ownership, faster decision-making, and alignment with agile values. It is a core aspect of DA governance, ensuring that oversight is constructive and supports self-organizing teams rather than micromanaging them.

Why this answer

DA governance is built on trust, collaboration, and empowerment, with clear boundaries that enable teams to self-organize. It is continuous and context-sensitive, avoiding one-size-fits-all mandates and excessive documentation. These two aspects reflect the core philosophy of DA governance, which balances oversight with agility to deliver value effectively.

Exam trap

The trap here is assuming governance must be command-and-control or phase-gate oriented, when DA governance actually emphasizes trust, empowerment, and continuous alignment.

Full explanation →
21
MCQhard

Your organization uses a large 'Project Management Office' to approve every change. How does this affect flow according to Lean principles?

A.It has no impact on total cycle time.
B.It improves flow by ensuring high-quality decisions.
C.It increases technical debt.
D.It introduces a queue, increasing cycle time.
AnswerD

Centralised approval by the Project Management Office creates a queue: work waits between value-adding steps, and according to Lean, queues directly extend cycle time and delay feedback. The constraint in the stem is mandatory approval of every change, so each item must idle before release, making queueing an inherent, measurable flow penalty.

Why this answer

According to Lean principles, any approval step that work must wait for creates a queue, and queues are the primary driver of increased cycle time. A centralized PMO that approves every change forces work items to sit idle while awaiting a decision, directly lengthening the time from request to delivery. This is a classic form of waste (waiting) and violates the Lean goal of continuous flow.

The correct answer identifies that the PMO introduces a queue, which increases cycle time.

Exam trap

The trap here is assuming that an approval process improves quality without considering its impact on flow; candidates may pick B because they equate governance with better outcomes, but Lean focuses on cycle time and queues.

How to eliminate wrong answers

Option A is wrong because approval gates inherently add waiting time, so they cannot have 'no impact' on total cycle time. Option B is wrong because while quality might improve, Lean flow is about speed and reducing batch sizes; a centralized approval board typically creates a bottleneck and slows flow, not improves it. Option C is wrong because technical debt is a code-quality issue, not a direct consequence of an approval process; the primary Lean impact is on flow and cycle time, not debt accumulation.

Full explanation →
22
MCQeasy

What does 'Kaizen' represent in a Lean context?

A.Continuous, incremental improvement.
B.The elimination of all management roles.
C.A sudden, radical organizational overhaul.
D.A specific software testing methodology.
AnswerA

Kaizen denotes continuous, incremental improvement pursued by everyone, every day, rather than occasional large change events. It underpins Lean thinking by steadily eliminating waste and refining processes, matching the question's requirement for what Kaizen represents in a Lean context.

Why this answer

Kaizen is the Japanese term for continuous, incremental improvement, a foundational Lean principle where every team member is empowered to identify and eliminate waste in small, ongoing steps rather than waiting for large transformative events. In a Lean context, Kaizen emphasizes steady refinement of processes, people, and products through frequent small changes that accumulate into significant gains over time.

Exam trap

DAF often tests whether candidates confuse Kaizen (incremental, continuous) with Kaikaku (radical, disruptive change) — the word 'sudden' or 'radical' in an option is the tell that it is not Kaizen.

How to eliminate wrong answers

Option B is wrong because Kaizen has nothing to do with removing management roles — Lean still relies on leadership and coaching to enable improvement. Option C is wrong because a sudden, radical overhaul describes Kaikaku (radical change) or reengineering, not Kaizen, which is explicitly incremental and continuous. Option D is wrong because Kaizen is a process-improvement philosophy, not a software testing methodology; testing frameworks like TDD or exploratory testing are unrelated.

Full explanation →
23
Multi-Selecthard

Which THREE of the following strategies help in 'Optimizing the Whole'?

Select 3 answers
A.Focusing on end-to-end cycle time rather than local task speed.
B.Identifying and managing cross-team dependencies.
C.Aligning team goals with the organization's overarching value delivery.
D.Creating specialized teams that work in complete isolation.
E.Assigning one manager to oversee each individual team member.
AnswersA, B, C

End-to-end cycle time measures the whole value stream from request to delivery, exposing delays caused by local optimisation that merely shifts bottlenecks downstream. This satisfies the stem's 'Optimizing the Whole' constraint by prioritising system-level throughput over individual task speed, which is the defining contrast with local efficiency.

Why this answer

Option A is correct because optimizing the whole means improving the entire value stream's flow, so measuring and reducing end-to-end cycle time (the total elapsed time from request to delivery) prevents suboptimization where one stage gets faster at the expense of others. Option B is correct because cross-team dependencies are the primary source of delays and handoff waste in multi-team systems, so identifying and actively managing them keeps work flowing across team boundaries rather than stalling at interfaces. Option C is correct because aligning each team's goals with the organization's overarching value delivery ensures local decisions contribute to overall customer and business outcomes instead of optimizing isolated metrics.

Option D is not correct because specialized teams working in complete isolation create silos, increase handoffs, and destroy the end-to-end flow that whole-system optimization requires. Option E is not correct because assigning a manager per individual team member adds supervisory overhead and reinforces a command-and-control, local-optimization mindset rather than improving system-wide value delivery.

Exam trap

DAF often tests 'Optimizing the Whole,' and the trap is selecting options that sound efficient (like specialized isolated teams or individual manager oversight) but actually sub-optimize the system.

Full explanation →
24
Multi-Selectmedium

Which TWO of the following are benefits of using the DA toolkit?

Select 2 answers
A.Increased transparency
B.Guaranteed success
C.Improved alignment with business goals
D.Standardization of all processes
E.Elimination of all meetings
AnswersA, C

The DA toolkit provides increased transparency by surfacing data lineage, transformation logic and quality metrics directly to stakeholders, satisfying the stem's requirement for visibility into analytical pipelines. This lets teams audit how figures are derived rather than trusting opaque outputs, which is the specific benefit the toolkit delivers.

Why this answer

Option A (Increased transparency) is correct because the DA (Disciplined Agile) toolkit makes decision points, process choices, and the rationale behind them explicit, so teams and stakeholders can see how work is governed and why a particular WoW (Way of Working) was selected. Option C (Improved alignment with business goals) is correct because DA's guided continuous improvement and goal-driven, context-sensitive approach ties process decisions to delivering value and achieving organizational objectives rather than enforcing a single prescribed method. Options B, D, and E are not benefits of DA: no toolkit can guarantee success, DA explicitly rejects one-size-fits-all standardization in favor of tailoring to context, and it does not eliminate meetings—it instead makes them more purposeful and effective.

Exam trap

The trap is selecting 'standardization of all processes' as a benefit because it sounds like a natural outcome of adopting a framework — but DA is explicitly anti-standardization in favor of context-driven choice.

Full explanation →
25
MCQmedium

A project is currently in the 'Construction' phase of the Disciplined Agile lifecycle. What is the main focus?

A.Building, testing, and verifying the solution
B.Establishing the initial team vision
C.Identifying stakeholders and their needs
D.Closing out the project and archiving documentation
AnswerA

Construction centres on incrementally building and testing a consumable solution, so this option matches the phase's purpose of producing verified, potentially shippable increments. It satisfies the stem's requirement by naming the actual work of the Construction phase rather than the Inception or Transition phases' concerns.

Why this answer

The Construction phase is where the team builds the solution in a series of iterations.

Full explanation →
26
MCQeasy

What is the primary goal of a retrospective in a DA-based environment?

A.To identify and plan process improvements.
B.To report progress to the stakeholder.
C.To assign blame for failed tasks.
D.To discuss the project budget.
AnswerA

The retrospective examines how the team worked during the iteration, surfacing impediments and experiments, then selecting concrete changes to the way of working. Its output is planned process improvement, not status reporting or delivery of functionality.

Why this answer

The primary goal of a retrospective in a Disciplined Agile environment is to identify and plan process improvements. Retrospectives are regular meetings where the team reflects on their work, identifies what went well and what didn't, and agrees on actions to improve their way of working. This continuous improvement is a core agile principle.

Exam trap

DAF often tests the purpose of retrospectives by including options about reporting or blame, which are common misconceptions about the ceremony.

How to eliminate wrong answers

Option B is wrong because reporting progress to stakeholders is typically done in other ceremonies like demos or status meetings, not retrospectives. Option C is wrong because assigning blame is counter to the retrospective's purpose, which is blameless and focused on improvement. Option D is wrong because discussing the project budget is not the focus of a retrospective; that would be handled in financial reviews or planning sessions.

Full explanation →
27
MCQeasy

Why does DA suggest 'Choice is Good'?

A.To keep the documentation long
B.To make the framework complex
C.Because teams need options for different contexts
D.To satisfy management
AnswerC

Disciplined Agile rejects one-size-fits-all prescriptions because team size, culture, compliance and technical context vary. Offering a range of practices lets each team select the option that best fits its own situation, satisfying the need for contextual fit rather than imposed uniformity.

Why this answer

Disciplined Agile (DA) suggests 'Choice is Good' because it recognises that teams operate in different contexts — different organisational cultures, regulatory environments, team sizes, and technical domains — and therefore need the flexibility to choose the practices, lifecycle, and tools that best fit their specific situation. This principle underpins DA's pragmatic, context-driven approach rather than a one-size-fits-all prescription.

Exam trap

DAF often tests the misconception that 'Choice is Good' means 'anything goes' or that it is about complexity — the trap is selecting an answer that implies lack of discipline or arbitrary choice, when the principle is actually about context-driven, guided selection of practices.

How to eliminate wrong answers

Option A is wrong because 'Choice is Good' has nothing to do with keeping documentation long — DA actually promotes lean documentation and right-sizing artefacts to the context. Option B is wrong because the principle is not about making the framework complex; rather, it acknowledges that the real world is complex and provides options to navigate that complexity, not to add unnecessary complexity. Option D is wrong because 'Choice is Good' is a principle for empowering teams to make context-appropriate decisions, not a tactic to satisfy management — management satisfaction is not the driver of this principle.

Full explanation →
28
Multi-Selecthard

Which TWO of the following aspects should you consider when evaluating the suitability of a new lifecycle for your team?

Select 2 answers
A.The team's current experience level with agile.
B.The number of coffee breaks per day.
C.The level of risk associated with the project.
D.The favorite framework of the lead developer.
E.The organization's physical office layout.
AnswersA, C

A team new to agile needs more coaching, simpler ceremonies and gradual adoption, whereas experienced practitioners can sustain tighter iterations and self-organisation. Matching lifecycle rigour to the team's actual agile maturity directly affects whether the chosen approach will succeed.

Why this answer

Option A is correct because a team's current experience level with agile directly determines how much structure, ceremony, and self-organization a new lifecycle can realistically support; a less experienced team may need more prescriptive guidance, while a mature team can handle lighter-weight approaches. Option C is correct because the level of risk associated with the project should drive lifecycle selection—higher-risk efforts typically benefit from more iterative, feedback-rich lifecycles with frequent validation, while lower-risk work may suit more linear approaches. Options B, D, and E are not valid considerations: coffee breaks, a lead developer's personal framework preference, and office layout are irrelevant to evaluating lifecycle suitability, which should be based on team capability, project risk, and delivery context rather than personal comfort or physical workspace factors.

Exam trap

DAF often tests the misconception that lifecycle selection is driven by personal preferences or trendy frameworks, when in fact it should be based on objective contextual factors like team experience and project risk.

Full explanation →
29
Multi-Selecthard

A team is adopting Disciplined Agile and wants to ensure they are applying the DA mindset. Which TWO of the following are key aspects of the DA mindset? (Choose two.)

Select 2 answers
A.Avoiding any form of planning to stay flexible.
B.Focusing on value delivery and continuous improvement.
C.Following a fixed set of ceremonies regardless of team size.
D.Being pragmatic and context-driven.
E.Maximizing documentation for all decisions.
AnswersB, D

DA is centered on delivering value to stakeholders and continuously improving processes and products. This aspect drives teams to measure outcomes and adapt. It is a core element of the DA mindset, ensuring that agility serves business goals rather than being an end in itself.

Why this answer

The Disciplined Agile mindset is built on principles such as being pragmatic, context-driven, and focused on value delivery and continuous improvement. These aspects guide teams to tailor their way of working and to constantly seek better outcomes. The other options represent misconceptions: rigid ceremonies, excessive documentation, or no planning, none of which align with the DA mindset.

Exam trap

The trap here is equating agility with the absence of planning or with strict adherence to ceremonies, whereas DA promotes purposeful adaptation.

Full explanation →
30
Multi-Selecthard

Which TWO of the following are potential side effects of failing to address bottlenecks in a process?

Select 2 answers
A.Improved team collaboration.
B.Increased lead time for all items in the system.
C.Faster delivery of high-priority items.
D.Increased pressure and potential burnout for team members.
E.A natural reduction in project costs.
AnswersB, D

Unaddressed bottlenecks restrict throughput, so work queues upstream and downstream. Because items wait longer before and after the constraint, overall lead time increases for every item in the system, not just those passing through the bottleneck.

Why this answer

Option B is correct because a bottleneck caps the throughput of the entire process, so work-in-progress queues up in front of the constrained step and every item—regardless of priority—spends longer waiting, which directly increases lead time (Little's Law: WIP = throughput × lead time). Option D is correct because unaddressed bottlenecks force people to constantly expedite, context-switch, and absorb schedule pressure at the constrained resource, which raises stress levels and is a well-documented driver of burnout. Option A is wrong because bottlenecks typically create friction and blame between teams rather than improving collaboration.

Option C is wrong because a bottleneck delays all items, including high-priority ones, unless explicit prioritization mechanisms are introduced. Option E is wrong because bottlenecks usually increase costs through overtime, expediting, and delayed delivery, not reduce them.

Exam trap

The trap here is assuming that bottlenecks only affect low-priority work or that prioritizing high-priority items can bypass the constraint, when in fact a bottleneck degrades lead time and team health across the entire system.

Full explanation →
31
MCQeasy

Which of the following is NOT an objective of the DA process decision framework?

A.To provide options based on context.
B.To mandate a single 'best' process for all teams.
C.To help teams understand trade-offs.
D.To enable guided continuous improvement.
AnswerB

The DA framework explicitly rejects prescribing one universal process; it offers decision points teams use to shape their own Way of Working. Mandating a single best process contradicts that intent, making it the correct NOT-an-objective answer.

Why this answer

The Disciplined Agile (DA) process decision framework is explicitly designed to offer context-sensitive options and trade-offs, not to prescribe a single universal process. Mandating one 'best' process for all teams contradicts DA's core philosophy that context counts and choice is good. Therefore, 'to mandate a single best process' is NOT an objective of the framework.

Exam trap

The trap here is confusing DA's structured guidance with prescriptive methodologies like SAFe or Scrum — candidates may assume any framework aims to standardize, but DA explicitly rejects a single mandated process.

How to eliminate wrong answers

Option A is a genuine objective because DA provides options tailored to the team's context. Option C is a genuine objective because DA helps teams understand trade-offs between different ways of working. Option D is a genuine objective because DA enables guided continuous improvement through its toolkit and principles.

Only option B contradicts the framework's intent.

Full explanation →
32
MCQmedium

Why does Lean advocate for 'Small Batch Sizes'?

A.To make the project appear larger to stakeholders.
B.To allow the team to work on more things simultaneously.
C.To reduce cycle time and increase the speed of feedback.
D.To minimize the use of automation tools.
AnswerC

Smaller batches shorten the time between starting and finishing work, cutting cycle time and letting feedback arrive sooner, so defects and misalignment surface earlier. This directly delivers the reduced cycle time and faster feedback the option names as Lean's goal.

Why this answer

Small batch sizes reduce the amount of work in progress between steps, which shortens the time any single item spends waiting in queues and therefore reduces overall cycle time. Shorter cycles mean feedback — from tests, users, or downstream teams — arrives sooner, so defects and wrong assumptions are caught while they are cheap to fix. This is a direct application of Lean flow and Little's Law.

Exam trap

The trap is equating small batches with doing more at once; the exam tests whether you understand that small batches reduce WIP and cycle time to accelerate feedback, not increase parallelism.

How to eliminate wrong answers

Option A is wrong because batch size has nothing to do with stakeholder perception of project size; Lean optimizes internal flow, not optics. Option B is wrong because working on more things simultaneously increases WIP and context switching, which is the opposite of what small batches achieve — small batches deliberately limit concurrent work. Option D is wrong because small batches often depend more on automation (CI/CD, automated tests) to be viable, not less; minimizing automation would undermine the fast feedback that small batches enable.

Full explanation →
33
MCQhard

You are trying to improve flow in a cross-functional team. How does 'T-shaped' skill development support this?

A.It reduces the need for salary increases.
B.It enables team members to help each other, preventing bottlenecks.
C.It increases the number of people available for specialized tasks.
D.It makes documentation unnecessary.
AnswerB

T-shaped development gives each member deep expertise in one discipline plus working knowledge across adjacent areas, so they can absorb overflow work when a specialist becomes a bottleneck. This directly satisfies the stem's cross-functional flow constraint: shared baseline competence lets peers redistribute tasks without waiting on a single deep specialist.

Why this answer

T-shaped skills allow team members to jump in and help others during bottlenecks, preventing work from stalling.

Full explanation →
34
MCQmedium

Why does a 'Push' system often lead to lower quality?

A.It forces work into the system, causing teams to rush.
B.It encourages too much collaboration.
C.It makes it too easy to track progress.
D.It allows for too much testing time.
AnswerA

Push systems release work based on upstream schedules rather than downstream capacity, forcing items into the system regardless of readiness. This satisfies the stem's constraint by explaining how overload pressures teams to rush, degrading quality.

Why this answer

A Push system schedules work into the process based on forecasts or external demands, regardless of whether the team has capacity to handle it. This forces work into the system, often causing teams to rush, multitask, and cut corners on quality practices like testing and review. The result is higher defect rates, increased rework, and lower overall quality.

Exam trap

DAF often tests the misconception that Push systems fail for organizational or tooling reasons, when the core issue is that pushing work into the system without capacity signals causes rushing and quality erosion.

How to eliminate wrong answers

Option B is wrong because a Push system does not inherently encourage collaboration — if anything, it can create silos as teams struggle to keep up with pushed work. Option C is wrong because easy progress tracking is not a cause of lower quality; tracking is orthogonal to the push/pull dynamic. Option D is wrong because a Push system typically reduces testing time by creating schedule pressure, rather than allowing too much testing time.

Full explanation →
35
Multi-Selectmedium

Which THREE of the following are examples of organizational contexts that might influence your 'Choose Your WoW' decisions?

Select 3 answers
A.The office address of the company headquarters.
B.The regulatory environment.
C.The brand of the team's laptops.
D.The organizational culture (e.g., risk-averse vs. experimental).
E.The team's geographic distribution.
AnswersB, D, E

A strict regulatory environment constrains 'Choose Your WoW' by mandating specific compliance evidence, audit trails and segregation of duties, which rules out lightweight or undocumented ways of working. This satisfies the stem's requirement for an organisational context, since regulation externally dictates which practices and governance structures remain viable.

Why this answer

Option B is correct because the regulatory environment directly shapes how a team must work — for example, compliance-heavy industries (finance, healthcare, government) require documented controls, audit trails, and formal approvals that constrain which practices and cadences a team can safely adopt. Option D is correct because organizational culture determines the appetite for experimentation versus predictability; a risk-averse culture favors more upfront planning and gated reviews, while an experimental culture tolerates iterative discovery and frequent change. Option E is correct because geographic distribution affects communication and coordination — co-located teams can rely on osmotic, face-to-face interaction, whereas distributed teams need deliberate tooling, time-zone-aware ceremonies, and more explicit documentation.

Option A does not belong because a headquarters street address is a logistical detail with no bearing on how a team designs its way of working. Option C does not belong because the laptop brand is a procurement/hardware choice, not an organizational context that influences process or practice selection.

Exam trap

DAF often tests the distinction between genuine context factors (culture, regulation, distribution) and irrelevant operational details (office address, laptop brand) that candidates might mistakenly treat as influencing WoW decisions.

Full explanation →
36
MCQmedium

A delivery team at a financial services organization has been using a predictive approach for years. Leadership now wants to adopt Disciplined Agile to improve responsiveness. During the first retrospective, the team identifies that their biggest challenge is that they cannot get feedback from stakeholders until the very end of the project. Which Disciplined Agile principle should the team apply first to address this challenge?

A.Deliver value incrementally to obtain feedback early and often.
B.Optimize the whole by eliminating local efficiencies.
C.Make all decisions at the last responsible moment.
D.Choose the right level of detail for the context.
AnswerA

This principle directly addresses the challenge by breaking work into smaller increments that can be demonstrated to stakeholders, enabling early and frequent feedback. By delivering value incrementally, the team can validate assumptions and adjust direction before the project ends, reducing the risk of building the wrong thing. It is a core Disciplined Agile principle that promotes empirical process control and stakeholder collaboration.

Why this answer

Delivering value incrementally is the foundational Disciplined Agile principle that enables early and frequent feedback. By shortening the cycle time between building and showing working software, the team can engage stakeholders throughout the project rather than only at the end. This directly solves the identified problem and sets the stage for other principles such as optimizing the whole.

Exam trap

The trap here is assuming that any Disciplined Agile principle will fix the feedback gap, when only incremental delivery directly creates the opportunity for early stakeholder input.

Full explanation →
37
MCQeasy

During a retrospective, the team notices they spend 30% of their time fixing defects in previously delivered code. Which Lean principle does this violate?

A.Respect People.
B.Optimize the Whole.
C.Deliver Fast.
D.Build Quality In.
AnswerD

Reworking delivered code directly contradicts building quality in, which demands defects be prevented at each stage rather than detected downstream. The 30% rework figure evidences escaped defects, violating the Lean principle that quality is designed into the process, not inspected afterwards.

Why this answer

The 30% rework rate indicates defects are escaping into delivered code rather than being prevented at the source. The Lean principle 'Build Quality In' (derived from Lean manufacturing's jidoka/stop-the-line concept) requires embedding quality at each step so defects are caught immediately, not fixed later. Spending nearly a third of capacity on rework is the classic symptom of inspecting quality in at the end instead of building it in throughout.

Exam trap

DAF often tests whether candidates can distinguish Lean quality principles (Build Quality In) from flow/efficiency principles (Deliver Fast, Optimize the Whole) when the scenario describes rework or defects.

How to eliminate wrong answers

Option A is wrong because 'Respect People' concerns how teams are treated, empowered, and enabled — it does not directly address defect rates or rework. Option B is wrong because 'Optimize the Whole' is about optimizing the value stream end-to-end rather than local efficiencies; a defect-fixing statistic is a quality symptom, not a system-optimization one. Option C is wrong because 'Deliver Fast' concerns shortening lead time and flow, and while rework slows delivery, the question specifically points to a quality failure, which is the domain of Build Quality In.

Full explanation →
38
MCQmedium

You are applying the 'Coordinate Activities' process goal. What is the main reason to look at the decision points within this goal?

A.To find a single 'best' practice for all teams.
B.To satisfy regulatory audit requirements.
C.To understand the trade-offs of various practices.
D.To minimize the number of team meetings.
AnswerC

Decision points capture the options available at each process goal and the trade-offs between them, so teams choose practices suited to their context. Reviewing them within Coordinate Activities therefore reveals those trade-offs, which is precisely the reason the question asks for.

Why this answer

DA's decision points exist precisely because there is no universally best practice — each practice carries trade-offs (e.g., a daily stand-up improves transparency but consumes time; a Kanban board improves flow visibility but requires discipline to maintain). Examining the decision points within 'Coordinate Activities' lets a team consciously weigh those trade-offs against its own context and choose the coordination practices that fit. That is the core purpose of the decision-point structure in the DA toolkit.

Exam trap

DAF often tests the misconception that DA provides a single prescriptive 'best practice' for each process goal, when in fact decision points exist specifically to help teams evaluate trade-offs and choose context-appropriate options.

How to eliminate wrong answers

Option A is wrong because DA explicitly rejects the notion of a single 'best' practice — its entire philosophy is context-driven, and decision points exist to expose options, not to converge on one universal answer. Option B is wrong because satisfying regulatory audit requirements is a governance/compliance concern handled by other process goals (e.g., 'Align With Enterprise Direction' or 'Governing'), not the reason DA structures decision points. Option D is wrong because minimising meetings is a possible side effect of good coordination choices, not the purpose of examining decision points — DA is about effectiveness and fit, not meeting-count reduction as an end in itself.

Full explanation →
39
MCQmedium

A team has decided to use the 'Scrum' lifecycle. According to DA, what is the next step after selecting the lifecycle?

A.Report the choice to the executive sponsor.
B.Start the first sprint immediately.
C.Identify and address the process goals within the lifecycle.
D.Hire a Scrum expert to manage the team.
AnswerC

Once a lifecycle is chosen, DA directs teams to the process goals that lifecycle contains, then assess each one and select practices addressing it. This satisfies the stem's sequencing constraint: lifecycle selection precedes goal identification, not practice selection.

Why this answer

In Disciplined Agile (DA), after selecting a lifecycle (such as Scrum), the team must identify and address the process goals that are relevant to that lifecycle. Process goals are the foundational activities that guide how the team will work, and they must be tailored to the team's context. This step ensures that the team doesn't just adopt a superficial set of ceremonies but instead focuses on the underlying goals that drive success.

Only after addressing these goals can the team effectively start executing the lifecycle.

Exam trap

DAF often tests the misconception that selecting a lifecycle is the final step before execution, when in fact it is just the beginning of a continuous improvement process that starts with addressing process goals.

How to eliminate wrong answers

Option A is wrong because reporting the choice to the executive sponsor is not a prescribed step in DA; while communication may be useful, it is not the immediate next step after lifecycle selection. Option B is wrong because starting the first sprint immediately skips the critical step of identifying and addressing process goals, which is necessary to tailor the lifecycle to the team's needs. Option D is wrong because hiring a Scrum expert is not a required step in DA; DA emphasizes team self-organization and does not mandate external experts for lifecycle implementation.

Full explanation →
40
MCQhard

In the DA framework, what is the 'Transition' phase primarily focused on?

A.Continuous improvement
B.Requirement gathering
C.Team building
D.Deployment and release
AnswerD

Transition covers deploying the solution into production and releasing it to users, including cutover, migration and handover activities. It follows the solution lifecycle's construction work, satisfying the stem's focus on deployment and release rather than ongoing operational support.

Why this answer

In Disciplined Agile, the Transition phase focuses on deploying the solution to production and releasing it to stakeholders. It covers activities like release planning, deployment, and operational readiness, ensuring the solution is delivered and supported. This phase follows Construction and precedes ongoing operations and continuous improvement.

Exam trap

The trap is confusing Transition with Ongoing Operations or Continuous Improvement — candidates may pick 'continuous improvement' because DA emphasizes it, but that is not the phase's primary focus.

How to eliminate wrong answers

Option A is wrong because continuous improvement is an ongoing activity across all phases, not the primary focus of Transition. Option B is wrong because requirement gathering occurs primarily in Inception. Option C is wrong because team building is part of Inception and ongoing team development, not the Transition phase's core purpose.

Full explanation →
41
Multi-Selecthard

Which THREE of the following activities are considered essential for 'Continuous Improvement' in a DA team?

Select 3 answers
A.Implementing automated testing.
B.Conducting regular retrospectives.
C.Waiting for the annual performance review.
D.Monitoring and acting on team metrics.
E.Increasing the number of meetings.
AnswersA, B, D

Automated testing provides fast, repeatable feedback on every change, which is the empirical data continuous improvement depends on. Without it, teams cannot detect regressions quickly enough to inspect and adapt their Way of Working meaningfully.

Why this answer

Option A (Implementing automated testing) is correct because automated tests provide fast, repeatable feedback on code quality and regression risk, which is the empirical data Continuous Improvement depends on to shorten feedback loops and raise deployment confidence. Option B (Conducting regular retrospectives) is correct because retrospectives are the structured inspect-and-adapt ceremony in which the team identifies what worked, what did not, and commits to concrete improvement actions each iteration. Option D (Monitoring and acting on team metrics) is correct because Continuous Improvement requires measuring delivery and quality signals (e.g., lead time, deployment frequency, change failure rate, MTTR) and then acting on those metrics rather than guessing.

Option C (Waiting for the annual performance review) is not correct because yearly feedback is far too infrequent to drive iterative improvement and is not a team-level continuous mechanism. Option E (Increasing the number of meetings) is not correct because more meetings add overhead without guaranteeing measurable improvement; improvement comes from feedback and action, not meeting volume.

Exam trap

DAF often tests the confusion between continuous improvement and periodic events like annual reviews — candidates may pick 'annual performance review' because it sounds like evaluation, but continuous improvement requires frequent, team-based reflection and action.

Full explanation →
42
MCQeasy

What is the role of 'Enterprise Awareness' in the DA toolkit?

A.To ensure everyone works the same way
B.To encourage team members to act in the best interest of the organization
C.To report all team activities to management
D.To limit the team to internal tasks
AnswerB

Enterprise Awareness guides individuals to consider organisational strategy, goals and broader context when making local decisions. This ensures teams optimise for the whole enterprise rather than their own silo, which is precisely the behaviour the DA toolkit intends this concept to instil.

Why this answer

Enterprise Awareness in DA is a guiding principle that encourages individuals and teams to consider the whole organisation when making decisions, rather than optimising only for their local team. It pushes teams to act in the best interest of the enterprise, even when that means accepting a locally suboptimal outcome. This is distinct from standardisation or reporting mandates.

Exam trap

The trap is equating Enterprise Awareness with enforced uniformity or management reporting, when it is actually a mindset of acting for the organisation's broader good.

How to eliminate wrong answers

Option A is wrong because Enterprise Awareness does not mandate that everyone work the same way — DA explicitly supports context-driven, varied ways of working across teams. Option C is wrong because Enterprise Awareness is a mindset, not a reporting mechanism; DA governance is lean and automated rather than requiring exhaustive activity reporting. Option D is wrong because Enterprise Awareness expands a team's perspective beyond internal tasks to include customers, other teams, and enterprise goals — it does not restrict the team to internal work.

Full explanation →
43
MCQhard

A team is using a 'Lean' approach. What is their primary goal?

A.To eliminate waste and optimize the flow of value
B.To force team members to work faster
C.To replace all agile practices with kanban
D.To increase the number of team meetings
AnswerA

Lean's primary goal is eliminating waste while optimising value flow, directly satisfying the stem's question. Every Lean practise, from value stream mapping to pull systems, serves this aim of removing non-value-adding activity and smoothing delivery.

Why this answer

Lean's primary goal is to maximize customer value by eliminating waste and optimizing the flow of value through the system. In software development, this means removing activities that do not add value, reducing cycle time, and delivering value smoothly. Lean is not about working faster or replacing Agile practices; it is a mindset and set of principles that complement Agile.

Exam trap

DAF often tests the misconception that Lean means working harder or faster, or that it is synonymous with Kanban — candidates may pick 'replace all agile practices with kanban' or 'work faster' instead of the waste-elimination goal.

How to eliminate wrong answers

Option B is wrong because Lean is not about forcing people to work faster — it is about removing waste so that work flows efficiently; pushing people to work faster leads to burnout and defects, which are wastes. Option C is wrong because Lean does not require replacing all Agile practices with Kanban; Kanban is a Lean-inspired method, but Lean is broader and can coexist with Scrum, XP, and other Agile practices. Option D is wrong because increasing meetings adds overhead and is often a form of waste (waiting, over-processing), directly contradicting Lean's goal of eliminating waste.

Full explanation →
44
MCQhard

If you have a 'bottleneck', how does increasing local efficiency at a non-bottleneck step affect the system?

A.It reduces the cycle time of the entire system.
B.It has no effect on the system.
C.It increases the pile-up at the bottleneck.
D.It improves the total throughput of the system.
AnswerC

Increasing local efficiency at a non-bottleneck step raises that step's throughput, pushing work into the bottleneck faster than it can process. Since the bottleneck's capacity is unchanged, excess inventory accumulates in front of it, worsening the pile-up.

Why this answer

Increasing speed at a non-bottleneck simply pushes more work to the bottleneck, increasing the pile-up without increasing system throughput.

Full explanation →
45
MCQeasy

What is the role of 'Governance' in DA?

A.To replace all leadership roles
B.To provide light, risk-based guidance
C.To impose strict, heavy rules
D.To stop teams from working
AnswerB

Disciplined Agile governance supplies light, risk-based guidance, scaling oversight to the actual risk and regulatory exposure of the initiative. This satisfies the need for control without heavyweight stage gates, letting teams retain autonomy while remaining accountable for outcomes.

Why this answer

In DA, Governance provides light, risk-based guidance rather than heavy, prescriptive control. It ensures that teams operate within acceptable risk boundaries while still having the autonomy to tailor their Way of Working. Governance in DA is about enabling teams and providing oversight proportional to the risk and regulatory context, not about imposing rigid rules.

Exam trap

The trap is equating governance with heavy-handed control, when DA specifically defines it as light and risk-based, enabling rather than restricting teams.

How to eliminate wrong answers

Option A is wrong because Governance does not replace leadership roles; it complements them by providing oversight and guidance. Option C is wrong because DA explicitly rejects strict, heavy rules in favor of light, risk-based guidance that scales with context. Option D is wrong because Governance is intended to enable work, not stop it; its purpose is to keep work aligned with organizational and regulatory expectations.

Full explanation →
46
Multi-Selecthard

Which THREE of the following are considered 'Waste' in the context of Lean software development?

Select 3 answers
A.Waiting for external dependencies to clear.
B.Automated regression testing.
C.Rework due to defects.
D.Developing features that the user does not want.
E.Pair programming sessions.
AnswersA, C, D

Waiting is one of the seven Lean wastes, and time lost while external dependencies clear produces no value. It satisfies the waste criterion because the delay is non-value-adding, blocking flow and consuming cycle time the team cannot recover.

Why this answer

In Lean software development, 'waste' (muda) is any activity that consumes resources without creating value for the customer. Option A, waiting for external dependencies to clear, is waste because idle time caused by blocked work adds delay and no value, matching the Lean waste category of 'waiting.' Option C, rework due to defects, is waste because correcting defects consumes effort and time that could have been spent on value-adding work, corresponding to the Lean waste of 'defects.' Option D, developing features that the user does not want, is waste because building unnecessary functionality consumes capacity without delivering customer value, matching the Lean waste of 'extra features' or overproduction. Option B, automated regression testing, is not waste because it is a value-enabling practice that verifies working software and reduces defect-related waste.

Option E, pair programming sessions, is not waste because pairing is a deliberate practice that improves quality, knowledge sharing, and reduces rework, so it supports value delivery rather than consuming resources without benefit.

Full explanation →
47
MCQmedium

A team must decide how to handle a recurring decision about which work items to pull into the next iteration. Several team members want to make this decision themselves, while the product owner expects to decide alone. Which principle should guide how the Way of Working assigns this decision?

A.The team should decide alone because self-organization means all decisions belong to the team.
B.The decision rights should be explicitly assigned based on context, with the team's Way of Working recording who decides.
C.The product owner should always decide alone because they own the backlog.
D.The decision should always be escalated to the team's manager to avoid conflict.
AnswerB

Disciplined Agile treats decision rights as a design choice that should be made consciously and documented in the Way of Working. Context such as the team's experience, the product's risk, and stakeholder needs determines who decides. Making the assignment explicit prevents recurring friction and clarifies accountability.

Why this answer

Disciplined Agile treats decision rights as something to be assigned deliberately based on context, not assumed from role or ideology. The team's Way of Working should record who decides what, so recurring questions do not reopen conflict. This balances the product owner's accountability for value with the team's need for meaningful ownership of its work.

Exam trap

The trap here is assuming decision rights follow automatically from a role or from the idea of self-organization, rather than being assigned explicitly based on context.

Full explanation →
48
MCQmedium

What is the primary Lean motivation for 'deferring commitment' until the last responsible moment?

A.To allow stakeholders to change their minds frequently.
B.To keep the team busy with administrative work.
C.To save money on project overhead.
D.To make decisions based on better, more current information.
AnswerD

Deferring commitment lets teams decide at the last responsible moment, when the most information is available. This directly satisfies Lean's goal of reducing uncertainty: options stay open, and choices rest on current facts rather than forecasts. Better information yields better decisions, which is the primary motivation.

Why this answer

Deferring commitment is a Lean principle that delays irreversible decisions until the last responsible moment, when the most information is available. This reduces the cost of change and the risk of deciding on outdated assumptions. The primary motivation is better decision quality through more current, complete information.

Exam trap

DAF often tests the confusion between 'deferring commitment' and indecision or procrastination — the trap is missing that it is a deliberate, information-driven strategy, not avoidance.

How to eliminate wrong answers

Option A is wrong because deferring commitment is not about indulging stakeholder whims; it is a disciplined strategy to maximize information before deciding. Option B is wrong because the goal is not to keep the team busy with administrative work — that would be waste, not value. Option C is wrong because cost savings are a possible byproduct, not the primary motivation; the core driver is decision quality under uncertainty.

Full explanation →
49
MCQhard

A Disciplined Agile team is struggling with frequent interruptions and unclear priorities. The team lead wants to apply the DA principle of 'Delight Customers' to improve focus. Which action best aligns with this principle?

A.Implement a strict change control process to minimize disruptions.
B.Adopt a weekly status meeting to keep stakeholders informed.
C.Increase the team's velocity by adding more resources.
D.Prioritize work based on the greatest value to the customer, even if it means saying no to some stakeholder requests.
AnswerD

Delighting customers means consistently delivering valuable solutions that meet their needs. Prioritizing based on customer value ensures the team focuses on what matters most, even if it requires pushing back on lower-value requests. This directly addresses the struggle with interruptions and unclear priorities by providing a clear decision-making criterion.

Why this answer

The principle 'Delight Customers' emphasizes delivering valuable solutions that meet customer needs. By prioritizing work based on customer value, the team can focus on high-impact tasks and reduce interruptions from lower-priority requests. This directly addresses the scenario's issues of unclear priorities and frequent disruptions, ensuring the team's efforts are aligned with what truly matters to the customer.

Exam trap

The trap here is confusing 'Delight Customers' with simply keeping customers informed or controlling changes, rather than actively prioritizing their value.

Full explanation →
50
MCQhard

A team has a significant number of remote members. Which decision point within the 'Coordinate Activities' goal is most critical?

A.Select the lifecycle.
B.Manage the scope.
C.Coordinate the team.
D.Improve the process.
AnswerC

With many remote members, coordination cannot rely on incidental proximity, so deliberately coordinating the team becomes the pivotal decision point. It addresses distributed communication, availability and shared cadence, satisfying the stem's remote-workforce constraint within Coordinate Activities.

Why this answer

Within the 'Coordinate Activities' process goal, the decision point 'Coordinate the team' is most critical for a team with many remote members because it directly addresses how team members communicate, collaborate, and align their work across distances. This decision point covers practices such as virtual stand-ups, shared calendars, and communication tools that are essential for remote coordination.

Exam trap

DAF often tests the confusion between decision points within a process goal, leading candidates to choose a broader goal like 'Select the lifecycle' instead of the specific decision point that addresses remote coordination.

How to eliminate wrong answers

Option A is wrong because 'Select the lifecycle' is a higher-level decision that may be influenced by distribution but is not the most critical decision point within 'Coordinate Activities' for remote members. Option B is wrong because 'Manage the scope' is about controlling what work is included, not about coordinating remote team interactions. Option D is wrong because 'Improve the process' is about continuous improvement, which is important but not the immediate critical need for remote coordination.

Full explanation →
51
MCQmedium

You are managing a process where work consistently stalls at the 'Testing' stage. What is the most effective way to address this bottleneck?

A.Outsource the Testing phase to a third party.
B.Shift team focus to assist in the Testing phase to clear the backlog.
C.Increase the speed of the development phase to clear the backlog faster.
D.Remove the Testing phase from the workflow.
AnswerB

Shifting team focus to assist Testing applies the theory-of-constraints principle of subordinating non-bottleneck capacity to the bottleneck, directly relieving the stalled Testing stage. Clearing that backlog raises throughput, whereas optimising upstream stages would only worsen the queue.

Why this answer

In Lean and Theory of Constraints, the correct response to a bottleneck is to exploit and elevate the constraint — i.e., focus resources on the bottleneck to increase its throughput. Shifting team focus to assist the Testing phase directly increases testing capacity, clears the backlog, and improves overall flow, which is the most effective immediate action.

Exam trap

DAF often tests the misconception that speeding up non-bottleneck stages (like development) improves flow — candidates who pick 'increase development speed' ignore Theory of Constraints and Little's Law.

How to eliminate wrong answers

Option A is wrong because outsourcing the Testing phase adds handoff delays, coordination overhead, and loss of context — it does not address the root capacity constraint and often worsens cycle time. Option C is wrong because increasing development speed when Testing is the bottleneck only floods the constraint with more WIP, worsening the backlog and increasing cycle time (per Little's Law). Option D is wrong because removing the Testing phase eliminates quality control, which violates the Lean principle of building quality in and would push defects downstream.

Full explanation →
52
MCQmedium

What is meant by 'Self-Organization' in a team context?

A.The team does not have a leader or a coach
B.Team members work on whatever they want, whenever they want
C.The team refuses to communicate with management
D.The team determines how to best accomplish the work assigned to them
AnswerD

Self-organisation means the team, not a manager, decides how to divide and sequence the work it has been assigned. Authority over the 'how' sits with those doing the work, while the 'what' and 'why' come from outside. This satisfies the stem's requirement that the team determines its own approach.

Why this answer

Self-organization in an Agile team means the team has the authority and responsibility to determine how to best accomplish the work assigned to them — they decide on task breakdown, assignment, and approach. It does not mean the absence of leadership or structure; rather, it means the team self-manages its internal processes while remaining accountable to the organization. The team still operates within organizational boundaries and may have a coach or Scrum Master facilitating the process.

Exam trap

The trap here is equating self-organization with anarchy — candidates often pick the option suggesting no leader or no structure, when self-organization actually means autonomy within organizational constraints.

How to eliminate wrong answers

Option A is wrong because self-organizing teams can and often do have leaders and coaches — a Scrum Master or Agile coach facilitates the team's self-organization rather than directing it, so the absence of a leader is a misconception. Option B is wrong because self-organization does not mean team members work on whatever they want whenever they want; the team still commits to sprint goals and delivers against agreed priorities, just with autonomy over how they execute. Option C is wrong because self-organizing teams are expected to communicate transparently with management and stakeholders — refusing communication would undermine the transparency that Agile depends on.

Full explanation →
53
MCQmedium

If a team is using the 'Agile' lifecycle, what is their primary focus?

A.Risk mitigation only
B.Cost reduction
C.Continuous delivery of value
D.Long-term planning
AnswerC

Agile lifecycles prioritise delivering working value to customers in short, frequent increments rather than gating delivery behind sequential phase completion. This continuous delivery of value satisfies the stem's Agile constraint, distinguishing it from Waterfall's phase-gated handoffs and stage-gate approval cycles.

Why this answer

The Agile lifecycle in Disciplined Agile is centered on delivering value to customers in short, incremental cycles. The primary focus is on continuous delivery of value, which means frequently producing working, potentially shippable increments that meet stakeholder needs. This approach allows for rapid feedback and adaptation, aligning with Agile principles.

Exam trap

DAF often tests the confusion between the Agile lifecycle and other lifecycles, such as Continuous Delivery, by presenting options that sound plausible but miss the core focus on value delivery.

How to eliminate wrong answers

Option A is wrong because risk mitigation is a concern but not the primary focus; Agile addresses risk through iterative delivery but it's not the sole focus. Option B is wrong because cost reduction is a possible benefit but not the primary goal; Agile prioritizes value delivery over cost. Option D is wrong because long-term planning is more characteristic of traditional or predictive lifecycles; Agile emphasizes adaptive planning over long-term detailed plans.

Full explanation →
54
MCQmedium

A team is working on a project with high technical uncertainty. Which approach should they adopt?

A.Follow the original plan strictly to reduce risk
B.Adopt an iterative approach with frequent spikes to learn
C.Outsource the uncertain parts of the project
D.Delay the uncertain work until the end of the project
AnswerB

Iterative delivery with spikes lets the team probe unknowns early, converting technical uncertainty into evidence before committing to full build. Spikes are timeboxed investigations, so learning happens without derailing delivery cadence — directly addressing the high uncertainty constraint in the stem.

Why this answer

When a project faces high technical uncertainty, the most effective approach is to reduce that uncertainty through rapid, iterative learning. Option B advocates an iterative approach with frequent spikes—time-boxed investigations or prototypes—which directly addresses unknowns by testing assumptions early and often. This aligns with agile and lean principles, where uncertainty is managed by short feedback loops rather than rigid planning.

By learning quickly, the team can adapt the plan based on empirical evidence, thereby reducing risk and increasing the likelihood of delivering value.

Exam trap

DAF often tests the misconception that uncertainty can be eliminated by strict planning or outsourcing, when in fact it requires iterative learning and adaptation.

How to eliminate wrong answers

Option A is wrong because following the original plan strictly assumes the plan is correct despite high uncertainty; it ignores the need to adapt when new information emerges, which can lead to wasted effort and failure. Option C is wrong because outsourcing uncertain parts does not eliminate the uncertainty; it merely transfers the work to another party who may lack the necessary context or may also struggle with the same unknowns, and it can introduce coordination overhead. Option D is wrong because delaying uncertain work until the end increases risk; the team may discover too late that the approach is unworkable, leaving no time to pivot, and it defers learning when it is most needed.

Full explanation →
55
MCQmedium

Which of the following is NOT an objective of the 'Improve Process' goal?

A.Experimenting with new practices
B.Identifying process bottlenecks
C.Learning from past mistakes
D.Documenting every single step for auditors
AnswerD

Documenting every single step for auditors is a compliance artefact, not a process-improvement objective. The 'Improve Process' goal targets cycle time, waste and quality through measurement and iteration; exhaustive documentation satisfies audit evidence requirements instead. It therefore falls outside the goal's scope, making it the correct answer to this NOT question.

Why this answer

Stopping the work to document everything is not an improvement strategy; it's a bottleneck.

Full explanation →
56
Multi-Selecthard

Which THREE of the following are foundational principles of the Disciplined Agile toolkit that guide the 'Choose Your WoW' process?

Select 3 answers
A.Choice is good.
B.Follow the methodology strictly.
C.Context counts.
D.One size fits all.
E.Be pragmatic.
AnswersA, C, E

Choice is good affirms that teams should select from viable options rather than follow a single mandated process. This principle directly enables the Choose Your WoW approach, letting teams tailor their way of working to fit.

Why this answer

The Disciplined Agile toolkit is built on the principle that 'Choice is good' (A), meaning teams should be free to select from a range of techniques and practices rather than being forced into a single prescribed method. 'Context counts' (C) is also foundational because DA recognizes that the best way of working depends on the team's unique situation, including organizational culture, team size, and problem domain. 'Be pragmatic' (E) is the third core principle, emphasizing that teams should focus on what actually works in practice rather than dogmatically following theory. Options B and D are incorrect because DA explicitly rejects strict methodology adherence and the idea that one size fits all; instead, it promotes tailoring the way of working (WoW) to the team's specific context.

Exam trap

The trap is selecting 'Follow the methodology strictly' or 'One size fits all' because they sound like principles of a disciplined framework — but DA is explicitly anti-dogmatic and context-driven.

Full explanation →
57
Multi-Selectmedium

Which TWO of the following are core components of the Disciplined Agile 'Mindset'?

Select 2 answers
A.Strictly adhere to Scrum ceremonies.
B.Follow the PMI PMBOK guide exclusively.
C.Optimize Flow.
D.Be Awesome.
E.Always choose the newest technology.
AnswersC, D

Optimize Flow is a core component of the Disciplined Agile Mindset, focusing on removing bottlenecks and smoothing value delivery across the system. It satisfies the stem by naming a principle that guides decisions toward continuous, unimpeded throughput.

Why this answer

The Disciplined Agile (DA) Mindset is built around a set of guiding principles and promises, and among its core principles are 'Optimize Flow' (option C) and 'Be Awesome' (option D). 'Optimize Flow' reflects DA's lean-influenced focus on improving the smooth, continuous delivery of value through the value stream rather than optimizing individual silos or resources. 'Be Awesome' captures DA's emphasis on delivering delightful, high-quality solutions and continuously improving both the product and the team's way of working. Options A and B are incorrect because DA explicitly avoids prescribing a single framework or body of knowledge — it is a pragmatic, choice-driven hybrid that tailors practices from Scrum, Kanban, SAFe, PMBOK, and others rather than strictly adhering to Scrum ceremonies or following the PMBOK guide exclusively. Option E is incorrect because DA does not mandate always choosing the newest technology; instead it advises choosing the simplest technology that fits the context and delivers value.

Exam trap

DAF often tests whether candidates can identify DA's actual mindset principles (Optimize Flow, Be Awesome, Context Counts, Choice is Good) versus framework-specific rules or generic agile slogans that are not part of the DA mindset.

Full explanation →
58
MCQhard

A team is deciding when to make a final commitment on a new database technology. They have two viable options and more information will be available in two weeks. According to Lean principles, what should the team do?

A.Commit to both options and build parallel implementations
B.Choose the option with the lowest initial cost immediately to avoid delay
C.Defer the commitment until the last responsible moment
D.Ask the architecture review board to decide immediately
AnswerC

Deferring commitment keeps both options viable until more information arrives, which is the Lean principle of last responsible moment. This reduces the risk of an irreversible choice and allows the team to decide with better data, directly addressing the scenario.

Why this answer

The last responsible moment is the point at which delaying a decision further would cost more than deciding now. Since more information will be available in two weeks, the team should keep both options open until then, reducing risk and avoiding premature commitment.

Exam trap

The trap here is equating decisiveness with immediate action, when Lean actually values delaying irreversible decisions until the cost of waiting outweighs the benefit.

Full explanation →
59
Multi-Selectmedium

A team is reviewing its Way of Working after a difficult quarter. Which TWO actions are consistent with Disciplined Agile's guidance for evolving a Way of Working? (Choose two.)

Select 2 answers
A.Hold a retrospective to identify which practices helped or hindered the team, then adjust them.
B.Replace the entire Way of Working with a different lifecycle without first identifying what is failing.
C.Wait for the annual process audit before changing any practice.
D.Experiment with a small change to one practice in the next iteration and measure the effect.
E.Freeze all process changes for a quarter so the team can focus purely on delivery.
AnswersA, D

Retrospectives are the team's primary mechanism for inspecting its Way of Working and deciding what to change. They connect observed outcomes to specific practices, which supports evidence-based adjustment. This action keeps ownership with the team and aligns with the expectation of continuous improvement rather than periodic redesign.

Why this answer

Evolving a Way of Working in Disciplined Agile relies on the team inspecting its practices and making small, measured adjustments. Retrospectives surface what helps or hinders, and controlled experiments produce evidence for the next change. Deferring to audits, replacing everything at once, or freezing change all remove the team's ability to learn and adapt in a timely way.

Exam trap

The trap here is equating process change with large, formal overhauls, when Disciplined Agile favors small, evidence-based experiments owned by the team.

Full explanation →
60
MCQhard

Why does DA suggest that teams should start with their 'current' process?

A.Because it's the only way the PMO will approve.
B.Because it's a more pragmatic and less disruptive way to evolve.
C.Because all current processes are already perfect.
D.Because it's the easiest way to do nothing.
AnswerB

Beginning with the current process gives a factual baseline, so improvements target real bottlenecks rather than assumed ones. This satisfies the stem's constraint of evolving existing work pragmatically: teams adapt what already functions, minimising disruption and resistance, instead of imposing an unfamiliar process that risks rejection and lost productivity.

Why this answer

DA suggests starting with the current process because it is a more pragmatic and less disruptive way to evolve. By understanding and improving existing processes incrementally, teams can avoid the risks and resistance associated with radical change. This approach aligns with DA's philosophy of continuous improvement and respect for existing context.

Exam trap

The trap is that candidates might think DA advocates for ignoring current processes or that starting with current is just a way to avoid change, but it's actually about pragmatic evolution.

How to eliminate wrong answers

Option A is wrong because PMO approval is not the primary reason; DA focuses on team empowerment and pragmatic evolution, not just compliance. Option C is wrong because DA does not assume current processes are perfect; it acknowledges they can be improved. Option D is wrong because starting with the current process is not about doing nothing; it's about building on what exists to make meaningful improvements.

Full explanation →
61
MCQhard

When applying the Lean principle of 'Optimize the Whole', what should you avoid doing?

A.Optimizing a sub-process without considering the impact on the overall value stream.
B.Identifying bottlenecks in the production pipeline.
C.Aligning team goals with organizational objectives.
D.Analyzing the end-to-end value stream.
AnswerA

Optimising a sub-process in isolation creates local gains that can degrade the overall value stream through handoff delays and rework. Lean's Optimize the Whole principle therefore requires sub-process changes to be assessed against end-to-end flow, which this option correctly identifies as the practice to avoid.

Why this answer

'Optimize the Whole' in Lean means focusing on improving the entire value stream end-to-end rather than optimizing individual sub-processes in isolation. The key thing to avoid is local optimization — improving one sub-process without considering its impact on the overall flow, which can actually harm the whole system. For example, speeding up one station may create a bottleneck downstream or increase WIP elsewhere.

Exam trap

DAF often tests Lean principles by asking what to avoid, and candidates may pick a positive practice like 'identifying bottlenecks' because they misread the question as asking what to do rather than what to avoid.

How to eliminate wrong answers

Option B is wrong because identifying bottlenecks in the production pipeline is a positive Lean activity that supports Optimize the Whole — you must find bottlenecks to improve flow, so this is not something to avoid. Option C is wrong because aligning team goals with organizational objectives is exactly what Optimize the Whole encourages — it ensures local efforts contribute to global value, so it is not something to avoid. Option D is wrong because analyzing the end-to-end value stream is a core practice of Optimize the Whole — value stream mapping is how you identify waste and improvement opportunities across the whole system, so it is not something to avoid.

Full explanation →
62
Multi-Selectmedium

Which TWO of the following statements about 'Guided Continuous Improvement' (GCI) are correct?

Select 2 answers
A.It is only applicable to the software engineering team.
B.It uses the DA toolkit to guide the selection of improvements.
C.It focuses on small, incremental improvements.
D.It requires all teams to improve in the same way.
E.It is a one-time activity at the start of a project.
AnswersB, C

GCI draws on the DA toolkit's process goals and practices as its reference set, so improvement candidates are selected systematically from that body of guidance rather than invented ad hoc, grounding each increment in established DA content.

Why this answer

Option B is correct because Guided Continuous Improvement (GCI) leverages the DA (Disciplined Agile) toolkit — its process goals, practices, and guided tailoring — to help teams deliberately choose which improvements fit their context rather than prescribing a single method. Option C is correct because GCI is built on the principle of small, incremental, evolutionary change: teams make modest adjustments, measure the results, and then decide whether to adopt, adapt, or abandon them, which reduces risk and sustains momentum. Options A, D, and E are incorrect: GCI is not limited to software engineering teams (it applies across the whole organization, including IT, operations, and business groups), it explicitly rejects a one-size-fits-all approach by allowing each team to improve in ways suited to its own situation, and it is a continuous, ongoing discipline rather than a one-time kickoff activity.

Exam trap

DAF often tests the misconception that continuous improvement must be uniform across all teams or limited to certain roles, when in fact GCI is context-sensitive and applies to all teams.

Full explanation →
63
MCQhard

Why might a team intentionally choose a 'Lean' lifecycle over a 'Scrum' lifecycle in the DA toolkit?

A.Because they want to avoid retrospectives.
B.Because it's easier to implement.
C.Because the DA toolkit suggests it for every team.
D.Because their work context is better served by continuous flow than by iterations.
AnswerD

Lean's axis of difference from Scrum is flow-based delivery: work moves continuously through the system rather than being batched into sprints. Choosing Lean satisfies the stem's constraint that the context favours continuous flow over iteration-based cadence.

Why this answer

A team might intentionally choose a Lean lifecycle over a Scrum lifecycle in Disciplined Agile because their work context is better served by continuous flow than by iterations. Lean lifecycles are ideal for work that arrives continuously, such as support or maintenance, where fixed-length iterations may not be suitable. This choice aligns with DA's principle of context-sensitive agility.

Exam trap

DAF often tests lifecycle selection by including options that suggest one lifecycle is universally better or easier, when the correct answer is based on context fit.

How to eliminate wrong answers

Option A is wrong because avoiding retrospectives is not a valid reason; retrospectives are valuable in any lifecycle. Option B is wrong because ease of implementation is not the primary driver; the choice should be based on fit for context. Option C is wrong because the DA toolkit does not suggest one lifecycle for every team; it provides options and guides teams to choose based on their situation.

Full explanation →
64
MCQhard

When a team is using a 'Kanban' system, what is the best way to determine if WIP limits are too high?

A.The cycle time is increasing while throughput remains stable.
B.The board looks too crowded.
C.The team is having too many meetings.
D.The team members are complaining about stress.
AnswerA

Rising cycle time with stable throughput signals that excess work in progress is queueing rather than flowing, since Little's Law ties WIP to cycle time and throughput. This directly satisfies the stem's constraint: WIP limits are too high when items wait longer without additional completed work.

Why this answer

If the cycle time is consistently increasing despite the throughput remaining the same, the WIP is likely too high.

Full explanation →
65
MCQmedium

A team has a very large backlog of items. How should they manage it?

A.Regularly prioritize and refine the backlog
B.Have the project manager manage the backlog in secret
C.Delete half of the backlog to reduce the workload
D.Keep everything in the backlog and work on it sequentially
AnswerA

Regular prioritisation and refinement keeps a large backlog ordered by value and keeps top items estimated and ready for delivery. This satisfies the stem's constraint of an oversized backlog by preventing stale, low-value items from accumulating and obscuring what matters.

Why this answer

A large backlog should be managed through regular prioritization and refinement so that the most valuable items rise to the top and are ready for the team to pull. DA treats the backlog as a living artifact that is continuously groomed rather than a static list. This keeps the team focused on the highest-value work and prevents the backlog from becoming an unusable wish list.

Exam trap

DAF often tests whether candidates recognize that backlog management is a continuous, transparent, prioritization-driven activity, so options that propose secrecy, arbitrary deletion, or sequential processing are planted as plausible but wrong.

How to eliminate wrong answers

Option B is wrong because having the project manager manage the backlog in secret contradicts DA's transparency principle and removes the team's ability to make informed trade-offs. Option C is wrong because deleting half the backlog arbitrarily discards potentially valuable work without prioritization or stakeholder input, which is not a disciplined approach. Option D is wrong because keeping everything and working sequentially ignores prioritization, delays value delivery, and treats the backlog as a queue rather than a prioritized set of options.

Full explanation →
66
MCQmedium

When applying the principle of 'Optimize the Whole', how should you view a 'specialized' sub-team?

A.As a potential silo that should be integrated into cross-functional flow.
B.As the most important part of the organization.
C.As a group that should work at their own pace.
D.As a highly efficient unit that should be kept separate.
AnswerA

A specialized sub-team risks becoming a silo, disrupting the end-to-end value stream that 'Optimize the Whole' prioritises. Integrating it into cross-functional flow removes handoff delays and local optimisation, ensuring its work advances the entire system's throughput rather than a narrow functional agenda.

Why this answer

Specialized teams often act as silos. The goal is to integrate them into a cross-functional unit to improve end-to-end flow.

Full explanation →
67
MCQhard

Your organization is struggling with 'Shadow IT'—teams buying their own software without oversight. What is the Disciplined Agile view on this?

A.Fully decentralize all IT procurement decisions
B.Force all teams to use legacy software only
C.Ban all software purchases by individual teams
D.Provide organizational guidance on standards while allowing for innovation
AnswerD

Disciplined Agile treats Shadow IT as a governance gap, not a crime: publish lightweight standards and guardrails covering security, data and support, then let teams innovate within them. This satisfies the stem by channelling autonomous purchasing into guided choice rather than blanket prohibition.

Why this answer

Disciplined Agile advocates for a balanced approach to Shadow IT, where the organization provides guidance on standards and governance while still allowing teams the flexibility to innovate. This means establishing clear guidelines for software procurement and usage, but not imposing rigid bans that stifle innovation. The goal is to enable teams to make informed decisions that align with enterprise objectives.

Exam trap

DAF often tests the misconception that DA either fully endorses or completely bans Shadow IT, when the correct answer is a balanced approach with guidance.

How to eliminate wrong answers

Option A is wrong because fully decentralizing procurement can lead to chaos and security risks, which DA does not endorse. Option B is wrong because forcing legacy software hinders innovation and agility. Option C is wrong because banning all purchases is overly restrictive and ignores the potential benefits of team-level innovation.

Full explanation →
68
MCQeasy

Which of the following is an example of 'Inventory' waste in software development?

A.The project management software license fees.
B.Code that is written but not yet tested or deployed.
C.The time developers spend in training.
D.The office space rent.
AnswerB

Code written but untested or undeployed sits idle, delivering no value until it is verified and released — exactly the definition of inventory waste in Lean. It satisfies the stem's requirement for work-in-progress that accumulates without flowing downstream, unlike defects, overproduction or waiting, which describe different waste categories.

Why this answer

In Lean and DevOps, 'Inventory' waste refers to work that has been started but not yet completed and delivered — anything sitting in a queue waiting for the next step. Code that is written but not yet tested or deployed is the classic software equivalent of unsold stock on a warehouse shelf: it has consumed effort but delivers no value until it flows through the pipeline. The longer it sits, the more it accumulates risk (merge conflicts, stale assumptions, defects) and the more it costs to eventually finish.

Exam trap

The trap here is confusing any business cost (licenses, rent, training) with Lean's seven wastes — candidates pick a plausible-sounding expense instead of recognizing that 'Inventory' specifically means unfinished work-in-progress, not money spent.

How to eliminate wrong answers

Option A is wrong because a project management software license fee is a direct operating expense (a cost of doing business), not partially-completed work sitting in a queue — Lean would classify it as a necessary cost, not inventory waste. Option C is wrong because time spent in training is an investment in capability and is typically categorized as a form of 'motion' or 'waiting' waste at worst, not inventory — no work-in-progress artifact is accumulating. Option D is wrong because office rent is a fixed overhead/facility cost, which Lean treats as a necessary expense rather than inventory; inventory waste specifically concerns unfinished work items, not physical premises.

Full explanation →
69
MCQeasy

A newly formed team is choosing its Way of Working. A senior manager insists the team must adopt the same detailed process used by another department because it worked there. What does Disciplined Agile recommend the team do?

A.Start from a proven base such as a lifecycle, then tailor practices to the team's context and evolve them over time.
B.Reject all existing practices and invent a completely new process from scratch.
C.Adopt the other department's process unchanged to maintain organizational consistency.
D.Escalate the disagreement to a steering committee for a binding process decision.
AnswerA

This reflects the Disciplined Agile principle that teams should own their Way of Working. Beginning from a proven base reduces risk, while tailoring and ongoing evolution ensure the process fits the team's actual context. It also positions the team to improve continuously rather than defend a borrowed process.

Why this answer

Disciplined Agile expects the team to own its Way of Working, starting from a proven base and tailoring it to context. Blind adoption ignores fit, while wholesale rejection discards useful experience. Tailoring from a lifecycle and evolving over time balances learning from others with adapting to the team's own situation.

Exam trap

The trap here is framing the choice as either fully adopting another team's process or rejecting all existing practice, when the disciplined approach is to start from a proven base and tailor it.

Full explanation →
70
MCQmedium

Why does DA avoid prescriptive workflows?

A.Because teams need to tailor their WoW to their context
B.To allow team leads to manage projects
C.Because documentation is unnecessary
D.To reduce the cost of training
AnswerA

Prescriptive workflows assume one universal way of working, but value streams, team maturity, and constraints differ. DA therefore lets teams design their own way of working, guided by principles and practices, so improvements fit their specific context rather than an imposed template.

Why this answer

DA avoids prescriptive workflows because it recognizes that every team operates in a unique context shaped by its culture, technology, regulations, and customer needs. A prescriptive workflow would force teams into a one-size-fits-all process that may not fit their reality. Instead, DA provides guidance and a toolkit of practices so teams can tailor their Way of Working (WoW) to their specific situation.

Exam trap

The trap here is assuming DA avoids prescriptive workflows for cost or management reasons, when the real reason is contextual tailoring of the Way of Working.

How to eliminate wrong answers

Option B is wrong because DA is not designed to give team leads more project management control; in fact, DA distributes decision-making and emphasizes self-organizing teams. Option C is wrong because DA does not treat documentation as unnecessary; it advocates for the right amount of documentation for the context, not its elimination. Option D is wrong because reducing training cost is not a stated reason for avoiding prescriptive workflows; the rationale is contextual fit, not cost savings.

Full explanation →
71
Multi-Selecthard

Which TWO of the following are examples of 'Active Stakeholder Participation'?

Select 2 answers
A.Stakeholders only reading the final report
B.Stakeholders collaborating on feature prioritization
C.Stakeholders dictating the team's internal coding style
D.Stakeholders providing feedback on iterations
E.Stakeholders attending daily stand-up meetings
AnswersB, D

Collaborative feature prioritisation requires stakeholders to actively shape the product backlog rather than merely receive updates, satisfying the stem's demand for participation that is active. This contrasts with passive consultation or one-way communication, where stakeholders supply input but hold no shared decision-making authority over what gets built.

Why this answer

Option B is correct because active stakeholder participation means stakeholders engage directly in shaping what the team builds, and collaborating on feature prioritization is exactly that kind of ongoing, hands-on involvement in product decisions. Option D is correct because providing feedback on iterations keeps stakeholders continuously engaged throughout development, which is the essence of active participation rather than passive, end-of-project review. Option A is not correct because merely reading a final report is passive, after-the-fact involvement with no influence on the work.

Option C is not correct because dictating the team's internal coding style is inappropriate overreach into technical implementation, not legitimate stakeholder participation. Option E is not correct because daily stand-ups are internal team coordination events, and routine attendance is not the defining example of active stakeholder participation.

Exam trap

DAF often tests the boundary between active and passive stakeholder involvement — candidates pick 'attending daily stand-ups' as active participation, missing that stand-ups are a team-internal ceremony and that active participation means contributing to priorities and feedback, not intruding on team mechanics.

Full explanation →
72
MCQhard

What is the primary role of an 'Agile Coach' in a DA team?

A.To help the team learn and improve their WoW
B.To enforce the rules of the company
C.To act as the project manager
D.To perform the technical coding tasks
AnswerA

An Agile Coach guides the team in refining its way of working, fostering continuous improvement through mentoring and feedback rather than directing delivery. This satisfies the stem's focus on helping the team learn and improve their WoW.

Why this answer

An Agile Coach helps the team improve their way of working, not just manage the work.

Full explanation →
73
MCQmedium

Why does Lean emphasize 'Visible Management' for project boards?

A.It provides transparency that highlights issues without needing meetings.
B.It ensures the project looks good for visiting clients.
C.It is required by the PMO software.
D.It makes it easier for managers to track employees.
AnswerA

Visible boards expose workflow status, blockers and flow metrics to everyone continuously, so problems surface immediately rather than waiting for scheduled meetings. This satisfies Lean's transparency constraint, enabling faster collective response without added coordination overhead.

Why this answer

Visible boards (like Kanban) allow everyone to see the status of the project, identifying bottlenecks and issues without needing a meeting.

Full explanation →
74
Multi-Selecteasy

Which TWO of the following are benefits of an 'Iterative' development approach compared to a waterfall approach?

Select 2 answers
A.Elimination of all documentation.
B.Guaranteed delivery of all original requirements on day one.
C.Reduced focus on software quality.
D.Ability to adapt to changing business needs.
E.Reduced risk through regular stakeholder feedback.
AnswersD, E

Iterative delivery produces working increments each cycle, so feedback arrives while requirements can still be changed cheaply. This satisfies the stem's benefit: unlike waterfall's single late delivery, iterations let the team adapt to changing business needs before significant investment is locked in.

Why this answer

Option D is correct because iterative development delivers software in short, repeated cycles, so newly discovered or changed business requirements can be incorporated in later iterations rather than being frozen at project start as in waterfall. Option E is correct because each iteration typically ends with a review or demo, giving stakeholders regular opportunities to inspect working software and provide feedback, which surfaces defects and misalignments early and thereby reduces overall project risk. The unmarked options do not belong: A is false because iterative approaches still require documentation (though often lighter and evolving), B is false because iterative delivery explicitly accepts that requirements will change and does not guarantee all original requirements on day one, and C is false because iterative methods such as continuous integration and testing generally increase, not reduce, focus on software quality.

Exam trap

DAF often tests the false dichotomy that iterative means 'no documentation' or 'no planning' — candidates must distinguish reduced ceremony from eliminated discipline.

Full explanation →
75
MCQhard

Why does DA distinguish between 'Process Goals' and 'Practices'?

A.To separate the goal (what) from the technique (how).
B.To make the toolkit more complicated.
C.Because they are the same thing.
D.Because only one practice can fulfill a goal.
AnswerA

Process Goals articulate the desired outcome or capability, while Practices describe the specific techniques and routines used to achieve them. Separating the two lets teams adapt their methods without redefining the objective, keeping the what stable while the how evolves.

Why this answer

DA separates Process Goals (the 'what' — the outcomes a team aims to achieve, such as 'Produce a Potentially Consumable Solution') from Practices (the 'how' — the specific techniques or approaches used to achieve those goals, such as continuous integration or test-driven development). This separation allows teams to choose different practices that all serve the same goal, depending on their context. It reinforces the fit-for-purpose philosophy by keeping the goal stable while allowing the technique to vary.

Exam trap

DAF often tests the misconception that Process Goals and Practices are interchangeable or that only one practice can fulfill a goal, when in fact the distinction exists precisely to allow multiple practices per goal.

How to eliminate wrong answers

Option B is wrong because the distinction is not about complexity — it is a deliberate design choice to enable flexibility and context-sensitivity in process tailoring. Option C is wrong because Process Goals and Practices are explicitly different concepts in DA: goals describe desired outcomes, while practices describe the methods used to achieve them. Option D is wrong because DA explicitly recognizes that multiple practices can fulfill a single process goal, which is precisely why the distinction is valuable — teams can select from alternative practices.

Full explanation →

Page 1 of 3

Page 2

All pages

123

Practice DAF by domain

Target a specific domain to shore up weak areas.

Foundations OF Disciplined AgileFoundations OF AgileChoose Your Way OF WorkingFoundations OF Lean
See all domains with question counts →