Courseiva

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

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

Take a mock examExam hub
Page 2

Page 3 of 3

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

Full explanation →
152
MCQeasy

Which is a common symptom of a 'bottleneck' in a Lean workflow?

A.Very short cycle times.
B.High employee satisfaction levels.
C.The team having no work to do.
D.A queue of work building up before a specific process step.
AnswerD

A growing queue before one process step directly signals that this step's capacity is lower than upstream demand, which is the defining characteristic of a bottleneck in Lean. Work-in-progress accumulates at the constraint rather than flowing smoothly, making the queue itself the visible symptom of limited throughput at that stage.

Why this answer

In Lean, a bottleneck is the process step with the least capacity, causing work to accumulate in front of it. The visible symptom is a queue of work-in-progress (WIP) building up before that step, which increases lead time and hides problems. Identifying and relieving bottlenecks (e.g., via Theory of Constraints) is central to Lean flow.

Exam trap

DAF often tests the misconception that a bottleneck means idle workers — candidates pick 'the team having no work to do' because they confuse bottleneck with starvation, but a bottleneck is characterized by excess WIP queuing before the constrained step.

How to eliminate wrong answers

Option A is wrong because very short cycle times indicate smooth flow, not a bottleneck — bottlenecks lengthen cycle times. Option B is wrong because high employee satisfaction is unrelated to bottleneck detection; while bottlenecks can cause frustration, satisfaction is not a diagnostic symptom. Option C is wrong because having no work to do indicates starvation (underutilization), the opposite of a bottleneck, which is characterized by too much work waiting.

Full explanation →
153
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.

Full explanation →
154
Multi-Selecthard

Which THREE criteria are important to consider when selecting a delivery lifecycle in DA?

Select 3 answers
A.The preferred color of the workspace
B.The office location of the stakeholders
C.Project team size
D.The level of uncertainty
E.Technical complexity
AnswersC, D, E

Team size constrains coordination overhead and ceremony, so it directly shapes whether a lean or more structured lifecycle fits. DA lists it among the selection criteria alongside uncertainty and complexity, because larger teams need more explicit coordination mechanisms than small colocated ones.

Why this answer

In Disciplined Agile (DA), the delivery lifecycle is chosen based on context factors, and three of the options listed are genuine criteria: C (Project team size) matters because larger teams need more coordination and ceremony, favoring a more structured lifecycle such as a continuous delivery or lean lifecycle, while small teams can use lighter approaches; D (The level of uncertainty) is critical because high uncertainty favors an exploratory/agile lifecycle like Lean or Agile, whereas low uncertainty suits a more predictive or continuous delivery approach; and E (Technical complexity) is important because complex technical solutions may require more architecture, integration, and validation, influencing whether a continuous delivery, exploratory, or lean lifecycle fits best. Options A (The preferred color of the workspace) and B (The office location of the stakeholders) are not DA lifecycle selection criteria, as workspace color is irrelevant and stakeholder location is at most a minor environmental factor, not one of the core criteria for choosing a delivery lifecycle.

Full explanation →
155
MCQhard

A Disciplined Agile team is struggling with unpredictable delivery because they frequently receive urgent requests from different business units. The team lead suggests adopting a 'flow-based' approach. Which of the following best describes how a flow-based approach would help this team?

A.It limits work in progress and visualizes the value stream to manage demand and reduce multitasking.
B.It requires all work to be estimated in story points and planned in fixed-length iterations.
C.It mandates a single-piece flow where only one item is worked on at a time by the entire team.
D.It eliminates the need for a product backlog and replaces it with a continuous stream of unplanned work.
AnswerA

A flow-based approach, often implemented with Kanban, uses work-in-progress limits and visual management to expose bottlenecks and balance demand against capacity. By limiting WIP, the team reduces context switching and can better handle urgent requests without derailing all other work. Visualizing the value stream also helps stakeholders see the impact of new requests, enabling more disciplined prioritization.

Why this answer

A flow-based approach helps by making work visible and limiting WIP, which directly addresses the chaos of urgent requests. It allows the team to manage demand, expose capacity constraints, and have data-driven conversations with stakeholders about prioritization. This leads to more predictable delivery even when requests vary, because the team can control the amount of work in process and focus on completing items.

Exam trap

The trap here is confusing flow-based with iteration-based approaches, or assuming that flow means no planning or unlimited work intake.

Full explanation →
156
MCQmedium

When planning, what is the difference between 'Predictive' and 'Adaptive' planning?

A.Predictive planning is not allowed in Disciplined Agile
B.Predictive planning is better for high-uncertainty projects
C.Adaptive planning is always faster than predictive
D.Adaptive planning evolves as the project progresses based on feedback
AnswerD

Adaptive planning deliberately defers detailed scope decisions until feedback from working increments arrives, so the plan is revised each iteration. This contrasts with predictive planning, which fixes scope and schedule upfront. It satisfies the scenario's need for a plan that responds to emerging learning rather than assuming stable requirements.

Why this answer

Predictive planning is upfront and detailed, while adaptive is rolling-wave and iterative.

Full explanation →
157
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.

Full explanation →
158
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.

Full explanation →
159
MCQmedium

During a project, the team realizes the initial plan is no longer viable due to market changes. What should they do?

A.Wait for the end of the year to reassess
B.Ask the stakeholders to force the team to continue
C.Stick to the original plan to show commitment
D.Update the plan and pivot the strategy accordingly
AnswerD

Updating the plan and pivoting preserves alignment with current market reality instead of executing a plan whose assumptions have failed. This satisfies the stem's constraint that the initial plan is no longer viable, reflecting Agile's empirical approach of responding to change over following a fixed, outdated baseline.

Why this answer

Agile teams embrace change and pivot based on empirical evidence and feedback.

Full explanation →
160
Multi-Selecthard

Which THREE of the following strategies help in 'scaling' Agile across multiple teams?

Select 3 answers
A.Increase the number of project managers
B.Use shared communication tools
C.Ensure each team uses a different framework
D.Coordinate activities across teams
E.Establish a consistent 'Definition of Done'
AnswersB, D, E

Scaling requires coordination across team boundaries, and shared communication tools give distributed teams a common channel for status, dependencies and decisions. This directly addresses the scaling constraint of maintaining alignment when work spans multiple teams.

Why this answer

Option B is correct because shared communication tools (e.g., Jira, Confluence, Slack, or Azure DevOps) give distributed Agile teams a single source of truth for backlogs, sprint boards, and impediments, enabling transparency and synchronization at scale. Option D is correct because coordinating activities across teams — through Scrum of Scrums, PI Planning, or dependency-mapping ceremonies — manages cross-team dependencies and integration points that inevitably arise when many teams work on one product. Option E is correct because a consistent Definition of Done ensures every team applies the same quality bar (e.g., code reviewed, tests passed, CI green, documentation updated), so increments from different teams are genuinely integratable and releasable.

Option A is not correct because adding project managers increases overhead and central control rather than enabling the self-organizing, empirical flow that Agile scaling frameworks rely on. Option C is not correct because mixing frameworks per team (e.g., one Scrum, one Kanban, one SAFe) fragments terminology, cadence, and metrics, making cross-team coordination and shared planning far harder.

Exam trap

DAF often tests the misconception that scaling Agile means adding more managers or letting each team choose its own framework — candidates pick 'increase project managers' or 'different frameworks per team' because they sound like autonomy or oversight, but both undermine alignment and coordination.

Full explanation →
161
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.

Full explanation →
162
MCQeasy

A team is new to Lean and wants to understand the purpose of a value stream map. Which statement best describes what a value stream map helps them do?

A.It shows only the steps that add value and ignores all other activities
B.It visualizes the flow of work and information, including delays, to identify waste
C.It assigns blame to the departments that cause the most delays
D.It replaces the need for a retrospective by providing a permanent record
AnswerB

A value stream map captures the sequence of steps, the information flow that triggers them, and the waiting time between them. This end-to-end view exposes waste such as queues and handoffs, which is exactly what helps a new team see where to improve.

Why this answer

A value stream map provides an end-to-end view of how work and information flow, including the delays that consume most of the lead time. By making both value-added and non-value-added steps visible, it gives the team a shared picture for identifying waste and prioritizing improvements.

Exam trap

The trap here is thinking a value stream map only shows value-added steps or is a blame tool, when its real power is exposing delays and waste across the whole flow.

Full explanation →
163
MCQmedium

What is the primary Lean goal of reducing the number of handoffs between specialized teams?

A.To increase the total number of specialized team members.
B.To improve organizational visibility.
C.To minimize the opportunity for information loss and waiting.
D.To reduce the cost of payroll.
AnswerC

Each handoff between specialised teams creates a queue where work waits and knowledge must be transferred. Lean seeks to reduce these handoffs because every transfer risks information loss and adds waiting time, both of which are non-value-add waste.

Why this answer

In Lean, handoffs between specialized teams are a form of waste (specifically, waiting and defects from miscommunication). Each handoff introduces a queue, a transfer of tacit knowledge, and an opportunity for requirements or context to be lost. Reducing handoffs directly shrinks the opportunity for information loss and idle waiting time, which shortens lead time and improves flow.

Exam trap

The trap here is confusing a secondary benefit (visibility, cost) with the primary Lean purpose, which is always waste reduction — specifically minimizing information loss and waiting at handoff boundaries.

How to eliminate wrong answers

Option A is wrong because Lean seeks to optimize flow and value delivery, not to inflate headcount or the number of specialists — adding specialists typically increases handoffs. Option B is wrong because improved visibility is a byproduct of visual management and flow, not the primary reason for reducing handoffs; visibility alone doesn't address the waste of waiting and information decay. Option D is wrong because payroll cost reduction is a financial outcome, not the Lean goal — Lean targets waste elimination and flow, and cost savings may or may not follow.

Full explanation →
164
MCQeasy

Which of the following best describes the 'Respect for People' principle?

A.Removing all performance management.
B.Allowing everyone to work from home.
C.Empowering individuals to improve their own work processes.
D.Paying the highest salaries in the industry.
AnswerC

Empowering individuals to improve their own work processes directly embodies 'Respect for People', which in DAF (Disciplined Agile Framework) means trusting those closest to the work to make decisions about it. This satisfies the principle's core requirement: authority and responsibility for process improvement rest with the people performing the work, not imposed from above.

Why this answer

Respect for people involves empowering them, providing them with the tools they need, and involving them in the improvement process.

Full explanation →
165
MCQhard

A product team is mapping its value stream and discovers that a feature request spends 10 days in 'Development' and 20 days waiting in 'Ready for Release' because releases are batched monthly. The team wants to apply Lean thinking to improve flow. Which action should they take first?

A.Implement a kanban board to visualize the 'Ready for Release' queue.
B.Increase development capacity to reduce the 10 days in development.
C.Reduce the release batch size by moving to more frequent, smaller releases.
D.Assign a release manager to prioritize items in the 'Ready for Release' queue.
AnswerC

The largest delay is the 20-day wait caused by monthly batching. Reducing batch size and increasing release frequency directly attacks that wait, improving flow and reducing lead time. This is a classic Lean approach to eliminate waiting waste and optimize the whole value stream.

Why this answer

The value stream shows that most of the lead time is waiting for release due to monthly batching. Lean teaches that batching creates waiting waste. Reducing batch size and releasing more frequently directly removes that wait, improving flow and delivering value sooner.

Exam trap

The trap here is focusing on the active work time (development) rather than the waiting time, which is the larger waste in the value stream.

Full explanation →
166
MCQmedium

A team notices that it frequently starts new work before finishing current work, and as a result, lead time keeps growing even though everyone is busy. Which Lean principle should the team apply to address this?

A.Create flow
B.Establish pull
C.Limit work in progress
D.Build quality in
AnswerC

Limiting work in progress directly addresses the behavior of starting new work before finishing current work. By capping the number of active items, the team reduces multitasking and queues, which shortens lead time and improves flow, exactly matching the scenario.

Why this answer

The scenario describes classic overload: too many items in progress at once, which increases lead time. Limiting WIP is the direct Lean countermeasure because it forces the team to finish work before starting more, reducing multitasking and queues, and thereby improving flow.

Exam trap

The trap here is selecting a related Lean principle like create flow or establish pull without applying the specific countermeasure that changes the behavior of starting too much work.

Full explanation →
167
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.

Full explanation →
168
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.

Full explanation →
169
Multi-Selectmedium

Which TWO of the following are common pitfalls of 'Push' systems?

Select 2 answers
A.The ability to perfectly match supply with demand.
B.Overwhelming the team with too much work.
C.High levels of team satisfaction.
D.The accumulation of hidden queues.
E.Automatic elimination of defects.
AnswersB, D

Push systems schedule work by forecast rather than capacity, so demand is released regardless of whether the team can absorb it. This inflates work in progress and multi-tasking, directly breaching the stem's pitfall of overwhelming the team with more work than it can deliver.

Why this answer

Option B is correct because a Push system schedules and assigns work based on forecasted demand rather than actual capacity, so more work items are pushed into the team than they can complete, overwhelming the team with too much work. Option D is correct because when work is pushed faster than it can be finished, the excess accumulates as hidden queues (work-in-progress inventory) between process steps, increasing lead times and obscuring the true state of the workflow. Options A, C, and E are incorrect because Push systems are not known for perfectly matching supply with demand (they typically cause mismatch), do not inherently produce high team satisfaction (overload and hidden queues tend to reduce it), and do not automatically eliminate defects (defects must be detected and removed through explicit quality practices).

Exam trap

DAF often tests whether candidates can distinguish push-system pitfalls (overload, hidden queues) from pull-system benefits (matched capacity, visible flow) — the distractors describe pull benefits disguised as push outcomes.

Full explanation →
170
MCQeasy

What is the purpose of a 'Retrospective'?

A.To critique individual performance
B.To report progress to the stakeholders
C.To improve the team's way of working
D.To plan the next set of features
AnswerC

The Retrospective is the dedicated inspect-and-adapt ceremony held at iteration end, where the team examines its own processes and agrees concrete changes. This directly satisfies the stem's purpose of improving the team's way of working, rather than reviewing product scope or individual performance.

Why this answer

Retrospectives are for team reflection and process improvement.

Full explanation →
171
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.

Full explanation →
172
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.

Full explanation →
173
MCQhard

A team is transitioning to a 'Disciplined Agile' way of working. They need to handle 'Governance'. How is governance defined in DA?

A.A set of strict, compliance-driven checkpoints
B.Something that happens only during the final release
C.Lightweight and integrated into the workflow
D.The responsibility of a separate audit department
AnswerC

Disciplined Agile defines governance as lightweight and embedded within the team's workflow, rather than a heavyweight, separate control layer. This satisfies the transition constraint by letting the team self-organise while remaining accountable, with decision-making and compliance checks woven into daily ceremonies instead of imposed through external gate reviews.

Why this answer

In Disciplined Agile, governance is defined as lightweight and integrated into the team's workflow, not as a separate, heavyweight control layer. It is a continuous, collaborative activity that ensures the team is doing the right thing in the right way, and it is owned by the team and its stakeholders. This makes governance compatible with agile delivery rather than opposed to it.

Exam trap

DAF often tests the misconception that governance must be a strict, external, phase-gate activity, so candidates who equate governance with compliance checkpoints pick the wrong answer instead of recognizing DA's lightweight, integrated definition.

How to eliminate wrong answers

Option A is wrong because strict, compliance-driven checkpoints describe a traditional phase-gate governance model, which DA explicitly moves away from. Option B is wrong because governance in DA is continuous throughout the lifecycle, not a one-time event at final release. Option D is wrong because governance is not delegated to a separate audit department; in DA it is a shared responsibility of the team, stakeholders, and enterprise, integrated into daily work.

Full explanation →
174
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.

Full explanation →
175
MCQhard

A team is struggling with the 'Inception' phase. What is the goal of this phase in DAD?

A.Write all the code for the MVP
B.Complete 100% of the project design
C.Gain stakeholder alignment and establish a viable strategy
D.Finalize the budget and vendor contracts
AnswerC

The Inception phase in Disciplined Agile Delivery exists to align stakeholders around a shared vision and secure funding and initial scope before construction begins. Gaining stakeholder alignment and establishing a viable strategy directly satisfies the stem's requirement, since Inception's purpose is precisely to set direction and obtain consensus, not to build or release.

Why this answer

In Disciplined Agile Delivery (DAD), the Inception phase is a short, collaborative start-up effort whose primary goal is to gain stakeholder alignment and establish a viable strategy for the initiative. It is not about producing code or completing design, but about ensuring the team and stakeholders share a common vision and direction before committing to delivery.

Exam trap

DAF often tests the misconception that Inception equals full design or MVP development — candidates pick 'complete 100% of the project design' because it sounds like a thorough start, but DA explicitly rejects big up-front design in favor of alignment and a viable strategy.

How to eliminate wrong answers

Option A is wrong because writing all the code for the MVP is a Construction-phase activity — Inception produces a vision and strategy, not working software. Option B is wrong because completing 100% of the project design contradicts DA's embrace of 'just enough' up-front planning; DA is iterative and design evolves throughout the lifecycle. Option D is wrong because finalizing the budget and vendor contracts is a governance/procurement activity that may occur alongside Inception but is not its defining goal — Inception focuses on alignment and strategy, not contractual closure.

Full explanation →
176
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.

Full explanation →
177
Multi-Selecteasy

Which THREE of the following are foundational Lean thinking principles?

Select 3 answers
A.Mandatory 12-hour work days.
B.Elimination of waste.
C.Respect for people.
D.Centralized, hierarchical decision-making.
E.Continuous improvement (Kaizen).
AnswersB, C, E

Elimination of waste is a core Lean principle, targeting non-value-adding activities such as overproduction, waiting, and defects. It directly satisfies the stem's requirement for foundational Lean thinking, since removing muda increases flow and value delivery, forming the basis of continuous improvement within any Lean transformation.

Why this answer

Option B (Elimination of waste) is a foundational Lean principle because Lean defines value from the customer's perspective and systematically removes the seven wastes (muda) — overproduction, waiting, transport, overprocessing, inventory, motion, and defects — to improve flow. Option C (Respect for people) is equally foundational, as Lean relies on engaging, empowering, and developing employees so they can surface problems and improve their own work, which is why it is often paired with continuous improvement as the two pillars of Lean. Option E (Continuous improvement, or Kaizen) is correct because Lean treats improvement as an ongoing, incremental, everyone-everyday activity rather than a one-time project, using tools such as PDCA and kaizen events to sustain gains.

Option A (Mandatory 12-hour work days) is not a Lean principle; Lean seeks to eliminate overburden (muri) and excessive hours, since fatigue undermines quality and kaizen. Option D (Centralized, hierarchical decision-making) is also not Lean, because Lean favors decentralized, fact-based decisions made close to the work (genchi genbutsu) with input from the people doing the job.

Full explanation →
178
Multi-Selectmedium

Which THREE of the following actions support the Lean principle 'Build Quality In'?

Select 3 answers
A.Deferring testing until the end of the project.
B.Relying on manual testing by an external team.
C.Using automated regression testing.
D.Performing continuous integration.
E.Implementing Test-Driven Development (TDD).
AnswersC, D, E

Automated regression testing detects defects immediately whenever code changes, preventing faults from progressing downstream. This embodies Build Quality In by verifying each increment at source rather than inspecting quality after the fact, satisfying the Lean principle named in the stem.

Why this answer

Option C (Using automated regression testing) is correct because it embeds quality checks into the delivery pipeline, catching defects immediately after each change rather than letting them accumulate, which directly supports building quality in at the source. Option D (Performing continuous integration) is correct because CI automatically builds and tests every commit, providing fast feedback and preventing integration defects from compounding, which is a core mechanism for building quality into the product. Option E (Implementing Test-Driven Development (TDD)) is correct because writing tests before code forces quality requirements into the design and implementation from the start, eliminating defects at the earliest possible point.

Option A (Deferring testing until the end of the project) is not correct because late-stage testing allows defects to accumulate and violates the build-quality-in principle of early detection. Option B (Relying on manual testing by an external team) is not correct because outsourcing manual testing creates delayed, non-continuous feedback and does not embed quality into the development process itself.

Exam trap

DAF often tests the confusion between 'building quality in' (prevention via TDD, CI, automation) and 'testing quality in' (detection via late-stage manual testing) — candidates who pick manual or end-of-project testing misunderstand the Lean principle.

Full explanation →
179
MCQeasy

What is 'Velocity' in an agile project?

A.A measure of the volume of work a team completes per iteration
B.The total number of bugs found in the product
C.The number of hours worked by the team
D.The speed at which the project manager moves tasks
AnswerA

Velocity quantifies completed work per iteration, typically by summing story points or similar size estimates for items meeting the team's definition of done. It is a planning and forecasting input, not a productivity metric, and its value depends on consistent estimation across iterations.

Why this answer

Velocity is a measure of the amount of work a team completes in a given iteration.

Full explanation →
180
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.

Full explanation →
181
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.

Full explanation →
182
MCQmedium

Your team is struggling with scope creep due to unclear requirements from stakeholders. Using Disciplined Agile principles, what is the most appropriate action?

A.Increase the frequency of stakeholder feedback loops
B.Hire a dedicated business analyst to write detailed documentation
C.Lock down the scope for the next six months
D.Ignore the stakeholders until the product increment is finished
AnswerA

Increasing the frequency of stakeholder feedback loops shortens the gap between requirement clarification and delivery, surfacing ambiguity before it becomes scope creep. It satisfies the stem by tightening collaboration cadence, letting the team validate assumptions early and adjust scope continuously.

Why this answer

Scope creep from unclear requirements is best addressed by tightening and increasing feedback loops with stakeholders so requirements are clarified iteratively and misunderstandings surface early. DA favours frequent, lightweight stakeholder collaboration over documentation-heavy or scope-freezing approaches. This aligns with DA's principle of delighting customers through continuous engagement.

Exam trap

The trap is choosing a plan-driven fix (documentation, scope freeze) for an agile problem — DAF expects candidates to favour feedback loops and iterative clarification.

How to eliminate wrong answers

Option B is wrong because hiring a dedicated business analyst to write detailed documentation is a traditional, plan-driven response that adds handoff and delay rather than improving the feedback loop; DA prefers collaborative requirement elaboration. Option C is wrong because locking down scope for six months contradicts agile and DA principles of embracing change and delivering value incrementally — it treats the symptom by freezing requirements rather than resolving ambiguity. Option D is wrong because ignoring stakeholders until the increment is finished guarantees rework and misalignment, directly violating DA's emphasis on continuous stakeholder collaboration.

Full explanation →
183
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.

Full explanation →
184
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.

Full explanation →
185
Multi-Selectmedium

Which TWO of the following are essential components of a successful Value Stream Mapping session?

Select 2 answers
A.Objective data about cycle time and lead time.
B.A mandate from upper management to cut costs.
C.An external facilitator to enforce rigid rules.
D.Participation by the people actually doing the work.
E.A requirement to automate the whole process.
AnswersA, D

Objective cycle time and lead time data anchor the map in measured reality rather than opinion, exposing where queues and delays actually accumulate across the value stream. Without these metrics, the team cannot quantify waste or prioritise improvement efforts, so the session fails to satisfy its core purpose of identifying actionable flow constraints.

Why this answer

Option A is correct because Value Stream Mapping depends on objective metrics such as cycle time (the time to complete one unit of work) and lead time (the total elapsed time from request to delivery), which expose real bottlenecks and delays rather than opinions. Option D is correct because the people who actually perform the work possess the detailed, tacit knowledge of handoffs, wait states, and workarounds, and their participation builds ownership of the resulting improvement actions. Options B, C, and E are not essential: a cost-cutting mandate can distort the map toward blame rather than flow, an external facilitator enforcing rigid rules suppresses the open, honest discussion VSM requires, and full automation is neither necessary nor always desirable since the goal is to identify and remove waste first.

Exam trap

DAF often tests the misconception that VSM is a management-driven cost-cutting or automation exercise, when it is actually a data-driven, practitioner-led flow analysis.

Full explanation →
186
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.

Full explanation →
187
Multi-Selecteasy

Which THREE are characteristics of a 'high-performing' Agile team?

Select 3 answers
A.Shared accountability for results
B.High trust among team members
C.Strict adherence to the initial plan
D.A leader who dictates every action
E.A focus on continuous improvement
AnswersA, B, E

High-performing teams hold collective ownership of outcomes rather than individuals owning isolated tasks. Shared accountability for results satisfies the stem's characteristic, since the team commits to delivering value together and absorbs setbacks as a group instead of assigning blame.

Why this answer

Option A (Shared accountability for results) is correct because high-performing Agile teams collectively own outcomes rather than siloing responsibility, which aligns with Agile principles of self-organizing teams. Option B (High trust among team members) is correct because trust enables open communication, psychological safety, and rapid collaboration, all essential for high performance. Option E (A focus on continuous improvement) is correct because Agile teams regularly inspect and adapt through retrospectives and iterative delivery to raise effectiveness.

Option C is incorrect because Agile values responding to change over strict adherence to an initial plan. Option D is incorrect because Agile teams are self-organizing, not led by a leader who dictates every action.

Exam trap

DAF often tests whether candidates can separate genuine high-performing team traits (trust, shared accountability, continuous improvement) from command-and-control or plan-worship behaviors that sound disciplined but are actually anti-agile.

Full explanation →
188
MCQeasy

A new project team is struggling to choose between a Scrum-based approach and a Lean-based approach. Which Disciplined Agile principle should the coach emphasize to help them decide?

A.Let the senior project manager decide the methodology.
B.Context counts.
C.Always choose Lean as it is inherently superior to Scrum.
D.Follow the Scrum Guide strictly to ensure consistency.
AnswerB

Context counts directs the team to fit their approach to their specific situation rather than defaulting to one method. This satisfies the stem by giving the coach a Disciplined Agile principle for choosing between Scrum and Lean based on actual circumstances.

Why this answer

'Context counts' is one of the foundational Disciplined Agile principles: the right way of working depends on the situation — team size, culture, regulatory environment, product complexity, and customer needs. Rather than dogmatically choosing Scrum or Lean, the coach should guide the team to fit the method to their context using DA's goal-driven, choice-based approach. This is the essence of DA's 'choice is good' philosophy.

Exam trap

DAF often tests the misconception that DA endorses one methodology (Scrum or Lean) as universally superior — candidates who pick a 'best framework' answer miss the core DA principle that context determines the right approach.

How to eliminate wrong answers

Option A is wrong because DA explicitly rejects top-down, command-and-control methodology selection by a single authority — the team owns its way of working (WoW) and evolves it collaboratively. Option C is wrong because DA does not declare any one method inherently superior; Lean and Scrum each fit different contexts, and DA's whole premise is that no single framework is universally best. Option D is wrong because strictly following the Scrum Guide contradicts DA's principle of tailoring and its recognition that Scrum is just one of many viable strategies — DA even documents how Scrum can be extended or hybridized.

Full explanation →
189
MCQeasy

Which of these is a key 'Agile' value?

A.Comprehensive documentation over working software
B.Following processes over individuals and interactions
C.Contract negotiation over customer collaboration
D.Responding to change over following a plan
AnswerD

The Agile Manifesto values responding to change over following a plan, prioritising adaptability when requirements shift. This is the specific value pairing, not a general preference for flexibility, and it directly matches the option as stated.

Why this answer

The Agile Manifesto explicitly states 'Responding to change over following a plan' as one of its four core values. This value acknowledges that in complex product development, requirements and understanding evolve, so the ability to adapt to changing circumstances is more valuable than rigid adherence to an upfront plan. The other three values in the Manifesto are: individuals and interactions over processes and tools, working software over comprehensive documentation, and customer collaboration over contract negotiation.

Exam trap

DAF often tests the Agile Manifesto values by presenting reversed versions — candidates who don't memorize the exact 'X over Y' ordering may select an inverted option that sounds plausible.

How to eliminate wrong answers

Option A is wrong because it reverses the Agile value — the Manifesto values working software over comprehensive documentation, not the other way around. Option B is wrong because it also reverses the value — the Manifesto values individuals and interactions over processes and tools, not the reverse. Option C is wrong because it reverses the third value — the Manifesto values customer collaboration over contract negotiation, not contract negotiation over collaboration.

All three wrong options are direct inversions of the actual Agile Manifesto values, making them easy to eliminate if you know the correct ordering.

Full explanation →
190
MCQmedium

A team finds that their current workflow is plagued by bottlenecks at the quality assurance stage, causing delays in delivery. According to Disciplined Agile, which action should the team prioritize to improve their process?

A.Focus on the process goal 'Coordinate Activities' to ensure all members are aligned.
B.Increase the batch size to allow QA to process more items at once.
C.Implement the 'Improve Team Productivity' process goal by identifying and removing the specific constraint causing the delay.
D.Switch to a purely predictive model to ensure quality gates are strictly followed.
AnswerC

The Improve Team Productivity process goal directs the team to find and eliminate the constraint limiting throughput. Applying it to the QA bottleneck removes the specific delay source, improving delivery flow rather than optimising non-constraint stages.

Why this answer

In Disciplined Agile, when a workflow has a bottleneck (like QA), the team should apply the 'Improve Team Productivity' process goal, which explicitly includes identifying and removing constraints using lean/Theory of Constraints thinking. The QA stage is the constraint; the correct action is to find and eliminate it (e.g., automate tests, cross-train, shift-left quality) rather than optimize elsewhere. This aligns with DA's guidance to address the system constraint, not symptoms.

Exam trap

DAF often tests whether candidates apply lean/ToC thinking (fix the constraint) versus generic coordination or scaling answers that sound plausible but do not address the bottleneck.

How to eliminate wrong answers

Option A is wrong because 'Coordinate Activities' addresses alignment and communication across teams, not the throughput constraint causing delivery delays. Option B is wrong because increasing batch size is the opposite of lean guidance — larger batches increase WIP, delay feedback, and worsen bottlenecks (Little's Law). Option D is wrong because switching to a purely predictive model does not remove the QA constraint; it just changes planning style and often adds rigidity that worsens flow.

Full explanation →
191
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.

Full explanation →
192
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.

Full explanation →
193
MCQeasy

What is the primary benefit of 'Small Batch Sizes' in software development?

A.Faster feedback loops and reduced risk.
B.More time to attend meetings.
C.Lower total cost of labor.
D.Less documentation required.
AnswerA

Smaller batches shorten the interval between producing work and receiving feedback on it, so defects and wrong assumptions surface sooner. That earlier detection lowers the cost of correction and reduces the risk of building large amounts of unwanted functionality.

Why this answer

Small batch sizes reduce the amount of work in progress between steps, which shortens the time to get feedback and limits the blast radius of any single change. Faster feedback lets teams detect defects, misalignments, and market shifts earlier, while smaller changes are easier to test, review, and roll back — directly reducing delivery risk. This is a foundational lean/DA principle (Little's Law and flow efficiency).

Exam trap

DAF often tests whether candidates understand that small batches primarily improve feedback and risk — not cost, documentation, or meeting time — so distractors that sound like efficiency gains mislead.

How to eliminate wrong answers

Option B is wrong because small batches reduce meeting overhead, not increase it — the goal is more flow, not more ceremonies. Option C is wrong because labor cost is not the primary benefit; small batches may even require similar total effort but deliver value sooner and with less rework. Option D is wrong because documentation needs are driven by compliance, complexity, and risk — not by batch size — and small batches do not inherently reduce documentation requirements.

Full explanation →
194
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.

Full explanation →
195
MCQeasy

Which of the following is an example of an 'Agile' feedback loop?

A.Having the team work independently on features
B.Creating a Gantt chart of the project timeline
C.Sending a weekly status email to the project sponsor
D.Conducting a product demo with stakeholders
AnswerD

A product demo gives stakeholders direct visibility of a working increment, letting them inspect it and return feedback that shapes the next iteration. That inspect-and-adapt cycle is the defining Agile feedback loop, satisfying the stem's requirement for a genuine example rather than an internal ceremony.

Why this answer

An Agile feedback loop is any mechanism that shortens the cycle between producing work and receiving validated input from stakeholders, enabling course correction. Conducting a product demo with stakeholders is a classic feedback loop because it puts working product in front of real users or sponsors and generates actionable input that feeds the next iteration.

Exam trap

DAF often tests whether candidates can distinguish genuine two-way feedback loops (demos, reviews, retrospectives) from one-way reporting artifacts (status emails, Gantt charts) that look like communication but do not close the loop.

How to eliminate wrong answers

Option A is wrong because having the team work independently on features is the opposite of a feedback loop — it isolates work and delays integration and validation. Option B is wrong because a Gantt chart is a predictive, plan-driven artifact that documents a fixed schedule rather than generating iterative feedback. Option C is wrong because a weekly status email is one-way reporting to a sponsor, not a two-way feedback mechanism that validates product increments; it reports progress, it does not solicit course-correcting input.

Full explanation →
196
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.

Full explanation →
197
Multi-Selectmedium

Which TWO of the following are 'Lean' concepts applied in DA?

Select 2 answers
A.Mandating a fixed-price contract
B.Forcing team members to work long hours
C.Elimination of waste
D.Maximizing the number of features in a release
E.Optimizing the flow of value
AnswersC, E

Eliminating waste removes activities that consume effort without adding customer value, such as waiting, rework and handoffs. This satisfies the stem's requirement for a Lean concept applied in DA, since waste elimination is the foundational Lean principle underpinning value-stream mapping and continuous improvement.

Why this answer

Option C, elimination of waste, is a core Lean concept: Lean defines value from the customer's perspective and systematically removes non-value-adding activities (muda) such as waiting, handoffs, rework, and partially done work, which in DA (Disciplined Agile) translates into streamlining ceremonies, artifacts, and governance. Option E, optimizing the flow of value, is likewise central to Lean thinking: it emphasizes making value flow smoothly through the delivery pipeline by limiting work in progress, reducing batch sizes, and pulling work rather than pushing it, which DA applies through its value stream and continuous improvement guidance. The unmarked options do not belong: A (mandating a fixed-price contract) is a contractual/commercial constraint, not a Lean principle, and Lean favors adaptive, value-driven agreements; B (forcing long hours) contradicts Lean's respect for people and sustainable pace, and overwork increases defects and waste; D (maximizing the number of features in a release) is output-focused rather than value-focused and conflicts with Lean's aim of delivering only what the customer values while minimizing waste.

Exam trap

DAF often tests whether candidates can distinguish genuine Lean concepts from generic management or productivity directives, so options like fixed-price contracts, long hours, and feature maximization are planted as plausible-sounding but anti-Lean distractors.

Full explanation →
198
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.

Full explanation →
199
MCQeasy

What is a 'Pull' system in Lean?

A.Work is pushed by management to the team.
B.Work is completed as fast as possible regardless of quality.
C.Work is assigned based on seniority.
D.Work is initiated only when there is available capacity.
AnswerD

Work is initiated only when there is available capacity, which is precisely the demand-driven mechanism defining a pull system. Downstream consumption signals upstream production, so nothing is built without a real need, eliminating overproduction and excess work-in-progress. This satisfies the stem's requirement for a system where output responds to actual demand rather than forecast.

Why this answer

A Pull system in Lean means work is initiated only when there is available capacity — downstream processes 'pull' work from upstream only when they are ready to process it. This contrasts with a Push system where work is forced onto the team regardless of capacity. Pull systems prevent overproduction, reduce WIP, and expose bottlenecks, making them foundational to Just-In-Time (JIT) delivery.

Exam trap

DAF often tests the Push vs Pull distinction by describing Push behavior in the correct answer's wording — candidates who don't know that Pull is capacity-driven may select the Push option thinking it sounds like active management.

How to eliminate wrong answers

Option A is wrong because work being pushed by management to the team describes a Push system, which is the opposite of Pull — Push systems create queues and waste. Option B is wrong because completing work as fast as possible regardless of quality describes a reckless speed-focused approach, not Pull — Pull systems emphasize flow and quality, not raw speed at the expense of standards. Option C is wrong because assigning work based on seniority is an organizational hierarchy practice unrelated to Pull — Pull is about capacity-based work initiation, not who gets assigned what.

Full explanation →
200
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.

Full explanation →
201
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.

Full explanation →
202
MCQmedium

A team has identified 'task switching' as a primary source of waste. What is the most effective Lean practice to address this?

A.Host more frequent brainstorming meetings.
B.Establish strict WIP limits for each workflow state.
C.Assign a dedicated task-manager to monitor progress.
D.Rotate team members daily to ensure skill diversity.
AnswerB

Task switching stems from people holding too many items at once, so limiting work in progress per workflow state constrains concurrent load. This directly satisfies the stem's constraint by reducing multitasking and its associated waste.

Why this answer

WIP limits directly cap the number of items allowed in each workflow state, which forces the team to finish work before starting new work. This eliminates the multitasking and context-switching overhead that arises when people juggle multiple in-progress items simultaneously. Lean theory (and the Kanban method) treats WIP limits as the primary mechanism for reducing task switching and improving flow.

Exam trap

DAF often tests the misconception that adding coordination roles or meetings solves flow problems, when the real Lean answer is always to constrain WIP and let the system pull work.

How to eliminate wrong answers

Option A is wrong because more meetings add coordination overhead and do not constrain the amount of concurrent work, so task switching continues unabated. Option C is wrong because a task-manager role adds a monitoring layer without changing the underlying cause — the number of simultaneously active work items. Option D is wrong because rotating team members daily increases context switching and knowledge-transfer costs, directly worsening the problem rather than solving it.

Full explanation →
203
MCQmedium

Your team is experiencing 'context switching' due to frequent interruptions. Which Lean-inspired action is most appropriate?

A.Ask the team to work longer hours.
B.Require team members to answer emails immediately.
C.Increase the number of daily meetings.
D.Implement 'focus time' where interruptions are restricted.
AnswerD

Scheduled focus time directly removes the interruptions causing context switching, satisfying the stem's constraint of frequent disruption. Unlike flow-efficiency or value-stream measures, it targets the cognitive reload cost itself by blocking inbound requests during defined periods, letting developers sustain attention on one task before switching.

Why this answer

Context switching from frequent interruptions destroys flow and increases cycle time, a form of Lean waste (muda). Implementing protected 'focus time' where interruptions are restricted directly addresses the root cause by allowing uninterrupted work, consistent with Lean's respect for people and flow efficiency. This is a low-cost, team-driven countermeasure.

Exam trap

DAF often tests the reflex to solve flow problems with more effort or more meetings — the trap is missing that Lean addresses root causes (interruptions) rather than symptoms (slow delivery).

How to eliminate wrong answers

Option A is wrong because longer hours increase fatigue and defect rates without addressing the interruption source, violating Lean's respect-for-people principle. Option B is wrong because requiring immediate email responses institutionalizes the very interruptions causing context switching. Option C is wrong because more daily meetings add coordination overhead and fragment available focus blocks further.

Full explanation →
204
Multi-Selecteasy

Which TWO are common 'Agile' ceremonies?

Select 2 answers
A.Retrospective
B.Budget approval meeting
C.Project planning meeting (held once at the start)
D.Weekly status report to executives
E.Sprint Planning
AnswersA, E

The retrospective is a recurring inspect-and-adapt ceremony where the team examines its process and agrees improvements. It is a standard Agile event, distinct from Disciplined Agile's broader process-goal guidance, and satisfies the stem by being one of the two commonly recognised ceremonies.

Why this answer

Retrospective (A) is a core Agile ceremony held at the end of each iteration/sprint, where the team inspects how it worked and identifies improvements to apply in the next sprint. Sprint Planning (E) is also a standard Scrum/Agile ceremony that occurs at the start of every sprint to define the sprint goal and select the backlog items the team will deliver. Both are recurring, team-level events that support iterative delivery and continuous improvement.

In contrast, budget approval (B) and weekly executive status reporting (D) are governance/reporting activities rather than Agile ceremonies, and a one-time project planning meeting at the start (C) reflects a traditional waterfall approach, not the recurring planning cadence of Agile.

Exam trap

DAF often tests whether candidates can distinguish recurring agile ceremonies (Sprint Planning, Retrospective, Daily Scrum, Sprint Review) from traditional project management meetings (budget approval, one-time planning, executive status reports).

Full explanation →
205
Multi-Selectmedium

Which TWO of the following are valid ways for an Agile team to improve their way of working (WoW)?

Select 2 answers
A.Copy the process of the highest-performing team in the company
B.Experiment with new practices in a controlled way
C.Wait for management to dictate new processes
D.Hold regular retrospectives to identify improvements
E.Use the exact same tools as other teams
AnswersB, D

Controlled experimentation lets a team trial a new practice within bounded scope, measure the effect and retain or discard it. This satisfies the stem's requirement for a valid improvement route, since it changes the way of working based on evidence rather than assumption.

Why this answer

Option B is correct because Agile teams improve their way of working through deliberate experimentation: trying a new practice on a small scale, measuring its effect, and inspecting and adapting based on the results, which is the essence of empiricism. Option D is correct because the retrospective is the dedicated Scrum/Agile event where the team regularly inspects how it works and identifies concrete improvements to apply in the next iteration, making it the primary mechanism for continuous WoW improvement. Option A is not valid because blindly copying another team's process ignores the team's own context, constraints, and empirical data, and best practices cannot simply be transplanted.

Option C is not valid because Agile teams are self-managing and own their process; waiting for management to dictate processes contradicts self-organization and continuous improvement. Option E is not valid because adopting identical tools does not improve a team's way of working and may not fit the team's needs, since tools are enablers rather than the source of process improvement.

Exam trap

DAF often tests the distinction between active, team-driven improvement (experimentation and retrospectives) and passive or imitative approaches (copying others, waiting for management) — the trap is selecting answers that sound plausible but violate DA's principles of empowerment and context-driven improvement.

Full explanation →
206
MCQeasy

A team is transitioning from a traditional project management approach to Disciplined Agile. Which mindset shift is most critical for the team to embrace during their first iteration?

A.Eliminating all documentation throughout the lifecycle
B.Strict adherence to the project charter
C.Reducing the team size to improve velocity
D.Focusing on delivering high-value, working software early and often
AnswerD

Traditional project management defers value to phase gates; Disciplined Agile instead demands incremental delivery of working software each iteration. This shift satisfies the stem's first-iteration constraint by replacing document-driven progress with demonstrable, high-value output that generates early feedback.

Why this answer

The core of Disciplined Agile is the pragmatic shift towards value delivery over rigid adherence to process, emphasizing a 'choose your way of working' approach.

Full explanation →
207
MCQmedium

A team has a very high lead time. They notice that work sits in a 'Pending Approval' state for 80% of the total time. What should they do?

A.Report the delay to management.
B.Implement automated approvals for low-risk changes.
C.Conduct more frequent approval meetings.
D.Increase the number of approvers to speed up the process.
AnswerB

Automating approvals for low-risk changes directly attacks the queueing delay: the 'Pending Approval' wait, which consumes 80% of lead time, is removed for those items, so they flow straight to the next stage. This shortens total lead time without eliminating the human review that higher-risk changes still require.

Why this answer

The bottleneck is the approval wait state, which consumes 80% of lead time — a classic queue/wait problem, not a capacity problem. Automating approvals for low-risk changes removes the human queue entirely for a defined class of work, directly shrinking the largest contributor to lead time. This aligns with DevOps/DORA guidance: reduce batch size and manual gates, and reserve human approval for changes that genuinely carry risk.

Exam trap

DAF often tests the misconception that adding people or meetings to an approval bottleneck speeds it up, when the correct move is to remove or automate the gate for low-risk work.

How to eliminate wrong answers

Option A is wrong because reporting the delay to management is a status action, not a process change — it documents the bottleneck without removing it, so lead time stays unchanged. Option C is wrong because more frequent approval meetings still serialize work through a human gate; they may even increase context-switching and batching, and they don't address the 80% wait time. Option D is wrong because adding approvers typically increases coordination overhead and can slow decisions (Brooks's Law applied to approvals); the constraint is the approval step itself, not approver headcount.

Full explanation →
208
MCQmedium

What is the primary Lean goal of 'Visual Management'?

A.To track employee attendance.
B.To reduce the amount of paper used in the office.
C.To entertain the team during meetings.
D.To make the status of work and problems immediately apparent.
AnswerD

Visual Management makes the status of work and problems immediately apparent through visual signals such as andon lights, kanban cards and floor markings, so deviations are detected at a glance. This satisfies Lean's goal of rapid problem surfacing, enabling immediate corrective action rather than delayed reporting.

Why this answer

Visual Management in Lean uses physical or digital displays — kanban boards, andon cords, status lights, charts — to make the state of work and the presence of problems immediately obvious to anyone, without needing to ask. The goal is rapid detection and response: when a problem is visible, it can be swarmed and solved before it propagates.

Exam trap

The trap is choosing a tangential benefit (paper reduction, attendance) instead of the core purpose — making work status and problems immediately apparent so they can be acted on.

How to eliminate wrong answers

Option A is wrong because attendance tracking is an HR function, not a Lean visual management purpose; visual management is about work state, not personnel monitoring. Option B is wrong because reducing paper is an incidental environmental benefit at best — digital boards may use less paper, but the purpose is visibility of work and problems, not resource conservation. Option C is wrong because entertaining the team is not a Lean objective; visual displays exist to inform and trigger action, not to amuse.

Full explanation →
209
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.

Full explanation →
210
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.

Full explanation →
211
MCQhard

A team has high 'wait time' between code completion and code review. How should they address this using Lean principles?

A.Hire more senior developers to review code.
B.Eliminate code reviews.
C.Schedule all reviews for the end of the week.
D.Incorporate code review into the 'In Progress' workflow state.
AnswerD

Wait time between completion and review is queue delay, a Lean waste. Moving review into the 'In Progress' state makes it part of the active workflow, limiting work in progress and pulling reviews forward instead of letting finished items queue.

Why this answer

The team should pull the review into their workflow, making it a collaborative, immediate step rather than an external dependency.

Full explanation →
212
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.

Full explanation →
213
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.

Full explanation →
Page 2

Page 3 of 3

All pages

123

Practice DAF by domain

Target a specific domain to shore up weak areas.

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