Knowledge + Practice

CCNA Foundations OF Disciplined Agile Questions

49 questions · Foundations OF Disciplined Agile · All types, answers revealed

Practice these questions Domain overview All questions

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.

Practice this question →

2

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.

Practice this question →

3

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.

Practice this question →

4

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.

Practice this question →

5

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.

Practice this question →

6

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.

Practice this question →

7

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.

Practice this question →

8

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.

Practice this question →

9

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.

Practice this question →

10

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.

Practice this question →

11

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.

Practice this question →

12

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.

Practice this question →

13

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.

Practice this question →

14

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.

Practice this question →

15

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.

Practice this question →

16

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.

Practice this question →

17

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.

Practice this question →

18

MCQmedium

A team is transitioning to a 'Lean' lifecycle. What is the most likely change they need to make?

A.Increase batch sizes

B.Add a project manager

C.Require more documentation

D.Focus on continuous flow

AnswerD

Lean lifecycle replaces phase-gated, batch-oriented working with continuous flow, so work moves steadily rather than waiting for stage boundaries. The team must therefore restructure around limiting work in progress and pulling items through, which is the defining behavioural shift from the previous lifecycle.

Why this answer

Lean lifecycle is built around the principle of continuous flow — moving work through the value stream in small batches with minimal wait states, handoffs, and inventory. A team transitioning to Lean must therefore restructure how work moves, reducing batch sizes and eliminating queues so value is delivered steadily rather than in large, infrequent releases.

Exam trap

DAF often tests whether candidates recognize that Lean is fundamentally about flow and small batches — options that increase batch size, documentation, or management layers are Lean anti-patterns dressed up as improvements.

How to eliminate wrong answers

Option A is wrong because increasing batch sizes directly contradicts Lean — larger batches increase work-in-progress, delay feedback, and amplify waste, which is the opposite of what Lean prescribes. Option B is wrong because adding a project manager introduces coordination overhead and a command-and-control role that Lean seeks to minimize; Lean favors self-organizing teams with flow-based coordination. Option C is wrong because requiring more documentation adds non-value-adding work and slows flow; Lean favors just-enough documentation and emphasizes working product over comprehensive artifacts.

Practice this question →

19

MCQmedium

Which DA role helps define the architecture?

A.Team Lead

B.Product Owner

C.Scrum Master

D.Architecture Owner

AnswerD

The Architecture Owner defines the technical architecture and architectural runway, aligning solution design with enterprise standards. This role satisfies the stem's requirement to define architecture by owning design decisions and guiding teams on structural concerns, distinct from the Team Facilitator's process focus or the Product Owner's value prioritisation.

Why this answer

In Disciplined Agile, the Architecture Owner is the role responsible for defining and evolving the architecture of the solution. This role collaborates with the team to ensure that architectural decisions support the team's goals and align with enterprise standards, and is a key part of the DA team structure.

Exam trap

DAF often tests the confusion between traditional roles (like Scrum Master or Product Owner) and DA-specific roles like Architecture Owner — the trap is selecting a familiar role that sounds like it might handle architecture, when DA explicitly defines the Architecture Owner for this purpose.

How to eliminate wrong answers

Option A is wrong because the Team Lead focuses on facilitating the team's self-organisation and removing impediments, not on defining architecture. Option B is wrong because the Product Owner is responsible for representing the customer and prioritising the backlog, not for architectural decisions. Option C is wrong because the Scrum Master (or Team Lead in DA) is a servant-leader who coaches the team on Agile practices, not the architecture owner.

Practice this question →

20

MCQeasy

Which of these is a valid DA lifecycle?

A.The Command lifecycle

B.The Waterfall lifecycle

C.The Static lifecycle

D.The Agile lifecycle

AnswerD

The Agile lifecycle is a recognised Data Analytics lifecycle, structuring analytics delivery into iterative sprints with continuous stakeholder feedback. This satisfies the stem's requirement for a valid DA lifecycle, unlike sequential models that lack iteration. It governs project execution rather than data storage or governance, making it the appropriate lifecycle framework here.

Why this answer

The Agile lifecycle is one of the core lifecycles supported in DA.

Practice this question →

21

MCQhard

Your organization is transitioning to a more agile governance model. Which approach should you adopt to ensure effective decision-making?

A.Lean Governance

B.Command and Control

C.Ad-hoc Decision Making

D.Full Documentation

AnswerA

Lean Governance decentralises decisions to the teams closest to the work, using guardrails and feedback rather than upfront approval gates. Adopting it satisfies the stem's constraint of agile transition, where decision-making must be fast and evidence-based.

Why this answer

Lean Governance focuses on risk-based oversight rather than bureaucratic checklists.

Practice this question →

22

MCQhard

When applying 'Coordinate Activities' across multiple teams, what is the best DA approach?

A.Force all teams to use the same lifecycle

B.Use a regular coordination meeting

C.Appoint a single manager for all teams

D.Merge all teams into one large team

AnswerB

A regular coordination meeting gives multiple teams a recurring, predictable forum to align dependencies, surface blockers and synchronise work, satisfying the cross-team coordination constraint. It is the standard DA technique for scaling coordination beyond a single team's daily stand-up cadence.

Why this answer

DA recommends lightweight, regular coordination mechanisms — such as coordination meetings, scrum of scrums, or communities of practice — to align multiple teams without imposing rigid uniformity. A regular coordination meeting is the canonical DA approach for cross-team alignment. It preserves team autonomy while ensuring dependencies and integration points are managed.

Exam trap

The trap is assuming that scaling coordination requires centralised control or uniform processes, when DA favours lightweight, regular coordination that preserves team autonomy.

How to eliminate wrong answers

Option A is wrong because DA explicitly supports teams choosing different lifecycles (e.g., agile, lean, continuous delivery) based on their context; forcing one lifecycle contradicts the 'choice is good' principle. Option C is wrong because appointing a single manager for all teams reintroduces command-and-control hierarchy, which DA rejects in favour of self-organising teams with clear coordination mechanisms. Option D is wrong because merging teams into one large team destroys the benefits of small, focused teams and creates communication overhead that DA warns against.

Practice this question →

23

MCQmedium

Which DA principle supports the idea that teams should improve their process incrementally?

A.Improve Process

B.Choice is Good

C.Context Counts

D.Enterprise Awareness

AnswerA

Improve Process directly satisfies the incremental improvement principle by embedding continuous, small-scale experimentation into daily work rather than relying on periodic large transformations. Teams assess outcomes, adjust workflows, and repeat, which matches the stem's requirement for gradual, iterative refinement of how work is delivered.

Why this answer

The 'Improve Process' principle in DA states that teams should regularly reflect on and incrementally improve their way of working. It directly supports the idea of incremental process improvement rather than big-bang transformations. This principle encourages small, safe-to-fail experiments.

Exam trap

The trap is mixing up DA principles — candidates may choose 'Choice is Good' or 'Context Counts' because they sound related to improvement, but only 'Improve Process' explicitly addresses incremental process enhancement.

How to eliminate wrong answers

Option B is wrong because 'Choice is Good' is about having options and tailoring, not specifically about incremental improvement. Option C is wrong because 'Context Counts' is about tailoring to the team's environment, not about incremental improvement. Option D is wrong because 'Enterprise Awareness' is about considering the broader organization, not about incremental process improvement.

Practice this question →

24

MCQhard

A Disciplined Agile team is struggling with frequent interruptions and unplanned work. The team lead wants to apply a DA principle to address this. Which of the following actions best reflects the DA principle of 'Deliver value continuously'?

A.Create a separate backlog for interruptions and assign them to a dedicated team member.

B.Increase the team's velocity target to absorb the extra work without changing the process.

C.Escalate to senior management to mandate that stakeholders stop interrupting the team.

D.Limit work in progress, make the cost of interruptions visible, and collaborate with stakeholders to reduce them.

AnswerD

This aligns with the DA principle of delivering value continuously by optimizing flow and addressing impediments. Limiting WIP helps the team finish work before starting new items, making interruptions more visible. Collaborating with stakeholders to reduce unplanned work attacks the root cause. Together, these actions improve predictability and throughput, which are essential for continuous value delivery in a disciplined agile context.

Why this answer

The DA principle of delivering value continuously calls for optimizing flow, making work visible, and collaborating to remove impediments. Limiting WIP and exposing the cost of interruptions helps the team and stakeholders understand the impact and work together to reduce unplanned work, rather than simply absorbing it or escalating without addressing the system.

Exam trap

The trap here is thinking that adding capacity or escalating to management solves the interruption problem, when DA emphasizes making the cost visible and collaborating to address the root cause.

Practice this question →

25

MCQhard

Your team needs to scale their agile efforts. What should be your first step according to DA?

A.Assess the current team maturity and context

B.Switch to Kanban

C.Add a Program Manager

D.Implement SAFe immediately

AnswerA

Assessing current team maturity and context satisfies the stem because Disciplined Agile scaling begins with understanding where the team is now. Only after this baseline can appropriate scaling strategies be selected, avoiding premature or mismatched adoption.

Why this answer

According to Disciplined Agile, the first step when scaling agile efforts is to assess the current team maturity and context. DA emphasizes that scaling is not a one-size-fits-all journey; you must understand where the team is now (their skills, culture, constraints) before choosing a scaling approach. This aligns with DA's principle of 'Context Counts' and its guided continuous improvement approach.

Exam trap

DAF often tests the misconception that scaling agile requires immediately adopting a specific framework like SAFe, whereas DA emphasizes assessing context and maturity first to choose a tailored approach.

How to eliminate wrong answers

Option B is wrong because switching to Kanban is a specific practice choice, not a first step; DA would not prescribe Kanban without first understanding the team's context and needs. Option C is wrong because adding a Program Manager is a structural change that may not address the root need and is not a recommended first step in DA; DA focuses on team-level empowerment and organic scaling. Option D is wrong because implementing SAFe immediately is a prescriptive, framework-specific action that contradicts DA's pragmatic, context-driven philosophy; DA advises against adopting any framework wholesale without assessing fit.

Practice this question →

26

Multi-Selecthard

Which THREE of the following are considered 'Lean' practices in DA?

Select 3 answers

A.Eliminating waste

B.Increasing batch sizes

C.Adding unnecessary roles

D.Reducing WIP

E.Optimizing flow

AnswersA, D, E

Eliminating waste is a core Lean principle, directly satisfying the stem's requirement for Lean DA practises. Lean thinking targets non-value-adding activities such as redundant data transformation, manual rework, and waiting time, so removing them improves flow and efficiency within the analytics pipeline.

Why this answer

In Lean Data Analytics (DA), eliminating waste (A) is a core principle because it removes non-value-adding activities such as redundant data processing, rework, or waiting, directly improving efficiency. Reducing WIP (D) is correct because limiting work-in-progress prevents bottlenecks, shortens cycle times, and aligns with Lean's pull-based, just-in-time approach. Optimizing flow (E) is also correct because Lean emphasizes smooth, continuous delivery of value through value-stream mapping and removing impediments, ensuring data products move steadily from ingestion to insight.

In contrast, increasing batch sizes (B) contradicts Lean by creating larger queues and delaying feedback, while adding unnecessary roles (C) introduces waste in the form of over-processing and organizational bloat, neither of which is a Lean practice.

Exam trap

DAF often tests Lean practices by including opposites such as increasing batch sizes or adding roles, which are anti-patterns in Lean, to confuse candidates.

Practice this question →

27

MCQmedium

Your team is struggling with frequent context switching. As a Disciplined Agile practitioner, which process blade would you consult to better manage your work flow?

A.Team Development

B.Financial Management

C.People Management

D.Coordinate Activities

AnswerD

Coordinate Activities addresses cross-team dependency management and work-flow orchestration, directly tackling the context switching caused by uncoordinated handoffs. Unlike process blades focused on a single team's internal cadence, it governs how multiple teams align their efforts, satisfying the stem's constraint of managing flow across the wider value stream rather than within one team.

Why this answer

The Coordinate Activities process blade in Disciplined Agile focuses on managing the flow of work across teams, including planning, scheduling, and coordinating dependencies. It directly addresses issues like context switching by providing practices to visualize and limit work in progress, manage queues, and coordinate activities to reduce multitasking. This blade encompasses techniques such as kanban, Scrum of Scrums, and other coordination mechanisms that help teams maintain a smooth workflow.

Exam trap

DAF often tests the distinction between process blades that sound similar, such as confusing 'Coordinate Activities' with 'Team Development' or 'People Management' when the question is about managing work flow and reducing context switching.

How to eliminate wrong answers

Option A (Team Development) is wrong because it focuses on building team skills, roles, and capabilities, not on managing work flow or reducing context switching. Option B (Financial Management) is wrong because it deals with budgeting, funding models, and financial governance, which are unrelated to day-to-day work flow management. Option C (People Management) is wrong because it addresses HR-related concerns such as hiring, performance reviews, and career development, not the coordination of work activities.

Practice this question →

28

MCQhard

A Disciplined Agile team is working on a complex product and has identified a high degree of uncertainty in the requirements. The team wants to apply the DA principle of 'Deliver value continuously' while managing risk. Which strategy is most aligned with DA for exploring initial scope?

A.Use a series of short iterations or experiments to explore the problem space and validate assumptions with stakeholders.

B.Delegate all scope decisions to the product owner and have the team focus solely on implementation.

C.Adopt a predictive lifecycle with stage gates to ensure each phase is completed before moving on.

D.Create a detailed requirements specification upfront to eliminate uncertainty before development begins.

AnswerA

DA advocates for iterative and incremental approaches to explore scope when uncertainty is high. Short iterations or experiments allow the team to validate assumptions, gather feedback, and adjust direction quickly. This aligns with the principle of delivering value continuously by producing tangible results early and often. It also manages risk by failing fast and learning. This strategy is a core part of the DA process goal 'Explore Initial Scope' for complex endeavors.

Why this answer

When uncertainty is high, DA recommends using short iterations or experiments to explore the problem space and validate assumptions with stakeholders. This approach enables continuous learning and adaptation, aligning with the principle of delivering value continuously. It also helps manage risk by providing early feedback and allowing the team to pivot as needed.

Exam trap

The trap here is thinking that detailed upfront specification or a predictive lifecycle reduces risk, when in fact DA recommends iterative exploration to address uncertainty.

Practice this question →

29

MCQhard

You are a team lead in a DA environment. How do you resolve a conflict regarding technical direction?

A.Leave it to the Product Owner

B.Consult the Architecture Owner

C.Ask senior management to decide

D.Vote in the team meeting

AnswerB

The Architecture Owner owns technical direction and architectural decisions within a Disciplined Agile team. Escalating a disagreement about technical direction to that role provides an authoritative ruling grounded in architectural context, rather than leaving the conflict to informal negotiation among team members.

Why this answer

In Disciplined Agile, the Architecture Owner is the role responsible for guiding technical decisions, ensuring architectural integrity, and facilitating technical discussions. When a conflict arises regarding technical direction, the team lead should consult the Architecture Owner, who has the expertise and authority to guide the decision. This aligns with DA's principle of organizing around products/services with clear ownership.

Exam trap

DAF often tests role clarity — candidates may confuse the Product Owner's business focus with technical authority, or assume that all decisions should be democratic, missing that DA assigns technical direction to the Architecture Owner.

How to eliminate wrong answers

Option A is wrong because the Product Owner focuses on business value, prioritization, and stakeholder management — not technical direction. Option C is wrong because escalating to senior management bypasses the team's empowerment and the Architecture Owner's role, undermining DA's self-organization principle. Option D is wrong because voting in a team meeting is not the prescribed DA mechanism for resolving technical direction conflicts — technical decisions require architectural expertise, not majority rule.

Practice this question →

30

MCQeasy

What is the primary goal of the 'Form Team' process blade?

A.To handle stakeholder complaints

B.To improve technical skills

C.To define roles and organizational structure

D.To increase team size

AnswerC

Form Team establishes the team's roles, responsibilities and organisational structure before work begins, giving the team its shape and reporting lines. It does not itself plan work or manage flow; those belong to later process blades.

Why this answer

The primary goal of the 'Form Team' process blade in Disciplined Agile is to define roles and organizational structure for the team. This involves establishing the team's composition, roles, responsibilities, and how they will work together. It ensures the team is set up for success by clarifying expectations and structure.

Exam trap

DAF often tests the Form Team process blade by including distractors related to team development or stakeholder management, causing candidates to confuse it with other process blades.

How to eliminate wrong answers

Option A is wrong because handling stakeholder complaints is not the primary goal of Form Team; that would fall under stakeholder management or support processes. Option B is wrong because improving technical skills is part of team development but not the primary goal of Form Team, which focuses on structure and roles. Option D is wrong because increasing team size is not a goal; the focus is on the right size and skills, not simply growth.

Practice this question →

31

Multi-Selecthard

Which THREE of the following are important aspects of DA Governance?

Select 3 answers

A.Lean

B.Command and Control

C.Automated

D.Risk-based

E.Manual and heavy

AnswersA, C, D

Lean thinking underpins Disciplined Agile Governance, guiding decisions toward eliminating waste, limiting work in progress and optimising the whole value stream. Governance that ignores Lean principles tends to add approval overhead rather than enable flow, so Lean is an essential aspect.

Why this answer

DA Governance (Data Analytics Governance) is important because it must be Lean (option A), meaning it should minimize bureaucracy and overhead so that governance enables rather than blocks analytics delivery. It should also be Automated (option C), using tooling, policy-as-code, and automated monitoring/enforcement to keep governance consistent and scalable across data pipelines and models. Finally, it must be Risk-based (option D), prioritizing controls and oversight according to the sensitivity, regulatory impact, and business criticality of the data and analytics use cases.

Options B (Command and Control) and E (Manual and heavy) do not belong because DA Governance deliberately avoids rigid, top-down command-and-control structures and manual, heavyweight processes, which slow down analytics and reduce adoption.

Exam trap

DAF often tests the contrast between traditional command-and-control governance and DA's lean, automated, risk-based governance — candidates who default to heavyweight control pick the wrong options.

Practice this question →

32

MCQeasy

What is the relationship between Portfolio Management and the Team layer in DA?

A.Teams ignore portfolio management

B.Portfolio provides direction to teams

C.They are completely independent

D.Teams set the portfolio strategy

AnswerB

Portfolio Management sets strategic direction, funding and prioritisation that teams then execute within the Team layer. This satisfies the stem's relationship requirement: portfolios govern investment decisions and value streams, while teams deliver against that guidance, creating a directional dependency rather than a peer or reporting one.

Why this answer

In Disciplined Agile, Portfolio Management provides strategic direction to teams by aligning team-level work with organizational goals, funding, and governance. The Portfolio layer sets the context within which teams operate, ensuring that team efforts contribute to the broader enterprise strategy. This relationship is not independent; it is a directional flow from portfolio to teams.

Exam trap

DAF often tests the misconception that portfolio management and teams are independent or that teams set strategy, whereas DA clearly defines portfolio as providing direction to teams.

How to eliminate wrong answers

Option A is wrong because teams do not ignore portfolio management; in DA, teams are aware of and aligned with portfolio direction to ensure their work delivers value. Option C is wrong because they are not completely independent; DA explicitly links layers to enable alignment and coordination. Option D is wrong because teams do not set portfolio strategy; that is the role of the Portfolio layer, which provides direction downward to teams.

Practice this question →

33

MCQmedium

When dealing with stakeholders, what is the best practice in DA?

A.Limit communication to email

B.Actively engage them throughout the process

C.Avoid them until delivery

D.Only talk to their manager

AnswerB

Continuous stakeholder involvement surfaces changing requirements and concerns early, preventing late-stage surprises that derail delivery. Engaging them throughout the process satisfies the need for ongoing alignment and feedback rather than one-off consultation at the start or end.

Why this answer

Best practice in Disciplined Agile (DA) is to actively engage stakeholders throughout the entire lifecycle, not just at the beginning or end. Continuous engagement ensures requirements stay aligned with real needs, feedback is incorporated early, and surprises at delivery are avoided. DA's principle of 'delighting customers' and its emphasis on collaboration make ongoing stakeholder involvement a core practice.

Exam trap

The trap is treating stakeholder engagement as a phase-gate activity (kickoff and delivery only) rather than a continuous practice — DA explicitly rewards ongoing involvement.

How to eliminate wrong answers

Option A is wrong because limiting communication to email is a low-bandwidth, asynchronous channel that loses nuance and prevents the rich, rapid feedback that DA's collaborative approach requires. Option C is wrong because avoiding stakeholders until delivery is the classic waterfall anti-pattern that guarantees misalignment and late rework when expectations diverge from what was built. Option D is wrong because talking only to a stakeholder's manager bypasses the actual domain expert, introduces communication distortion, and violates DA's principle of direct, transparent collaboration with the people who own the requirements.

Practice this question →

34

MCQhard

You are leading a project with highly complex requirements. Which strategy does DA suggest for 'Explore Initial Scope'?

A.Write a full requirements document

B.Delegate to the architecture team

C.Use active stakeholder engagement and modeling

D.Guess the requirements

AnswerC

For highly complex requirements, Disciplined Agile recommends exploring initial scope through active stakeholder engagement combined with modelling techniques. This surfaces hidden complexity and aligns understanding early, rather than committing to a fixed scope before the problem is understood.

Why this answer

Disciplined Agile recommends exploring initial scope through active stakeholder engagement combined with modeling techniques such as user story mapping, impact mapping, and lightweight prototypes. This approach acknowledges that complex requirements cannot be fully specified upfront and are best discovered collaboratively with the people who will use and fund the solution.

Exam trap

DAF often tests whether candidates default to predictive artifacts (full requirements documents) when the question explicitly signals complexity — the correct DA answer almost always favors collaborative, iterative discovery over upfront specification.

How to eliminate wrong answers

Option A is wrong because writing a full requirements document assumes requirements can be known upfront, which contradicts DA's empirical, evolutionary approach to scope on complex initiatives. Option B is wrong because delegating scope exploration to the architecture team silos the work and excludes business stakeholders, producing technically sound but business-misaligned scope. Option D is wrong because guessing requirements is not a strategy — DA explicitly calls for deliberate, collaborative discovery using proven modeling techniques, not speculation.

Practice this question →

35

MCQeasy

A Disciplined Agile team is in the early stages of forming. The team members are unsure about their roles and responsibilities. According to DA, what is the most appropriate first step to clarify roles?

A.Ask the project manager to assign roles based on each member's job title and seniority.

B.Wait until the team encounters role conflicts and then resolve them through escalation.

C.Create a RACI chart that assigns every task to a specific team member.

D.Have the team collaboratively define its way of working, including roles, using the DA process goals as a guide.

AnswerD

DA encourages teams to self-organize and define their own roles and responsibilities as part of establishing their way of working. Using process goals, such as 'Form Team' or 'Coordinate Activities,' provides a structured yet flexible approach. This collaborative definition ensures roles are tailored to the team's context and fosters ownership. It is the most appropriate first step because it aligns with DA's principle of self-organization and context-sensitive tailoring.

Why this answer

DA emphasizes self-organization and context-sensitive tailoring. The team should collaboratively define its way of working, including roles, guided by DA process goals. This approach ensures roles are fit for purpose and owned by the team, rather than imposed externally or deferred until problems arise.

Exam trap

The trap here is assuming that a formal tool like RACI or a manager's assignment is the DA-recommended approach, when DA actually favors collaborative, team-driven role definition.

Practice this question →

36

MCQmedium

Which DA process goal is most relevant when preparing to release a product?

A.Produce a Potentially Consumable Solution

B.Form Team

C.Coordinate Activities

D.Address Risk

AnswerA

Produce a Potentially Consumable Solution ensures the product is built, tested and demonstrably ready to ship. It directly satisfies the stem's release preparation scenario by focusing on delivering consumable increments rather than merely planning or documenting.

Why this answer

'Produce a Potentially Consumable Solution' is the DA process goal focused on creating a solution that is potentially shippable, which is exactly what you need when preparing to release a product. It covers activities like continuous integration, testing, and building a deployable increment. The other goals address team formation, coordination, and risk, which are not release-preparation focused.

Exam trap

DAF often tests whether candidates can distinguish process goals by phase — release preparation maps to producing a consumable solution, not to team formation or risk management.

How to eliminate wrong answers

Option B is wrong because 'Form Team' is about establishing the team, roles, and working agreements — it happens at team inception, not at release time. Option C is wrong because 'Coordinate Activities' addresses aligning work across teams and dependencies, which supports delivery but is not the goal specifically about producing a releasable solution. Option D is wrong because 'Address Risk' focuses on identifying and mitigating risks (technical, business, and delivery), which is important but not the goal that directly produces a consumable increment for release.

Practice this question →

37

MCQeasy

Which process goal is concerned with defining the initial work to be done?

A.Address Risk

B.Explore Initial Scope

C.Form Team

D.Coordinate Activities

AnswerB

Explore Initial Scope defines the vision, initial backlog and high-level requirements before committing to delivery, so the team understands what work is genuinely in play. It satisfies the stem's focus on defining the initial work to be done.

Why this answer

In Disciplined Agile, the Explore Initial Scope process goal is concerned with defining the initial work to be done — understanding the problem space, identifying the initial backlog or work items, and establishing a high-level view of what the team will deliver. It is one of the early process goals in the Inception phase and directly addresses the question of what work is in scope at the outset.

Exam trap

DAF often tests confusion between the Inception-phase process goals — candidates pick Address Risk or Form Team because they sound like early activities, missing that 'defining initial work' maps specifically to Explore Initial Scope.

How to eliminate wrong answers

Option A is wrong because Address Risk focuses on identifying, assessing, and mitigating risks — it is a distinct process goal that runs alongside scope exploration but does not define the initial work. Option C is wrong because Form Team is about establishing the team, its roles, and its WoW, not about defining the work itself. Option D is wrong because Coordinate Activities addresses dependencies and coordination across teams, not the initial definition of scope or work items.

Practice this question →

38

MCQmedium

When applying the DA 'Choose Your WoW' tool, which factor is most important?

A.The budget available

B.Executive preference

C.The team's current context

D.The latest industry trend

AnswerC

Choose Your WoW tailors the way of working to the team's actual situation, so the current context governs which practices fit. This satisfies the stem by making context the decisive input rather than copying another team's approach.

Why this answer

The 'Choose Your WoW' tool in Disciplined Agile is fundamentally about tailoring the way of working to the team's specific context. The most important factor is the team's current situation, including their size, distribution, skills, culture, and the nature of the work. This context-driven approach ensures that the chosen practices are fit for purpose rather than imposed from outside.

Exam trap

DAF often tests the misconception that external factors like budget or executive preference should drive process selection, when DA emphasizes the team's own context as the primary consideration.

How to eliminate wrong answers

Option A is wrong because while budget can constrain options, it is not the most important factor; a low-budget team can still choose effective practices. Option B is wrong because executive preference may influence decisions but should not override the team's context if it leads to poor fit. Option D is wrong because following the latest industry trend is a form of cargo-culting that ignores the team's unique circumstances and can lead to ineffective practices.

Practice this question →

39

MCQeasy

Which of the following is a core DA principle?

A.Choice is Good

B.One right way to work

C.Follow the plan strictly

D.Documentation over code

AnswerA

Choice is Good underpins the core DA principle that users should select their own devices, applications and workflows rather than accept imposed standards. This satisfies the stem's requirement for a core principle by enabling diversity and autonomy, which drives innovation and adaptability across the organisation's technology estate.

Why this answer

'Choice is Good' is one of the foundational DA principles, reflecting the philosophy that teams should be empowered to select the practices, lifecycles, and tools that fit their context. It underpins the entire DA toolkit approach, where multiple options are presented rather than a single prescribed method. This principle distinguishes DA from prescriptive frameworks.

Exam trap

DAF often tests whether candidates confuse DA principles with generic agile slogans — 'Choice is Good' is a specific DA principle, while options like 'One right way' and 'Follow the plan' are distractors that sound plausible to candidates unfamiliar with DA's philosophical foundation.

How to eliminate wrong answers

Option B is wrong because 'One right way to work' is the antithesis of DA — DA explicitly rejects universal best practices in favor of context-driven choice. Option C is wrong because 'Follow the plan strictly' reflects a predictive/waterfall mindset; DA embraces adaptive planning and responding to change. Option D is wrong because 'Documentation over code' is not a DA principle — DA values working solutions and recognizes documentation as one of many concerns, not a priority over working software.

Practice this question →

40

MCQeasy

In the DA toolkit, what does 'WoW' stand for?

A.World of Work

B.Way of Working

C.Work of Wisdom

D.Winning over Work

AnswerB

WoW denotes Way of Working: the agreed practices, ceremonies and conventions a team adopts for delivering work. This satisfies the stem's request for the toolkit's expansion of the acronym, distinguishing it from other DA terms such as the backlog or iteration.

Why this answer

In the Disciplined Agile (DA) toolkit, 'WoW' is the acronym for 'Way of Working.' This term captures the unique combination of principles, practices, and processes that a given team adopts to deliver value in its specific context. DA deliberately uses 'WoW' rather than a fixed methodology because it recognizes that no two teams face identical constraints, so each team's WoW will differ.

Exam trap

DAF often tests acronyms and terminology, and the trap is confusing 'WoW' with a generic business phrase like 'World of Work' rather than the DA-specific 'Way of Working.'

How to eliminate wrong answers

Option A is wrong because 'World of Work' is not a DA term; it is a generic phrase with no meaning in the toolkit. Option C is wrong because 'Work of Wisdom' is a fabricated phrase that does not appear in DA literature. Option D is wrong because 'Winning over Work' is a made-up distractor with no basis in the DA vocabulary.

Practice this question →

41

Multi-Selectmedium

Which TWO of the following are ways to 'Improve Process' in DA?

Select 2 answers

A.Experimenting with new techniques

B.Increasing management oversight

C.Ignoring all feedback

D.Conducting retrospectives

E.Reducing team size

AnswersA, D

Experimenting with new techniques directly satisfies the 'Improve Process' objective by generating empirical evidence about what works, rather than assuming. In DA, improvement demands deliberate variation and measurement, so trialling new techniques produces the data needed to refine and standardise processes. This contrasts with merely documenting or automating existing steps, which cannot reveal better approaches.

Why this answer

In the DevOps Agile Skills Association (DASA) DevOps Agile (DA) framework, improving process means continuously refining how work flows through the value stream. Option A, experimenting with new techniques, is correct because DA encourages a culture of continuous experimentation and innovation, letting teams test new practices and adopt those that demonstrably improve flow and outcomes. Option D, conducting retrospectives, is correct because retrospectives are the structured inspect-and-adapt ceremony where teams regularly review their process, identify impediments, and agree on concrete improvements.

Option B, increasing management oversight, is not a process improvement technique; added control tends to slow flow and undermine the autonomy and self-organization DA promotes. Option C, ignoring all feedback, is the opposite of improvement since feedback loops are essential to learning and adaptation. Option E, reducing team size, is a staffing change rather than a process improvement and can harm the team's capacity and cross-functionality.

Practice this question →

42

MCQmedium

A newly formed Disciplined Agile team is choosing its way of working. The team wants to adopt a strategy that explicitly supports both agile and lean principles while also allowing for traditional governance and compliance requirements. Which of the following best describes the DA-recommended approach to selecting a lifecycle?

A.Start with a hybrid approach that blends agile, lean, and traditional practices, then tailor it based on the team's context.

B.Choose the lifecycle that best fits the team's context, then continuously inspect and adapt the way of working as the situation changes.

C.Adopt the Continuous Delivery lifecycle because it is the most advanced and therefore the most effective for all teams.

D.Select the Agile lifecycle because it is the default and most flexible option for any team.

AnswerB

DA explicitly guides teams to select a lifecycle—Agile, Lean, Continuous Delivery, or a hybrid—based on their specific context, then regularly inspect and adapt that choice. This aligns with the DA principle of context-sensitive agility. It avoids prescribing a one-size-fits-all method and instead encourages deliberate, evidence-based tailoring as the team learns and the environment shifts.

Why this answer

DA rejects a one-size-fits-all method. Teams are expected to choose a lifecycle that fits their context—such as team size, regulatory environment, and delivery cadence—and then continuously inspect and adapt that way of working. This context-driven selection is central to Disciplined Agile and distinguishes it from frameworks that mandate a single approach.

Exam trap

The trap here is assuming that one lifecycle, such as Agile or Continuous Delivery, is universally best rather than selecting based on the team's specific context.

Practice this question →

43

MCQhard

You notice your team's velocity is inconsistent. How should you apply the 'Optimize Flow' principle?

A.Add more team members

B.Identify and remove bottlenecks

C.Increase WIP limits

D.Stop all meetings

AnswerB

Inconsistent velocity signals uneven flow through the value stream, so Optimize Flow requires locating the constraint restricting throughput and eliminating it. Removing bottlenecks smooths delivery cadence, directly addressing the variability described in the stem rather than adjusting estimates or pushing the team harder.

Why this answer

The 'Optimize Flow' principle in Disciplined Agile is about making value move smoothly through the system by finding and eliminating constraints. When velocity is inconsistent, the correct response is to identify bottlenecks — the constraint that limits throughput — and remove or relieve them, which stabilizes flow. This aligns with Lean's theory of constraints and the DA guidance to optimize the whole system rather than local efficiencies.

Exam trap

The trap here is confusing 'optimize flow' with 'work faster' or 'add resources' — candidates often pick adding people or raising WIP limits, which actually degrade flow.

How to eliminate wrong answers

Option A is wrong because adding team members without addressing the constraint increases coordination overhead and can worsen flow (Brooks's Law); it treats a symptom, not the bottleneck. Option C is wrong because increasing WIP limits does the opposite of optimizing flow — higher WIP creates more work in progress, longer queues, and greater variability, violating the core Lean/kanban principle of limiting WIP to improve throughput. Option D is wrong because stopping all meetings removes necessary coordination and feedback mechanisms; DA values purposeful ceremonies, and eliminating them would harm alignment and flow rather than improve it.

Practice this question →

44

MCQhard

When applying 'Enterprise Awareness', what is the most important consideration for a team?

A.Their own speed

B.The latest software tools

C.Their internal team dynamics

D.Alignment with broader enterprise objectives

AnswerD

Enterprise awareness means teams align decisions with the organisation's wider goals, standards and governance rather than optimising locally. Alignment with broader enterprise objectives satisfies this by ensuring team-level choices, such as architecture and tooling, support strategic outcomes and avoid conflicting with enterprise direction.

Why this answer

Enterprise Awareness in Disciplined Agile emphasizes that teams should consider the broader organizational context when making decisions. The most important consideration is alignment with enterprise objectives, ensuring that team goals and activities contribute to the overall strategic direction of the organization. This alignment helps avoid sub-optimization and ensures that teams deliver value that matters to the enterprise.

Exam trap

DAF often tests the tendency to prioritize team-level concerns over enterprise alignment, making options like 'internal team dynamics' seem correct when they are not the most important.

How to eliminate wrong answers

Option A is wrong because focusing solely on team speed can lead to local optimization that may not benefit the enterprise. Option B is wrong because the latest software tools are not the primary consideration; tools should support enterprise objectives. Option C is wrong because internal team dynamics, while important, are secondary to aligning with enterprise goals.

Practice this question →

45

MCQeasy

What is the primary purpose of the 'Disciplined Agile' toolkit?

A.To automate all documentation

B.To force teams to use Scrum

C.To help teams tailor their WoW

D.To replace all project managers

AnswerC

Disciplined Agile exists to guide teams in choosing and tailoring their Way of Working (WoW) to fit their unique context, rather than imposing one prescribed method. This directly satisfies the stem's focus on tailoring, distinguishing it from frameworks that mandate fixed practices.

Why this answer

The Disciplined Agile toolkit is designed to help teams tailor their Way of Working (WoW) to fit their unique context. It provides a comprehensive set of process goals, practices, and strategies that teams can mix and match to create a customized approach. The primary purpose is to guide teams in making informed choices rather than prescribing a one-size-fits-all method.

Exam trap

DAF often tests the misconception that DA is a prescriptive framework like Scrum, when in fact it is a flexible toolkit for tailoring WoW.

How to eliminate wrong answers

Option A is wrong because DA does not aim to automate documentation; it emphasizes right-sized documentation based on context. Option B is wrong because DA is not prescriptive and does not force Scrum; it encourages teams to choose and tailor practices from various sources. Option D is wrong because DA does not seek to replace project managers; it redefines their role and may include them as part of the team.

Practice this question →

46

MCQmedium

You are working in a regulated environment. Which aspect of DA allows you to maintain compliance while staying agile?

A.External Audits

B.Standardized Documentation

C.Stop Agile Adoption

D.Disciplined Agile Governance

AnswerD

Disciplined Agile Governance supplies lightweight guardrails, decision points and compliance checkpoints that satisfy regulatory obligations without imposing heavyweight stage gates. It lets teams remain agile while evidencing the controls auditors require in a regulated environment.

Why this answer

Disciplined Agile Governance is the aspect of DA that enables teams to satisfy regulatory and compliance obligations while remaining agile. It embeds lightweight, scalable governance practices directly into the way of working rather than bolting them on as separate control gates. This lets regulated teams demonstrate fitness-for-purpose and auditability without sacrificing the ability to inspect and adapt.

Exam trap

DAF often tests the misconception that governance must be a heavyweight, external, phase-gate activity, causing candidates to reject 'lightweight and integrated' answers even when the question is explicitly about staying agile.

How to eliminate wrong answers

Option A is wrong because external audits are a compliance verification activity imposed from outside the team, not a DA mechanism for balancing agility and compliance. Option B is wrong because standardized documentation is a documentation strategy, not the governance aspect that reconciles regulatory needs with agile ways of working. Option C is wrong because stopping agile adoption directly contradicts the premise of the question, which is to maintain compliance while staying agile.

Practice this question →

47

MCQeasy

Which layer of the DA framework is responsible for aligning team efforts with the overall enterprise strategy?

A.Portfolio Management

B.Team Level

C.Enterprise Awareness

D.Governance

AnswerA

Portfolio Management coordinates value streams and initiatives across teams, translating enterprise strategy into funded, prioritised work. It is the layer that connects strategy to delivery, ensuring team efforts align with organisational goals rather than local optima.

Why this answer

In the Disciplined Agile framework, Portfolio Management is the layer that connects enterprise strategy to the work of delivery teams by selecting, prioritising, and funding initiatives. It ensures that team efforts roll up to strategic goals rather than operating in isolation. The other layers address team-level or awareness concerns, not strategic alignment.

Exam trap

The trap here is confusing 'Enterprise Awareness' (a mindset principle) with the structural Portfolio Management layer that actually aligns strategy and funding.

How to eliminate wrong answers

Option B is wrong because Team Level concerns how a single team organises its own work (e.g., lifecycle choice, roles, ceremonies) and does not own enterprise strategy alignment. Option C is wrong because Enterprise Awareness is a mindset/principle that encourages teams to consider the broader organisation, not a structural layer that aligns strategy to execution. Option D is wrong because Governance provides guardrails, decision rights, and compliance mechanisms — it constrains and guides work but is not the layer that translates enterprise strategy into funded, prioritised initiatives.

Practice this question →

48

MCQmedium

A team is having trouble delivering value because they lack clear roles. Which DA process goal addresses role definition?

A.Form Team

B.Coordinate Activities

C.Address Risk

D.Explore Initial Scope

AnswerA

Form Team establishes the team's structure, including the roles members occupy and how responsibilities are allocated. Unclear roles therefore point directly at this goal, which defines who does what before the team can deliver value effectively.

Why this answer

In Disciplined Agile, the 'Form Team' process goal explicitly addresses establishing the team's structure, including defining roles, responsibilities, and working agreements. When a team lacks clear roles, the Form Team goal is the correct DA process goal because it covers team formation activities such as identifying needed skills, assigning roles, and establishing how the team will operate. This is distinct from coordination, risk, or scope goals.

Exam trap

DAF often tests the confusion between process goals that sound related — candidates may pick 'Coordinate Activities' or 'Address Risk' when the question specifically asks about role definition, which belongs to 'Form Team'.

How to eliminate wrong answers

Option B is wrong because 'Coordinate Activities' focuses on aligning work across teams and managing dependencies, not on defining internal roles and responsibilities. Option C is wrong because 'Address Risk' deals with identifying, assessing, and mitigating risks; while unclear roles can be a risk, the goal itself is about risk management, not role definition. Option D is wrong because 'Explore Initial Scope' is about understanding the problem space, stakeholders, and high-level requirements at the start of an initiative, not about establishing team roles.

Practice this question →

49

MCQhard

How does DA handle technical debt?

A.Assign it to a separate team

B.Make it visible and plan for remediation

C.Ignore it until the project is over

D.Ban all technical debt

AnswerB

Disciplined Agile treats technical debt as a real, trackable liability rather than ignoring it. Teams record debt items in a backlog, make them visible to stakeholders, and schedule remediation work alongside feature delivery so the debt is consciously repaid.

Why this answer

DA encourages managing technical debt through explicit visibility and planned remediation within the process goals.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Foundations OF Disciplined Agile questions.

Start 20-question session

CCNA Foundations OF Disciplined Agile Questions | Courseiva