Courseiva

CCNA Choose Your Way OF Working Questions

49 questions · Choose Your Way OF Working · All types, answers revealed

1
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.

2
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.

3
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.

4
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.

5
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.

6
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.

7
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.

8
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.

9
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.

10
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.

11
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.

12
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.

13
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.

14
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.

15
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.

16
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.

17
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.

18
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.

19
MCQeasy

What is the primary benefit of the 'Guided Continuous Improvement' (GCI) approach in Disciplined Agile?

A.It forces every team to use the exact same metrics.
B.It allows teams to improve their way of working based on their unique context.
C.It eliminates the need for retrospectives.
D.It mandates the use of only one specific lifecycle.
AnswerB

GCI tailors improvement to the team's own context rather than imposing a prescribed method. It satisfies the scenario's need for context-sensitive evolution by guiding teams to inspect their unique situation and select practices that fit, making the way of working genuinely their own.

Why this answer

Guided Continuous Improvement (GCI) is DA's structured approach to helping teams evolve their WoW incrementally based on their own context, pain points, and goals. Rather than imposing a one-size-fits-all process, GCI uses retrospectives and guided workshops to identify improvements that fit the team's unique situation. This is the central mechanism by which DA remains flexible and context-sensitive.

Exam trap

DAF often tests the misconception that continuous improvement means standardizing metrics or eliminating retrospectives, when GCI is actually about context-driven, incremental evolution of the WoW.

How to eliminate wrong answers

Option A is wrong because GCI explicitly rejects uniform metrics — it encourages teams to select measures that matter for their context, not to standardize on one metric set. Option C is wrong because retrospectives are a core input to GCI, not something it eliminates; GCI builds on retrospective findings to drive guided change. Option D is wrong because DA supports multiple lifecycles (Agile, Lean, Continuous Delivery, Program, Exploratory) and GCI helps teams choose and evolve among them — it does not mandate a single lifecycle.

20
MCQmedium

When applying the DA toolkit, what is the best way to determine if a practice is 'fit-for-purpose'?

A.Measure its impact on team outcomes and compare it with the desired goals.
B.See if the team likes it.
C.Check if it's the latest fad in the agile community.
D.Ask the team to vote.
AnswerA

Fit-for-purpose is judged by whether a practise actually improves team outcomes relative to the desired goals, so measuring impact against those goals gives objective evidence. This outcome-based assessment avoids adopting practises merely because they are fashionable or prescribed.

Why this answer

In Disciplined Agile (DA), the DA toolkit is a collection of practices, and 'fit-for-purpose' means the practice should be evaluated based on its measurable impact on team outcomes relative to the team's desired goals. This aligns with DA's principle of 'Be Pragmatic' and its focus on guided continuous improvement. The best way is to measure outcomes and compare them with goals, not rely on subjective preferences or trends.

Exam trap

DAF often tests the misconception that agile practices should be adopted based on team preference or popularity, whereas DA emphasizes empirical measurement against goals to determine fit-for-purpose.

How to eliminate wrong answers

Option B is wrong because whether the team likes a practice is subjective and does not indicate whether it helps achieve business or team goals; DA emphasizes empiricism over popularity. Option C is wrong because adopting the latest agile fad is contrary to DA's pragmatic, context-driven approach; DA explicitly warns against 'agile dogma' and one-size-fits-all solutions. Option D is wrong because voting is a democratic method but not an empirical one; it does not measure the practice's actual impact on outcomes, which is the core of fit-for-purpose assessment in DA.

21
MCQmedium

In the context of the DA toolkit, what does the term 'Process Goal' represent?

A.A set of decision points that teams need to address.
B.A list of KPIs to measure team performance.
C.A project management certification level.
D.A specific set of practices that must be adopted.
AnswerA

A Process Goal defines the decision points teams must address when adopting the DA toolkit, structuring choices across the delivery lifecycle. It satisfies the stem's requirement by framing governance as explicit decisions rather than prescribed steps, enabling teams to tailor adoption while retaining the toolkit's guidance.

Why this answer

In the DA toolkit, a Process Goal represents a set of decision points that teams need to address as they work — it is not a prescribed practice or a metric. Each process goal (such as 'Improve Team Velocity' or 'Address Risk') identifies decisions the team must make and offers a catalog of techniques to help make them. This makes option A the correct definition.

Exam trap

DAF often tests the misconception that DA process goals are prescribed practices or metrics, when they are actually decision points that teams address by choosing from a catalog of optional techniques.

How to eliminate wrong answers

Option B is wrong because KPIs are measurement tools, not process goals — DA process goals are about decisions to be made, and while metrics may inform those decisions, they are not the definition of a process goal. Option C is wrong because a project management certification level is unrelated to DA's process goal concept; DA is a toolkit, not a certification hierarchy. Option D is wrong because DA explicitly avoids prescribing a specific set of practices that must be adopted — process goals are decision points with optional techniques, not mandatory practices.

22
MCQeasy

Which of the following is an example of 'Tailoring' in the DA toolkit?

A.Choosing between different options for 'Explore Scope' based on team size.
B.Ignoring the DA toolkit and using a standard methodology.
C.Increasing the number of meetings.
D.Copying a high-performing team's process exactly.
AnswerA

Selecting an appropriate Explore Scope variant according to team size exemplifies tailoring: the toolkit's processes are adapted to a project's specific context rather than applied uniformly. Tailoring adjusts method rigour, artefacts and roles to suit organisational constraints, which team size directly represents here.

Why this answer

Tailoring in DA means deliberately selecting among the documented options for a process goal based on the team's context — for example, choosing a particular 'Explore Scope' option because the team is small, co-located, and has easy customer access, versus a more formal option for a large distributed team. Option A is a textbook example: the choice is driven by a context factor (team size), which is exactly what tailoring means in the DA toolkit.

Exam trap

DAF often tests the confusion between tailoring (context-based selection among DA options) and ad hoc process change or copying — the key discriminator is whether a documented context factor drove the choice.

How to eliminate wrong answers

Option B is wrong because ignoring the DA toolkit and using a standard methodology is the opposite of tailoring — it is abandoning the toolkit's options entirely rather than selecting among them. Option C is wrong because increasing the number of meetings is a mechanical change with no context-based rationale; it is not tailoring, it is ceremony inflation, and DA would evaluate meeting cadence against communication needs, not add meetings arbitrarily. Option D is wrong because copying another team's process exactly is 'process plagiarism' — it ignores the receiving team's context factors and is precisely what DA warns against; tailoring requires adapting to your own context, not replicating someone else's.

23
MCQhard

A Disciplined Agile team has been using the Agile lifecycle for six months. The organization now requires the team to support a continuous flow of small enhancements while still running two-week iterations for larger features. The team's coach suggests adopting the Lean lifecycle to better handle the flow of work. Which statement best describes the primary reason the Lean lifecycle is appropriate in this situation?

A.It eliminates the need for a product owner and replaces that role with a flow manager.
B.It mandates the use of a specific Kanban tool and predefined work-in-progress limits for all teams.
C.It optimizes for continuous flow and limits work in progress, which suits a steady stream of small enhancements alongside iterative work.
D.It requires the team to abandon iterations entirely and adopt a continuous deployment model.
AnswerC

The Lean lifecycle is designed to optimize flow and limit work in progress, making it well suited to a continuous stream of small enhancements. It allows the team to handle flow-based work while still supporting iterative work for larger features, which matches the organization's new requirement. This is the core reason the Lean lifecycle fits the team's evolving context.

Why this answer

The Lean lifecycle is appropriate because it is optimized for continuous flow and limiting work in progress, which directly addresses the need to handle a steady stream of small enhancements while still supporting iterative work. It provides the flexibility to blend flow and iterations without forcing a full continuous delivery model or removing key roles.

Exam trap

The trap here is believing that adopting the Lean lifecycle forces the team to abandon iterations or adopt a specific tool, when in fact Lean is about flow and WIP limits that can coexist with iterative work.

24
MCQhard

You are assessing the 'Coordinate Activities' process goal for a team that is struggling with knowledge silos. Which decision point should you focus on?

A.Select the lifecycle.
B.Align the team.
C.Manage the budget.
D.Share information.
AnswerD

Sharing information is the decision point that directly dismantles knowledge silos, since silos persist when knowledge stays with individuals. Addressing this point in Coordinate Activities ensures the team distributes understanding across members rather than hoarding it.

Why this answer

The 'Coordinate Activities' process goal in Disciplined Agile includes decision points such as 'Share Information', which directly addresses knowledge silos. Focusing on 'Share Information' helps the team break down silos by improving communication, documentation, and cross-team visibility. This is the decision point most relevant to the described problem.

Exam trap

DAF often tests the mapping of process goals to decision points, so candidates who confuse 'Coordinate Activities' with 'Team' or 'Inception' goals pick the wrong decision point.

How to eliminate wrong answers

Option A is wrong because 'Select the lifecycle' is a decision point in the 'Inception' or 'Foundation' process goal, not 'Coordinate Activities'. Option B is wrong because 'Align the team' is part of the 'Team' process goal, not 'Coordinate Activities'. Option C is wrong because 'Manage the budget' is a financial governance decision point, not part of 'Coordinate Activities'.

25
MCQeasy

What is the purpose of the 'DA Toolkit'?

A.To provide a structured way for teams to tailor their processes.
B.To replace all other agile frameworks.
C.To provide a set of strict rules for Scrum teams.
D.To act as a project management tool like Jira.
AnswerA

The DA Toolkit supplies guidance, practices and process blades that teams combine when choosing their Way of Working. It provides a structured tailoring mechanism rather than a prescriptive method, satisfying the need to adapt processes to each team's context.

Why this answer

The DA Toolkit provides a structured way for teams to tailor their processes by offering a collection of practices, process goals, and decision points. It is designed to help teams choose their way of working (WoW) based on their context, rather than prescribing a rigid set of rules. This makes it a flexible guide for process tailoring.

Exam trap

DAF often tests the purpose of the DA Toolkit versus other frameworks, so candidates who think it is a rigid methodology or a software tool pick the wrong option.

How to eliminate wrong answers

Option B is wrong because the DA Toolkit does not replace other agile frameworks; it complements and integrates practices from them. Option C is wrong because DA is not a set of strict rules for Scrum teams; it is a flexible toolkit that includes Scrum as one of many options. Option D is wrong because the DA Toolkit is not a project management tool like Jira; it is a knowledge base of practices and guidance, not a software tool.

26
MCQeasy

Which DA concept describes the idea that teams should be able to choose their own way of working?

A.Standardized Agile.
B.Choose Your WoW.
C.Command and Control.
D.Managed Delivery.
AnswerB

Choose Your WoW (Way of Working) is the DA principle that teams tailor their practices, roles and ceremonies to their context instead of adopting one mandated process. It directly expresses the idea that teams select their own way of working.

Why this answer

'Choose Your WoW' (Way of Working) is a core Disciplined Agile principle stating that every team is unique and should tailor its process, practices, and lifecycle to its own context rather than being forced into a single mandated method. DA explicitly rejects one-size-fits-all frameworks and instead offers a toolkit from which teams select and evolve their approach. This is why the concept is named 'Choose Your WoW' — it captures team-level autonomy within enterprise guardrails.

Exam trap

The trap here is confusing DA's team-autonomy principle with a named framework or management style — candidates who don't know DA's vocabulary may pick 'Standardized Agile' thinking it sounds disciplined, when DA explicitly rejects standardization.

How to eliminate wrong answers

Option A is wrong because 'Standardized Agile' contradicts DA's philosophy — DA deliberately avoids prescribing one standardized Agile process for all teams. Option C is wrong because 'Command and Control' is the traditional top-down management style that DA explicitly moves away from in favor of self-organizing teams. Option D is wrong because 'Managed Delivery' is not a DA concept describing team autonomy; DA's delivery lifecycles are chosen by the team, not imposed as a managed mandate.

27
MCQmedium

When applying the DA toolkit, you discover that your team's 'Explore Scope' process goal has multiple high-performing options. How do you decide which one to implement?

A.Select the option with the fewest steps.
B.Analyze your team's context factors and select the option that best addresses your current challenges.
C.Randomly select an option to experiment.
D.Select the option that is most popular in the industry.
AnswerB

Context factors are the DA mechanism for choosing between equally viable options; they expose the team's specific constraints and challenges. Selecting the option that best addresses those challenges satisfies the stem's requirement to decide rationally rather than by preference.

Why this answer

DA's process goals are deliberately populated with multiple viable options, and the toolkit does not prescribe which to use. The correct approach is to evaluate the team's specific context factors — such as team size, distribution, regulatory constraints, customer availability, and technical complexity — and select the option whose trade-offs best address the team's current challenges. This is the essence of 'choose your WoW': decisions are context-driven, not popularity-driven or effort-minimizing.

Exam trap

DAF often tests the misconception that DA prescribes a 'best' option per process goal, when in fact it deliberately presents multiple context-dependent options and expects teams to choose based on their own situation.

How to eliminate wrong answers

Option A is wrong because fewest steps does not equal best fit — a lightweight option may omit critical controls (e.g., traceability, stakeholder validation) that a regulated or distributed team genuinely needs, leading to rework or compliance failure. Option C is wrong because random experimentation without a hypothesis or context analysis is not disciplined agile tailoring; DA encourages deliberate, evidence-based selection, not gambling. Option D is wrong because industry popularity is a lagging, context-blind signal — a practice that works at Google or Spotify may fail in a small compliance-heavy team, and DA explicitly warns against copying practices without evaluating fit.

28
Multi-Selectmedium

Which TWO of the following statements about 'Process Goals' in DA are true?

Select 2 answers
A.They must be followed in a specific order.
B.They eliminate the need for retrospectives.
C.They help teams make informed trade-offs.
D.They are only for the Inception phase.
E.They provide a list of options for a team to consider.
AnswersC, E

Process Goals define measurable outcomes that guide decision-making, letting teams evaluate competing design choices against agreed targets. This directly supports informed trade-offs, as the stem states, by giving objective criteria rather than subjective preference when balancing competing architectural concerns.

Why this answer

Option C is correct because Process Goals in Disciplined Agile serve as guidance that helps teams make informed trade-offs, allowing them to balance competing concerns such as scope, quality, and speed when choosing their way of working. Option E is correct because Process Goals are deliberately expressed as a list of options for a team to consider, rather than prescriptive steps, so the team can select the practices that best fit its context. Options A, B, and D are incorrect: Process Goals are not ordered sequentially, they do not replace retrospectives (which remain essential for continuous improvement), and they apply across the entire DA lifecycle, not only during Inception.

Exam trap

DAF often tests the misconception that Process Goals are prescriptive steps that must be followed in order, rather than flexible guidelines for decision-making.

29
Multi-Selectmedium

Which TWO of the following are benefits of using the Disciplined Agile toolkit compared to a single framework like Scrum?

Select 2 answers
A.It eliminates the need for any project management.
B.It guarantees project success.
C.It provides a more comprehensive set of options.
D.It forces teams to deliver faster than Scrum.
E.It allows for context-sensitive process selection.
AnswersC, E

Disciplined Agile offers a broader catalogue of techniques spanning lean, agile and traditional practices, letting teams tailor their way of working rather than being confined to Scrum's prescribed roles and ceremonies. This breadth directly satisfies the stem's requirement for a more comprehensive set of options.

Why this answer

Option C is correct because Disciplined Agile (DA) is explicitly designed as a hybrid toolkit that aggregates practices from Scrum, Kanban, SAFe, XP, Lean, and other sources, giving teams a broader and more comprehensive set of options than any single framework like Scrum can offer. Option E is correct because DA's core premise is context-sensitive process selection: teams use the DA tool kit and guided continuous improvement (GCI) to choose their WoW (Way of Working) based on their specific context—team size, compliance needs, distribution, and domain—rather than being locked into Scrum's prescribed roles, events, and artifacts. Option A is wrong because DA still requires project management disciplines such as planning, risk management, and governance; it does not eliminate them.

Option B is wrong because no framework or toolkit can guarantee project success, and DA explicitly promotes empiricism and adaptation rather than guarantees. Option D is wrong because DA does not mandate faster delivery than Scrum; it aims to optimize flow and fitness for context, not to impose a fixed speed requirement.

Exam trap

DAF often tests the misconception that DA is 'Scrum plus extras' or a prescriptive replacement framework, when in fact it is a decision toolkit whose value is optionality and context-sensitivity, not guaranteed speed or elimination of management.

30
Multi-Selecthard

Which TWO of the following statements correctly describe how a team should evolve its Way of Working according to Disciplined Agile?

Select 2 answers
A.Improvement should be continuous and guided by the team's current context.
B.Teams should rely on external consultants to define their process.
C.Improvements should be based on data and retrospectives to ensure they are effective.
D.Teams should adopt a new framework every quarter to stay modern.
E.Teams should skip retrospectives to maximize delivery time.
AnswersA, C

Disciplined Agile treats improvement as continuous and context-driven: teams inspect their own situation and adapt their Way of Working incrementally, rather than adopting a fixed prescriptive process. This satisfies the principle that guidance must fit the team's actual environment.

Why this answer

Option A is correct because Disciplined Agile (DA) treats the Way of Working (WoW) as something a team continuously evolves and tailors to its own context — the team's size, domain, culture, and constraints — rather than adopting a one-size-fits-all process. Option C is correct because DA's guided continuous improvement (GCI) approach relies on empirical data and regular retrospectives to inspect what is working, identify experiments, and verify that changes actually improve outcomes. Options B, D, and E are incorrect: DA deliberately keeps process ownership with the team rather than outsourcing it to external consultants, rejects the churn of swapping frameworks every quarter in favor of incremental, context-driven improvement, and depends on retrospectives as a core inspect-and-adapt mechanism, so skipping them would undermine the very feedback loop that drives WoW evolution.

Exam trap

DAF often tests the misconception that Disciplined Agile is a prescriptive framework that tells teams exactly which process to adopt, when in fact it is a context-driven toolkit where the team owns and continuously evolves its Way of Working.

31
Multi-Selectmedium

Which TWO of the following are key characteristics of a 'fit-for-purpose' Way of Working?

Select 2 answers
A.It is the same for every team in the company.
B.It is tailored to the team's unique context.
C.It is exactly what the organization's competitors are using.
D.It requires no changes after it is set.
E.It is focused on achieving the team's desired outcomes.
AnswersB, E

A fit-for-purpose Way of Working is deliberately shaped around the team's own context, including size, distribution, domain and constraints, rather than copied wholesale from another team. This contextual tailoring is what makes the approach genuinely fit for purpose.

Why this answer

Option B is correct because a fit-for-purpose Way of Working is deliberately tailored to the team's unique context — its goals, constraints, culture, and ways of collaborating — rather than being imposed uniformly. Option E is correct because the whole point of a fit-for-purpose Way of Working is that it is outcome-driven: it is selected and shaped to help the team achieve its desired results, not to conform to an external standard. Option A is wrong because a one-size-fits-all Way of Working applied identically to every team ignores context and is the opposite of fit-for-purpose.

Option C is wrong because copying competitors' practices assumes their context matches yours and does not guarantee fitness for your team's outcomes. Option D is wrong because a fit-for-purpose Way of Working is expected to evolve as the team's context and goals change, so it is not static.

Exam trap

DAF often tests the misconception that a 'good' WoW is one that matches an industry standard or is uniform across teams, when DA's entire premise is that fit is contextual and outcome-driven.

32
MCQmedium

When applying the DA toolkit, what is the best way to handle conflicting advice from different agile experts?

A.Follow your current process to avoid conflict.
B.Combine both approaches into one process.
C.Evaluate the trade-offs of both approaches within the context of your team's unique situation.
D.Choose the advice from the most famous expert.
AnswerC

Conflicting expert advice reflects differing contexts, not universal truths. Evaluating each approach's trade-offs against your team's specific constraints, skills and goals satisfies the stem's requirement by grounding the decision in your unique situation rather than blind adherence.

Why this answer

Disciplined Agile is a pragmatic, context-driven toolkit rather than a prescriptive method, so conflicting expert advice is resolved by weighing trade-offs against your team's specific situation. Option C reflects the DA principle of 'choice is good' — you tailor practices based on your context, not on authority or avoidance. The DA toolkit explicitly provides guidance for choosing between options via its process goals and decision points.

Exam trap

DAF often tests the misconception that there is one 'correct' agile practice to follow, when the toolkit's core message is that you must evaluate trade-offs against your own context.

How to eliminate wrong answers

Option A is wrong because blindly following your current process ignores the possibility that another approach may fit your context better and contradicts DA's continuous-improvement mindset. Option B is wrong because mechanically combining two approaches often produces an incoherent hybrid with conflicting practices rather than a deliberate, context-fit choice. Option D is wrong because DA rejects appeal-to-authority reasoning — the most famous expert's advice may not suit your team's size, culture, regulatory environment, or lifecycle.

33
MCQeasy

What is the primary benefit of the 'Process Goal' structure in the DA toolkit?

A.It replaces the need for a Project Manager.
B.It provides a clear way to navigate and choose practices.
C.It ensures that teams only use Lean practices.
D.It forces teams to adopt a specific lifecycle.
AnswerB

Process Goals organise the DA toolkit's practices into navigable structures, letting teams select the practices relevant to their current objective. This provides a clear way to navigate and choose practices rather than searching the full catalogue.

Why this answer

The 'Process Goal' structure in the DA toolkit provides a clear way to navigate and choose practices by organizing them around what the team wants to achieve rather than prescribing a fixed set of steps. Each process goal describes a desired outcome and offers a range of practices that can be selected based on context. This structure supports the 'Choose Your WoW' philosophy by making it easier to identify relevant practices.

Exam trap

DAF often tests the misunderstanding that process goals are prescriptive or replace traditional roles, when they are actually a flexible navigation tool for selecting practices.

How to eliminate wrong answers

Option A is wrong because process goals do not replace the need for a Project Manager; DA still recognizes management roles, though they may be distributed. Option C is wrong because process goals are not limited to Lean practices; they encompass agile, lean, and even traditional practices. Option D is wrong because process goals do not force a specific lifecycle; they are designed to support flexibility and choice across lifecycles.

34
MCQhard

A team is using the 'Continuous Delivery: Agile' lifecycle. They find that they are struggling to meet their commitments. Based on DA, what should they evaluate?

A.Switch to a Waterfall lifecycle immediately.
B.Increase the frequency of daily stand-ups.
C.Review their process goals within the DA toolkit to identify potential improvements.
D.Assign a dedicated Scrum Master to force compliance.
AnswerC

DA's process goals define the outcomes each lifecycle activity must achieve, so reviewing them exposes where the team's approach diverges from Continuous Delivery expectations. This targets the commitment shortfall at its process root rather than adjusting estimates.

Why this answer

In DA, when a team struggles to meet commitments, the prescribed response is to examine the relevant process goals in the toolkit and identify which decision points and practices need adjustment — for example, planning, estimation, or coordination practices. This is guided continuous improvement applied to a delivery problem: diagnose against the toolkit, then choose better-fitting options. Switching lifecycles or adding ceremonies without diagnosis would violate DA's context-driven approach.

Exam trap

DAF often tests the misconception that adding more ceremonies or switching frameworks fixes delivery problems, when DA's actual guidance is to diagnose against the process goals and decision points in the toolkit before changing anything.

How to eliminate wrong answers

Option A is wrong because switching to Waterfall is a drastic, context-blind reaction — DA would have the team diagnose the root cause first, and Waterfall is not a DA lifecycle option for this situation. Option B is wrong because increasing stand-up frequency treats a symptom without diagnosis; more stand-ups do not fix estimation, planning, or capacity problems and may add overhead. Option D is wrong because assigning a Scrum Master to 'force compliance' contradicts DA's self-organising, team-owned improvement model — DA does not prescribe enforcement roles to fix delivery problems.

35
MCQeasy

Which DA process goal is specifically concerned with the early stages of a project to ensure the team is aligned?

A.Ensure Continuity.
B.Produce Potentially Consumable Solution.
C.Improve Team Velocity.
D.Inception.
AnswerD

Inception covers the project's early phases: defining scope, identifying stakeholders and agreeing the shared vision. This directly satisfies the stem's alignment goal, since it establishes common understanding before requirements and construction begin, unlike later Disciplined Agile phases such as construction or transition.

Why this answer

Inception is the Disciplined Agile (DA) process goal focused on the early stages of a project — aligning the team around a shared vision, scope, and initial architecture before delivery work begins. It covers activities like forming the team, identifying stakeholders, and setting up the initial plan. The other goals address later lifecycle concerns such as delivery, continuity, and velocity improvement.

Exam trap

DAF often tests the distinction between lifecycle-phase goals (like Inception) and continuous/delivery goals (like Ensure Continuity or Improve Team Velocity), so candidates must map each goal to the correct lifecycle stage rather than picking the most familiar-sounding term.

How to eliminate wrong answers

Option A is wrong because 'Ensure Continuity' is a DA goal focused on sustaining and evolving the solution after delivery, not on early project alignment. Option B is wrong because 'Produce Potentially Consumable Solution' is a delivery-phase goal about producing working increments, not inception-stage alignment. Option C is wrong because 'Improve Team Velocity' is a continuous improvement goal about optimizing flow, not initial team alignment.

36
MCQhard

Why should a team periodically review their 'Way of Working' even if everything seems to be working well?

A.To keep the documentation current for auditors.
B.To justify the team's existence.
C.Because management requires it.
D.Because context is dynamic and a 'fit-for-purpose' WoW needs to evolve.
AnswerD

Team composition, technology, customer expectations and market conditions shift continuously, so a Way of Working tuned to last quarter's context gradually stops fitting. Periodic review keeps it fit for purpose, satisfying the stem's question of why teams inspect their WoW even when nothing currently appears broken.

Why this answer

A Way of Working (WoW) is only 'fit for purpose' relative to the current context — team composition, technology, market conditions, stakeholder expectations, and organizational constraints all shift over time. Even when things appear to be working well, periodic inspection and adaptation of the WoW ensures it continues to serve the team rather than becoming stale or misaligned with new realities. This reflects the underlying agile principle of inspecting and adapting at the process level, not just the product level.

Exam trap

DAF often tests the misconception that a WoW review is only needed when something is broken, when in fact the fit-for-purpose principle requires proactive, periodic inspection even when things appear to be working.

How to eliminate wrong answers

Option A is wrong because keeping documentation current for auditors is a compliance-driven, backward-looking rationale that misses the core reason — the WoW exists to serve the team's effectiveness, not to satisfy external audits. Option B is wrong because justifying the team's existence is a political/organizational concern unrelated to the purpose of reviewing working agreements. Option C is wrong because doing something merely because management requires it is compliance without understanding, and the question asks for the substantive reason a team should review its WoW.

37
MCQmedium

A team is working on a complex project with multiple dependencies. Which process goal is most relevant for managing these?

A.Grow Team Members.
B.Coordinate Activities.
C.Improve Team Velocity.
D.Produce Potentially Consumable Solution.
AnswerB

Coordinate Activities directly addresses managing multiple dependencies by synchronising tasks, resources, and handoffs across teams. It ensures interdependent workstreams align on timing and sequence, satisfying the stem's constraint of a complex project with multiple dependencies. Other goals, such as prioritisation or risk response, do not resolve cross-team sequencing conflicts.

Why this answer

The 'Coordinate Activities' process goal is specifically designed to address the coordination of work across teams, dependencies, and shared resources. In a complex project with multiple dependencies, this goal ensures that activities are aligned, dependencies are managed, and communication flows effectively. It provides the practices and guidance needed to synchronize work across team boundaries.

Exam trap

DAF often tests the confusion between process goals that sound similar, such as 'Coordinate Activities' versus 'Improve Team Velocity,' causing candidates to pick a goal that addresses team-level performance rather than cross-team dependency management.

How to eliminate wrong answers

Option A is wrong because 'Grow Team Members' focuses on individual skill development and career growth, not on managing cross-team dependencies. Option C is wrong because 'Improve Team Velocity' is about optimizing the team's throughput, which is important but not the primary goal for handling complex dependencies. Option D is wrong because 'Produce Potentially Consumable Solution' is about delivering working increments, not about coordinating activities across multiple teams and dependencies.

38
Multi-Selectmedium

Which THREE of the following factors would influence your choice of lifecycle within the DA toolkit?

Select 3 answers
A.The regulatory compliance requirements.
B.The color of the team's office walls.
C.The maturity of the team.
D.The salary of the team members.
E.The duration of the project.
AnswersA, C, E

Regulatory compliance constrains how much documentation, traceability and formal verification a lifecycle must embed. Heavily regulated work pushes teams toward more serial, risk-driven lifecycles, satisfying the stem's requirement for factors that genuinely shape lifecycle selection.

Why this answer

Option A (regulatory compliance requirements) is correct because the DA (Disciplined Agile) toolkit requires lifecycle selection to account for governance and compliance obligations; highly regulated environments favor more predictive, phase-gated lifecycles with documented control points, while low-regulation contexts can safely use agile or lean approaches. Option C (the maturity of the team) is correct because team capability and experience directly shape which lifecycle is viable: a less experienced or newly formed team typically needs the structure and guidance of a predictive or hybrid lifecycle, whereas a mature, self-organizing team can operate effectively with a continuous delivery or lean lifecycle. Option E (the duration of the project) is correct because project length influences lifecycle fit: short, well-bounded efforts suit agile or lean continuous approaches, while long, complex initiatives with evolving scope often benefit from hybrid or predictive lifecycles with staged governance.

Options B (office wall color) and D (team member salaries) are incorrect because they are irrelevant environmental or compensation details that have no bearing on the factors DA uses to guide lifecycle selection, such as compliance, team maturity, project duration, delivery cadence, and solution complexity.

Exam trap

DAF often tests whether candidates can distinguish between factors that directly influence lifecycle choice (compliance, team maturity, duration) and irrelevant distractors (office decor, salaries), so the trap is selecting superficial or budgetary factors instead of governance and capability factors.

39
MCQmedium

A team has decided to add a new 'quality assurance' practice to their WoW. According to DA, what should they do first?

A.Check if it's the 'standard' practice in the company.
B.Ask the vendor for a recommendation.
C.Adopt it immediately and see if it works.
D.Evaluate the practice in the context of their team's goals and constraints.
AnswerD

Disciplined Agile treats practices as options to be deliberately selected, so before adopting a quality assurance practice the team must assess how it fits their goals, constraints and existing way of working, rather than importing it wholesale.

Why this answer

In DA, every practice decision — including adding a new quality assurance practice — must be evaluated against the team's specific goals, constraints, and context factors before adoption. DA's 'choose your WoW' philosophy treats practices as options with trade-offs, not as universal best practices to be adopted on faith. The team should first assess whether the practice addresses a real problem, what it costs in effort and complexity, and how it fits their existing way of working.

Exam trap

The trap is treating DA like a prescriptive framework where you adopt 'best practices' by default; DA requires context-based evaluation first, and 'standard in the company' is a distractor that contradicts DA's anti-standardization principle.

How to eliminate wrong answers

Option A is wrong because 'standard in the company' is a conformity argument, not a fit argument — DA explicitly rejects standardization for its own sake and would have the team evaluate fit even if the practice is common elsewhere. Option B is wrong because vendors sell tools and training, not context-aware process advice; DA decisions should be made by the team using the toolkit's documented trade-offs, not outsourced to a vendor with a commercial interest. Option C is wrong because adopting immediately without evaluation is 'cargo cult' agile — it skips the context analysis and hypothesis-setting that DA requires, and it risks introducing a practice that conflicts with the team's constraints or duplicates existing controls.

40
MCQmedium

A team is consistently failing to complete their planned work. According to DA, what is the best first move?

A.Review their planning practices and choose a more appropriate estimation method from the DA toolkit.
B.Extend the sprint length.
C.Assign blame to the team members.
D.Work weekends to catch up.
AnswerA

Reviewing planning practices and selecting a more suitable estimation method from the DA toolkit addresses the root cause: plans that consistently exceed capacity. It satisfies the stem by fixing how work is sized and forecast, rather than pressuring the team to work longer.

Why this answer

DA's first move when a team consistently misses planned work is to examine the planning and estimation decision points in the toolkit and select practices that better fit the team's context — for example, switching from story points to flow-based forecasting, or adjusting the planning cadence. This is guided continuous improvement applied to a planning problem: diagnose, then choose a better-fitting option from the toolkit.

Exam trap

DAF often tests the misconception that missed commitments should be fixed by extending timelines or working harder, when DA's actual guidance is to review planning and estimation practices and choose a better-fitting option from the toolkit.

How to eliminate wrong answers

Option B is wrong because extending the sprint length treats a symptom without diagnosis — if estimation or capacity is the root cause, a longer sprint simply delays the same failure. Option C is wrong because assigning blame contradicts DA's team-owned, blameless improvement culture and does nothing to fix the underlying planning or estimation problem. Option D is wrong because working weekends is a burnout-inducing anti-pattern that masks the real issue and is explicitly contrary to DA's sustainable-pace and self-organising principles.

41
MCQhard

Why does the DA toolkit explicitly advise against 'standardizing' all teams on the same process?

A.It is cheaper to let teams choose their own.
B.DA is a marketing tool that discourages standardization to sell more training.
C.Standardization is technically impossible.
D.Different teams have different contexts, and a single process would be suboptimal for most.
AnswerD

Standardising every team on one process ignores variation in size, domain, compliance and skill. A single mandated process would be suboptimal for most teams, so Disciplined Agile instead offers a toolkit each team tailors to its own context.

Why this answer

DA is built on the principle that there is no single 'best' process — the best process is the one that fits a team's specific context. Different teams face different constraints: team size, geographic distribution, regulatory compliance, technical debt, customer availability, and organizational culture. Standardizing all teams on one process would force many teams into practices that are suboptimal or even counterproductive for their situation, undermining the very adaptability DA is designed to enable.

DA therefore recommends each team 'choose their WoW' and then consciously evolve it.

Exam trap

The trap here is the false dichotomy that 'no standardization' means 'no consistency at all' — DA permits enterprise-level alignment on governance and tooling while rejecting one-size-fits-all process mandates.

How to eliminate wrong answers

Option A is wrong because cost is not the driver — in fact, letting teams tailor their processes can require more coaching and tooling investment, not less; DA's rationale is effectiveness, not cheapness. Option B is wrong because it is a cynical and factually incorrect claim: DA is an open, freely published toolkit from the Project Management Institute (PMI), and its anti-standardization stance is grounded in systems thinking and complexity theory, not a training sales motive. Option C is wrong because standardization is entirely technically possible — many organizations do it successfully with SAFe or PRINCE2 — DA simply argues it is strategically suboptimal, not impossible.

42
MCQmedium

What is the primary role of the 'DA Flex' (or DA toolkit application) in an organization?

A.To monitor team performance against a standard.
B.To provide a rigid process that must be followed by all.
C.To standardize all team tools.
D.To enable teams to pick the best practices for their specific context.
AnswerD

DA Flex supplies a curated catalogue of delivery practices that teams select and tailor to their own context, rather than imposing one fixed method. This satisfies the stem's emphasis on organisational flexibility, since the toolkit's primary role is guiding context-specific practice choice, not mandating a single standardised process across every team.

Why this answer

The DA Flex (or DA toolkit application) is designed to enable teams to select and tailor the best practices that fit their specific context. It provides a structured but flexible approach, allowing teams to choose from a range of practices rather than imposing a rigid process. This aligns with the Disciplined Agile principle of context-sensitive agility.

Exam trap

DAF often tests the distinction between DA's flexible, context-driven approach and rigid frameworks, so candidates who associate 'toolkit' with 'standardisation' pick the wrong option.

How to eliminate wrong answers

Option A is wrong because monitoring team performance against a standard is not the primary role of DA Flex; DA is about choice and tailoring, not standardised performance monitoring. Option B is wrong because DA explicitly rejects a rigid, one-size-fits-all process; it is a flexible, goal-driven toolkit. Option C is wrong because standardising all team tools is not the purpose of DA Flex; it helps teams choose tools and practices that suit their context, not enforce uniformity.

43
MCQmedium

A newly formed agile team at an insurance company is about to begin its first iteration. The team's coach asks them to select a lifecycle that fits their situation. The team works on a single product, has a co-located product owner, and requires frequent feedback from the business. Which Disciplined Agile lifecycle is the most appropriate starting point for this team?

A.Continuous Delivery: Agile lifecycle
B.Agile lifecycle
C.Program lifecycle
D.Lean lifecycle
AnswerB

The Agile lifecycle is the simplest DA lifecycle and is designed for a single, co-located team delivering one product with a dedicated product owner. It provides short, frequent iterations with continuous stakeholder feedback, which matches the insurance team's need for frequent business input and its single-product focus. It is the recommended starting point before scaling to more complex lifecycles as the team's context evolves.

Why this answer

The Agile lifecycle is the best fit because it is the simplest DA lifecycle and is explicitly designed for a single, co-located team with a dedicated product owner delivering one product. It provides frequent iterations and stakeholder feedback without the coordination overhead of scaling or the engineering demands of continuous delivery, making it the right starting point for a newly formed team.

Exam trap

The trap here is assuming that a more advanced lifecycle such as Continuous Delivery: Agile is always better, when in fact the starting lifecycle should match the team's current context and capability.

44
MCQmedium

When a team is geographically distributed, which process goal should be examined to ensure effective collaboration?

A.Improve Team Velocity.
B.Coordinate Activities.
C.Address Changing Stakeholder Needs.
D.Grow Team Members.
AnswerB

Coordinate Activities addresses how distributed team members align their work, share information and manage dependencies across locations and time zones. It directly satisfies the stem's constraint of geographical distribution, where coordination mechanisms matter more than local practices.

Why this answer

For geographically distributed teams, the process goal 'Coordinate Activities' is directly concerned with ensuring that work is aligned and synchronized across locations. This goal addresses the challenges of communication, handoffs, and dependency management that are exacerbated by distance and time zones. Examining this goal helps the team select practices that enable effective collaboration despite physical separation.

Exam trap

DAF often tests the misconception that any process goal related to teamwork applies to distributed teams, when the specific goal of 'Coordinate Activities' is the one that directly addresses cross-location alignment and dependency management.

How to eliminate wrong answers

Option A is wrong because 'Improve Team Velocity' is a goal about optimizing throughput, not specifically about collaboration in distributed settings — velocity can be improved through many means unrelated to coordination. Option C is wrong because 'Address Changing Stakeholder Needs' focuses on requirements and feedback loops, not on the internal coordination challenges of distributed teams. Option D is wrong because 'Grow Team Members' is about individual skill development and career growth, which, while important, does not directly address the coordination needs of a distributed team.

45
MCQhard

A distributed team has been running the Agile lifecycle for six months. Retrospective data shows that work items frequently sit in review for days, releases are batched quarterly, and the team cannot demonstrate working software to stakeholders between releases. Which change to their Way of Working most directly addresses these symptoms?

A.Move all review work to a separate quality assurance team outside the delivery team.
B.Increase the length of iterations so the team has more time to complete reviews.
C.Adopt a continuous delivery approach with automated deployment and smaller, more frequent releases.
D.Add a dedicated review role and keep the quarterly release cadence.
AnswerC

The symptoms are classic batch-and-queue flow problems: long review waits and quarterly releases. Continuous delivery with automation shortens feedback loops, reduces work-in-progress in review, and makes working software demonstrable frequently. It directly targets the delivery cadence, which is the root cause of all three observed symptoms.

Why this answer

The observed symptoms all trace to large batch sizes and manual gates: review queues, quarterly batching, and no demonstrable software between releases. A continuous delivery approach with automation directly reduces batch size and shortens feedback. Other changes either add capacity to a broken flow or enlarge the batch, leaving the structural cause intact.

Exam trap

The trap here is treating long review times as a capacity problem solvable by adding reviewers, when the real issue is batch size and manual handoffs in the delivery flow.

46
MCQmedium

What should a team do if they find that a practice they chose from the DA toolkit is no longer effective?

A.Try to force the practice to work harder.
B.Stick with it, because consistency is more important than efficiency.
C.Consult the DA toolkit to identify alternative practices that better fit their current situation.
D.Report the failure to the PMO and ask for a new process.
AnswerC

The toolkit is a guided collection of practices, not a fixed prescription. When a chosen practice stops delivering value, the team consults the toolkit to select an alternative that better matches its current context, rather than persisting with an ineffective approach.

Why this answer

Disciplined Agile is explicitly a toolkit of options, not a fixed method: when a chosen practice stops delivering value, the team is expected to revisit the relevant decision point and select a different practice from the toolkit that better fits its current context. This is the essence of 'choose your WoW' combined with guided continuous improvement — the toolkit is the source of alternatives, and the team owns the choice.

Exam trap

DAF often tests the misconception that once a practice is chosen it must be preserved for consistency, when DA actually expects teams to swap practices from the toolkit whenever context or evidence shows a better fit.

How to eliminate wrong answers

Option A is wrong because forcing a failing practice to work harder ignores DA's context-driven philosophy — if the practice no longer fits the situation, effort alone will not fix a poor fit. Option B is wrong because DA values effectiveness over blind consistency; consistency with a practice that is not working is a form of process debt, not a virtue. Option D is wrong because DA places process ownership with the team, not the PMO — escalating to the PMO for a new process contradicts the self-organising, team-owned improvement model that DA advocates.

47
MCQmedium

When two team members disagree on the 'best' practice, how should the team resolve it according to DA?

A.Avoid both and do nothing.
B.The project manager decides.
C.Follow the most senior person's suggestion.
D.Try one, then the other, and see which works better in their context.
AnswerD

Disagreement over practice is settled empirically: run a small experiment with each approach and compare outcomes in the team's own context. DA treats practices as context-dependent options, so evidence from their environment, not authority or theory, determines which works better.

Why this answer

Disciplined Agile advocates for an empirical, context-driven approach to resolving disagreements. Rather than defaulting to authority or seniority, the team should try one practice, then the other, and evaluate which works better in their specific context. This aligns with DA's principle of 'Choice is Good' and its emphasis on guided continuous improvement through experimentation and feedback.

Exam trap

The trap here is assuming that conflict resolution in DA follows traditional authority-based decision-making, when DA actually promotes empirical experimentation and team autonomy.

How to eliminate wrong answers

Option A is wrong because avoiding both practices and doing nothing is a passive approach that stalls progress and ignores the team's responsibility to deliver value. Option B is wrong because having the project manager decide contradicts DA's self-organizing team philosophy and removes ownership from the people doing the work. Option C is wrong because following the most senior person's suggestion is a form of hierarchical deference that may not yield the best technical outcome and undermines team empowerment.

48
Multi-Selectmedium

Which TWO of the following are considered key factors when tailoring your Way of Working within the Disciplined Agile framework?

Select 2 answers
A.The personal preference of the executive sponsor.
B.The specific software vendor of your project management tool.
C.The size of the team.
D.The complexity of the solution being built.
E.The time of year the project starts.
AnswersC, D

Team size directly shapes coordination overhead, communication paths and ceremony weight, so it is a primary tailoring factor in Disciplined Agile. Smaller teams need lighter governance, while larger teams require more structure, making size a genuine axis for choosing the Way of Working.

Why this answer

In Disciplined Agile, tailoring the Way of Working (WoW) is driven by the context of the team and the work, and two recognized key factors are the size of the team (option C) and the complexity of the solution being built (option D). Team size matters because it directly affects coordination, communication, and which lifecycle and practices are viable — for example, a small co-located team can use lighter-weight practices than a large distributed team. Solution complexity matters because more complex, high-risk, or regulated solutions demand more deliberate practices such as architecture modeling, testing, and governance.

By contrast, the executive sponsor's personal preference (A) is not a legitimate tailoring factor, the project management tool's software vendor (B) is irrelevant to WoW selection, and the time of year the project starts (E) has no bearing on how the team should work.

Exam trap

DAF often tests the misconception that tailoring is driven by stakeholder preference or tooling rather than by objective contextual factors like team size and solution complexity.

49
MCQeasy

A team is using a basic Kanban approach and wants to improve their throughput. Which step is most aligned with the DA toolkit?

A.Increase team member hours.
B.Ignore the bottleneck and work faster.
C.Switch to a full Scrum implementation.
D.Review their current process goals and experiment with a practice that limits WIP.
AnswerD

Limiting work in progress directly addresses throughput by reducing multitasking and queueing waste. Reviewing process goals first keeps the experiment deliberate and context-driven, matching Disciplined Agile's guided improvement rather than blindly adopting a prescribed method.

Why this answer

The DA (Disciplined Agile) toolkit emphasizes empirical process improvement through inspecting current goals and experimenting with practices. Limiting WIP is a core Lean/Kanban practice that directly improves flow and throughput by reducing multitasking and bottlenecks. Reviewing process goals and experimenting aligns with DA's guided continuous improvement philosophy.

Exam trap

DAF often tests the misconception that improving throughput requires working harder or switching frameworks, when the DA-aligned answer is to experiment with flow-based practices like WIP limits.

How to eliminate wrong answers

Option A is wrong because increasing hours addresses effort, not flow; it can lead to burnout and does not remove bottlenecks. Option B is wrong because ignoring a bottleneck and working faster worsens the problem by piling up work in progress. Option C is wrong because switching to full Scrum is a prescriptive framework change, not an experiment aligned with DA's pragmatic, context-driven approach.

Ready to test yourself?

Try a timed practice session using only Choose Your Way OF Working questions.