Knowledge + Practice

CCNA Foundations OF Lean Questions

58 questions · Foundations OF Lean · All types, answers revealed

Practice these questions Domain overview All questions

1

MCQmedium

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

A.It creates a baseline for improvement.

B.It reduces the need for skilled workers.

C.It eliminates the need for team collaboration.

D.It makes the work boring and repetitive.

AnswerA

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

Why this answer

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

Practice this question →

2

MCQmedium

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

A.To measure individual developer productivity.

B.To relate WIP, Throughput, and Cycle Time mathematically.

C.To determine the number of staff members needed.

D.To calculate the total project budget.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

3

Multi-Selectmedium

Which THREE of the following represent ways to reduce handoffs?

Select 3 answers

A.Automating the delivery pipeline to minimize manual intervention.

B.Co-locating team members who need to collaborate frequently.

C.Forming cross-functional teams that own features end-to-end.

D.Outsourcing non-core tasks to a specialized vendor.

E.Adding an extra layer of management to monitor transfers.

AnswersA, B, C

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

Why this answer

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

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

Exam trap

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

Practice this question →

4

MCQhard

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

A.It has no impact on total cycle time.

B.It improves flow by ensuring high-quality decisions.

C.It increases technical debt.

D.It introduces a queue, increasing cycle time.

AnswerD

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

Why this answer

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

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

5

MCQeasy

What does 'Kaizen' represent in a Lean context?

A.Continuous, incremental improvement.

B.The elimination of all management roles.

C.A sudden, radical organizational overhaul.

D.A specific software testing methodology.

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

6

Multi-Selecthard

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

Select 3 answers

A.Focusing on end-to-end cycle time rather than local task speed.

B.Identifying and managing cross-team dependencies.

C.Aligning team goals with the organization's overarching value delivery.

D.Creating specialized teams that work in complete isolation.

E.Assigning one manager to oversee each individual team member.

AnswersA, B, C

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

Why this answer

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

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

Exam trap

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

Practice this question →

7

Multi-Selecthard

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

Select 2 answers

A.Improved team collaboration.

B.Increased lead time for all items in the system.

C.Faster delivery of high-priority items.

D.Increased pressure and potential burnout for team members.

E.A natural reduction in project costs.

AnswersB, D

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

Why this answer

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

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

Exam trap

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

Practice this question →

8

MCQmedium

Why does Lean advocate for 'Small Batch Sizes'?

A.To make the project appear larger to stakeholders.

B.To allow the team to work on more things simultaneously.

C.To reduce cycle time and increase the speed of feedback.

D.To minimize the use of automation tools.

AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

9

MCQhard

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

A.It reduces the need for salary increases.

B.It enables team members to help each other, preventing bottlenecks.

C.It increases the number of people available for specialized tasks.

D.It makes documentation unnecessary.

AnswerB

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

Why this answer

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

Practice this question →

10

MCQmedium

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

A.It forces work into the system, causing teams to rush.

B.It encourages too much collaboration.

C.It makes it too easy to track progress.

D.It allows for too much testing time.

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

11

MCQeasy

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

A.Respect People.

B.Optimize the Whole.

C.Deliver Fast.

D.Build Quality In.

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

12

MCQhard

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

A.It reduces the cycle time of the entire system.

B.It has no effect on the system.

C.It increases the pile-up at the bottleneck.

D.It improves the total throughput of the system.

AnswerC

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

Why this answer

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

Practice this question →

13

Multi-Selecthard

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

Select 3 answers

A.Waiting for external dependencies to clear.

B.Automated regression testing.

C.Rework due to defects.

D.Developing features that the user does not want.

E.Pair programming sessions.

AnswersA, C, D

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

Why this answer

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

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

Practice this question →

14

MCQmedium

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

A.To allow stakeholders to change their minds frequently.

B.To keep the team busy with administrative work.

C.To save money on project overhead.

D.To make decisions based on better, more current information.

AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

15

MCQmedium

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

A.Outsource the Testing phase to a third party.

B.Shift team focus to assist in the Testing phase to clear the backlog.

C.Increase the speed of the development phase to clear the backlog faster.

D.Remove the Testing phase from the workflow.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

16

MCQhard

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

A.Commit to both options and build parallel implementations

B.Choose the option with the lowest initial cost immediately to avoid delay

C.Defer the commitment until the last responsible moment

D.Ask the architecture review board to decide immediately

AnswerC

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

Why this answer

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

Exam trap

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

Practice this question →

17

MCQhard

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

A.Optimizing a sub-process without considering the impact on the overall value stream.

B.Identifying bottlenecks in the production pipeline.

C.Aligning team goals with organizational objectives.

D.Analyzing the end-to-end value stream.

AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

18

MCQhard

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

A.The cycle time is increasing while throughput remains stable.

B.The board looks too crowded.

C.The team is having too many meetings.

D.The team members are complaining about stress.

AnswerA

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

Why this answer

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

Practice this question →

19

MCQmedium

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

A.As a potential silo that should be integrated into cross-functional flow.

B.As the most important part of the organization.

C.As a group that should work at their own pace.

D.As a highly efficient unit that should be kept separate.

AnswerA

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

Why this answer

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

Practice this question →

20

MCQeasy

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

A.The project management software license fees.

B.Code that is written but not yet tested or deployed.

C.The time developers spend in training.

D.The office space rent.

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →

21

MCQmedium

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

A.It provides transparency that highlights issues without needing meetings.

B.It ensures the project looks good for visiting clients.

C.It is required by the PMO software.

D.It makes it easier for managers to track employees.

AnswerA

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

Why this answer

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

Practice this question →

22

MCQhard

In a Lean environment, how do you handle a 'non-value-add but necessary' activity?

A.Streamline and minimize it as much as possible.

B.Ignore it completely.

C.Automate it without optimization.

D.Assign it to a low-level employee.

AnswerA

If it is mandatory, you optimize its execution.

Why this answer

In Lean, activities are classified as value-add, non-value-add but necessary (sometimes called 'necessary non-value-add' or Type 1 muda), and pure waste. Necessary non-value-add work — like regulatory compliance checks or safety inspections — cannot be eliminated, so the correct Lean response is to streamline and minimize it (reduce time, effort, and variability) while preserving its necessity.

Exam trap

DAF often tests the misconception that all non-value-add work is waste to be eliminated — candidates who pick 'ignore it' or 'remove it' fail to distinguish necessary non-value-add from pure muda.

How to eliminate wrong answers

Option B is wrong because ignoring a necessary activity would violate compliance, safety, or quality requirements — Lean distinguishes necessary non-value-add from pure waste, and only the latter can be eliminated outright. Option C is wrong because automating without first optimizing simply accelerates a wasteful process (a classic Lean error: 'automating waste'), and it skips the kaizen step of understanding and simplifying the work. Option D is wrong because assigning work to a 'low-level' employee is not a Lean concept — Lean focuses on process improvement and respect for people, not hierarchical delegation as a way to handle non-value-add work.

Practice this question →

23

MCQeasy

What does a cumulative flow diagram (CFD) help a team visualize?

A.The specific team member assigned to each ticket.

B.The total budget remaining for the project.

C.The stability and distribution of work in progress.

D.Individual team member performance.

AnswerC

A cumulative flow diagram plots work items per workflow state over time, so widening bands reveal growing work in progress and bottlenecks. This directly exposes WIP stability and how work distributes across states, which is exactly what the question asks the CFD to visualise.

Why this answer

A cumulative flow diagram plots the count of work items in each workflow state over time, so the vertical thickness of each band shows work in progress (WIP) in that state. This lets a team see whether WIP is stable or ballooning, where bottlenecks form, and how evenly work is distributed across the flow. It is a core Lean/Agile flow metric, not a people or budget tool.

Exam trap

The trap is assuming the CFD is a people or budget chart; it is strictly a flow visualization of work items by state, and any answer referencing individuals or money is wrong.

How to eliminate wrong answers

Option A is wrong because a CFD aggregates items by state, not by assignee — it deliberately hides individual ownership to focus on flow. Option B is wrong because budget tracking is a financial concern handled by burn charts or cost reports, not by a CFD, which counts work items. Option D is wrong because a CFD is not a performance-management tool; using it to rank individuals misreads its purpose and would violate its aggregate, flow-oriented design.

Practice this question →

24

MCQhard

Your organization wants to transition to a 'Pull' system. What is the most important prerequisite?

A.Eliminating all meetings.

B.Moving to a cloud-based development environment.

C.Hiring more experienced team members.

D.Establishing and enforcing WIP limits.

AnswerD

WIP limits are the prerequisite for a pull system: they cap the amount of work in progress, so new work is only pulled when capacity frees up. Without enforced limits, downstream stages simply push work forward, and the pull signal cannot govern flow.

Why this answer

A Pull system in lean/agile means work is pulled into the system only when there is capacity to handle it, rather than being pushed in based on forecasts or schedules. The most important prerequisite for a Pull system is establishing and enforcing Work-In-Progress (WIP) limits, because without them there is no mechanism to signal when new work can be pulled. WIP limits create the 'pull' signal by constraining how much work can be in progress at once, forcing the team to finish before starting new items.

Exam trap

DAF often tests the misconception that Pull is about tools or team composition, when the essential prerequisite is WIP limits that create the pull signal and regulate flow.

How to eliminate wrong answers

Option A is wrong because eliminating all meetings is neither necessary nor sufficient for a Pull system — meetings can coexist with Pull if they are value-adding. Option B is wrong because moving to a cloud-based development environment is an infrastructure choice unrelated to the fundamental mechanics of Pull, which are about workflow control. Option C is wrong because hiring more experienced team members does not create a Pull system; experience may help, but the defining prerequisite is WIP limits that regulate flow.

Practice this question →

25

MCQmedium

If you observe a high rate of 'blocked' items on your Kanban board, what is the most appropriate action?

A.Remove the blocked items from the board.

B.Wait until the next daily stand-up to discuss the blocks.

C.Swarm on the blocked item to clear the impediment immediately.

D.Start new work to keep the developers busy.

AnswerC

Swarming clears the impediment immediately, directly addressing the constraint that blocked items halt flow and inflate cycle time. Rather than analysing causes or escalating, the team concentrates capacity on resolving the blocker, restoring throughput fastest. This satisfies the stem's demand for the most appropriate action when blocked items dominate the board.

Why this answer

A high rate of blocked items signals that work is getting stuck and flow is being disrupted, so the most appropriate action is to swarm on the blocked item to clear the impediment immediately. Swarming means the team temporarily focuses multiple people on the blocked work to unblock it, which restores flow and prevents the blockage from cascading into further delays. This is a core Kanban and Disciplined Agile practice for managing flow.

Exam trap

DAF often tests whether candidates default to 'keep everyone busy' thinking (starting new work) instead of recognizing that swarming to clear blockages is the flow-preserving action in Kanban.

How to eliminate wrong answers

Option A is wrong because removing blocked items from the board hides the problem rather than solving it — it destroys visibility and prevents the team from addressing the root cause. Option B is wrong because waiting until the next daily stand-up delays resolution; if the blockage is significant, the team should address it as soon as it is detected, not defer it to a scheduled meeting. Option D is wrong because starting new work to keep developers busy increases work in progress, which worsens flow, creates more queues, and violates the Kanban principle of limiting WIP — it is the classic '100% utilization' mistake.

Practice this question →

26

Multi-Selectmedium

Which TWO of the following are primary benefits of limiting Work-in-Progress (WIP)?

Select 2 answers

A.Elimination of all meetings.

B.Reduction in total cycle time.

C.Increased total throughput of the system.

D.Exposure of underlying process bottlenecks.

E.Improved individual employee performance.

AnswersB, D

Limiting WIP reduces queueing and context switching, so each item flows through the value stream faster. Little's Law confirms this: with throughput held steady, lowering the number of items in progress directly shortens the average time each item spends in the system, satisfying the scenario's demand for reduced total cycle time.

Why this answer

Option B is correct because limiting WIP reduces the amount of work queued at each stage, which shortens the time any single item spends waiting and being worked on, thereby reducing total cycle time (Little's Law: Cycle Time = WIP / Throughput). Option D is correct because capping WIP prevents work from piling up and hiding problems; when a stage hits its WIP limit, the blockage becomes visible and exposes the underlying process bottleneck that must be addressed. Option A is incorrect because limiting WIP does not eliminate all meetings; it may change their frequency or format but meetings are not inherently removed.

Option C is incorrect because limiting WIP primarily reduces cycle time and variability rather than directly increasing total throughput, which depends on the bottleneck's capacity. Option E is incorrect because WIP limits are a system-level flow control mechanism, not a technique for improving individual employee performance.

Exam trap

The trap is assuming WIP limits increase throughput — they primarily reduce cycle time and expose bottlenecks; throughput gains require addressing the constraint itself.

Practice this question →

27

MCQeasy

Which of the following is considered 'Waste' (Muda) in a software development process?

A.Performing automated unit tests.

B.Conducting a sprint demo.

C.Collaborating on design documents.

D.Developing features that the customer will never use.

AnswerD

Muda is any activity consuming effort without delivering value. Building features the customer never uses produces no value, so the effort, cost and delay it consumes are pure waste, unlike necessary but non-value-adding activities such as compliance testing.

Why this answer

In lean/Disciplined Agile thinking, waste (Muda) is any activity that consumes resources without creating value for the customer. Developing features the customer will never use is the canonical example of 'extra features' waste (overproduction), because the effort, code, and maintenance burden deliver zero customer value. Eliminating it via prioritization, MVP thinking, and validated learning is a core DA principle.

Exam trap

DAF often tests whether candidates can distinguish value-adding agile practices (tests, demos, collaboration) from genuine waste — the trap is labeling any overhead as waste.

How to eliminate wrong answers

Option A is wrong because automated unit tests create value by catching defects early and enabling safe refactoring — they reduce waste, not create it. Option B is wrong because a sprint demo provides feedback and transparency, which are value-adding activities in agile delivery. Option C is wrong because collaborating on design documents (when done just-in-time and collaboratively) improves shared understanding and reduces rework — it is not inherently waste.

Practice this question →

28

MCQmedium

When a team is 'swarming', what are they doing?

A.Taking a break together to recharge.

B.Collaborating simultaneously to finish a single item.

C.Working on as many tasks as possible at once.

D.Dividing work into the smallest possible tasks.

AnswerB

Swarming concentrates the whole team on one work item at a time, so collaboration happens simultaneously rather than through handoffs. This satisfies the stem's constraint of finishing a single item quickly, because limiting work in progress shortens cycle time and eliminates queueing between specialists.

Why this answer

Swarming in Agile means the entire team or a group of team members collaborates simultaneously on a single work item to finish it quickly, rather than each person working on separate tasks. This practice reduces work-in-progress (WIP), shortens cycle time for that item, and promotes knowledge sharing. It is a key technique in Kanban and Scrum for breaking through bottlenecks and accelerating delivery of high-priority items.

Exam trap

The trap here is confusing swarming with multitasking — candidates may pick 'working on as many tasks as possible' because it sounds productive, when swarming is actually about limiting WIP to a single item.

How to eliminate wrong answers

Option A is wrong because taking a break together is a team-building or rest activity, not swarming — swarming is an intense collaborative work practice, not a pause. Option C is wrong because working on as many tasks as possible at once is the opposite of swarming — swarming deliberately limits WIP to one item to maximize focus and throughput. Option D is wrong because dividing work into the smallest possible tasks describes task decomposition or slicing, not swarming — swarming is about many people on one item, not one person on many small items.

Practice this question →

29

MCQhard

When analyzing a Value Stream Map, what does an 'invisible' queue represent?

A.Future work that hasn't been started.

B.Work waiting in an inbox or system that is not explicitly tracked.

C.Work that has been completed but not yet verified.

D.The time spent in planning meetings.

AnswerB

An invisible queue is work that exists but is absent from the visual map, such as items sitting in an inbox or an untracked system queue. It satisfies the scenario by exposing hidden wait states that inflate lead time without appearing as explicit process steps.

Why this answer

In a Value Stream Map, an 'invisible' queue represents work that is waiting in a system or inbox but is not explicitly tracked or visualized on the map — for example, emails sitting in a shared mailbox or tickets in an untracked backlog. These queues still consume cycle time and hide waste, which is why making them visible is a key goal of value stream mapping.

Exam trap

DAF often tests whether candidates understand that 'invisible' in VSM refers to untracked waiting work, not to future work or completed work — the trap is confusing invisible queues with visible backlog or verification queues.

How to eliminate wrong answers

Option A is wrong because future work that has not been started is typically shown as a visible backlog or demand queue, not an invisible one — invisibility refers to lack of tracking, not lack of start. Option C is wrong because work completed but not yet verified is a visible 'wait for verification' queue, which is normally captured on the map as a distinct step. Option D is wrong because time spent in planning meetings is a process step or delay, not a queue of waiting work items, and it is typically visible in the map's timeline.

Practice this question →

30

MCQeasy

Which of these is the best definition of 'Value' in Lean?

A.The number of tasks completed in a sprint.

B.Anything the customer is willing to pay for.

C.The total effort hours spent by the team.

D.The number of lines of code written.

AnswerB

Lean defines value solely by the customer's judgement, so an activity counts as value only if the customer will pay for it. This satisfies the stem by anchoring value to customer willingness to pay, excluding internal effort that the customer does not recognise.

Why this answer

In Lean, value is defined from the customer's perspective: any activity or output for which the customer is willing to pay. This definition drives the identification of value-adding versus non-value-adding (waste) activities. Options A, C, and D are internal metrics that do not reflect customer willingness to pay.

Exam trap

The trap here is confusing internal productivity metrics (tasks, effort, code) with customer-defined value. Candidates may pick A or C thinking they represent value, but Lean strictly ties value to the customer's willingness to pay.

How to eliminate wrong answers

Option A is wrong because the number of tasks completed is an output metric, not a measure of customer-defined value. Option C is wrong because effort hours are a cost measure, not value. Option D is wrong because lines of code are a technical output, not something the customer values directly.

Practice this question →

31

MCQeasy

Which of these is a symptom of 'Overprocessing'?

A.Writing code in a professional IDE.

B.Conducting daily check-ins.

C.Adding extra features or documentation that the customer did not request.

D.Maintaining a clean codebase.

AnswerC

Adding unrequested features or documentation wastes effort on work the customer never valued, which is the defining symptom of Overprocessing in Lean. The stem asks for a symptom, and this directly satisfies it: effort expended beyond what the customer requires, generating no additional value and inflating cycle time.

Why this answer

Overprocessing waste occurs when teams do more work than the customer requires or values — such as adding unrequested features, gold-plating, or producing documentation nobody reads. Option C directly describes this: extra features or documentation the customer did not request.

Exam trap

The trap is that candidates pick options that sound like good engineering hygiene (clean code, IDEs, daily check-ins) as waste, when overprocessing specifically means doing more than the customer values.

How to eliminate wrong answers

Option A is wrong because using a professional IDE is a normal, value-adding development practice, not overprocessing. Option B is wrong because daily check-ins are a coordination practice that supports flow and is not inherently waste. Option D is wrong because maintaining a clean codebase reduces future waste (technical debt) and is a quality practice, not overprocessing.

Practice this question →

32

Multi-Selecthard

A product team is mapping its value stream and discovers that 60% of its cycle time is spent waiting for approvals from a centralized architecture review board. Which two actions best align with Lean thinking to improve flow? (Choose two.)

Select 2 answers

A.Move architecture decisions to the team and use lightweight guardrails

B.Schedule a weekly meeting to prioritize all pending reviews

C.Add more reviewers to the architecture review board

D.Require teams to submit more detailed documentation before review

E.Limit the number of items in the review queue and pull work only when capacity exists

AnswersA, E

Decentralizing decisions removes the external queue and lets the team closest to the work decide, which directly addresses the 60% waiting time. Lightweight guardrails preserve consistency without recreating a bottleneck, so this action aligns with Lean flow and respect for people.

Why this answer

The dominant waste is waiting for a centralized approval, so the strongest Lean actions are to eliminate the external queue by moving decisions to the team with guardrails, and to limit WIP in the review queue so work is pulled only when capacity exists. Both reduce lead time and make the bottleneck visible.

Exam trap

The trap here is choosing actions that make the existing approval process faster rather than removing the queue that causes the waiting.

Practice this question →

33

MCQmedium

A team is frustrated by 'rework'. Which Lean practice helps address this at the source?

A.Assigning a dedicated person to track defects.

B.Reducing the scope of the project.

C.Building quality in through practices like TDD and automated testing.

D.Increasing the testing phase duration.

AnswerC

TDD and automated testing build verification into the development cycle itself, catching defects at the point of creation rather than after handoff. This addresses rework at its source by preventing defective work from flowing downstream, where correction costs far more.

Why this answer

Lean addresses rework by preventing defects at the point of creation rather than detecting them later. Building quality in through Test-Driven Development (TDD) and automated testing shifts verification left, so defects never enter the codebase in the first place. This eliminates the root cause of rework — defective work products flowing downstream — instead of merely measuring or containing it.

Exam trap

The trap here is confusing defect detection activities (tracking, longer testing phases) with defect prevention practices — DAF questions reward prevention-at-the-source thinking over downstream inspection.

How to eliminate wrong answers

Option A is wrong because assigning a person to track defects is a detection/measurement activity that documents rework after it occurs rather than preventing it at the source. Option B is wrong because reducing scope is a scope-management tactic that limits how much work exists, not a quality practice that stops defects from being created. Option D is wrong because extending the testing phase is a late-stage detection strategy that finds defects after they are built, which is the opposite of building quality in at the source.

Practice this question →

34

MCQmedium

Your team is experiencing high WIP levels during the development phase. Which Lean technique should you apply first to identify the primary cause of this congestion?

A.Require developers to work overtime to clear the backlog.

B.Increase the team size to handle the overflow.

C.Conduct a Value Stream Mapping session to visualize handoffs and queues.

D.Implement a mandatory daily stand-up meeting extension.

AnswerC

Value Stream Mapping exposes queueing and handoff delays across the flow, directly surfacing where WIP accumulates during development. Unlike local fixes, it maps the whole value stream, revealing the primary congestion cause before you limit WIP or rebalance capacity.

Why this answer

Value Stream Mapping (VSM) is the Lean technique for visualizing the end-to-end flow of work, including handoffs, queues, and wait times, which reveals where WIP accumulates and why. Before applying countermeasures like WIP limits or swarming, the team must see the current state to identify the primary constraint. VSM provides that diagnostic view.

Exam trap

DAF often tests the urge to jump to solutions (add people, work overtime) — the trap is forgetting that Lean requires diagnosing the system with VSM before applying countermeasures.

How to eliminate wrong answers

Option A is wrong because overtime treats the symptom (backlog) while increasing burnout and defect rates, and it does not reveal the cause of congestion. Option B is wrong because adding people to a congested flow can worsen it (Brooks's Law) and does not diagnose the bottleneck. Option D is wrong because extending stand-ups adds meeting time without providing the systemic visibility that VSM delivers.

Practice this question →

35

MCQmedium

You notice that the team's 'Cycle Time' is increasing despite no change in the amount of work. What should you investigate?

A.The team's office lighting.

B.The presence of hidden queues between workflow states.

C.The number of coffee breaks taken.

D.The team's motivation level.

AnswerB

Rising cycle time with constant work volume points to wait states rather than capacity shortfalls. Hidden queues between workflow states accumulate work-in-progress, inflating elapsed time without adding effort, so investigating them directly addresses the constraint the stem describes.

Why this answer

Cycle time increases when work spends more time waiting between workflow states, and hidden queues — unacknowledged wait states such as 'waiting for review', 'waiting for test environment', or 'waiting for approval' — are the most common cause. Investigating these queues reveals where work is piling up and why flow has slowed even though the volume of work has not changed.

Exam trap

DAF often tests the misconception that cycle time increases are caused by people or effort factors (motivation, breaks, environment) rather than by structural flow problems like hidden queues, tricking candidates into selecting a human-factor answer.

How to eliminate wrong answers

Option A is wrong because office lighting is a physical environment factor that has no meaningful causal relationship with cycle time in a knowledge-work Kanban system. Option C is wrong because coffee breaks are a trivial and unlikely explanation for a systemic increase in cycle time, and they do not represent a workflow bottleneck. Option D is wrong because team motivation, while relevant to productivity, does not explain a structural increase in cycle time when the amount of work is unchanged — the question points to a flow problem, not a morale problem.

Practice this question →

36

MCQmedium

You are identifying 'non-value-add' work in your process. What is the most important first step?

A.Hire an outside consultant to audit the process.

B.Immediately delete all documentation.

C.Interview every team member about their tasks.

D.Create a current-state Value Stream Map.

AnswerD

Identifying non-value-add work requires first seeing how value currently flows. A current-state Value Stream Map exposes each step, delay and handoff, making waste visible before any improvement decision, so it is the essential starting point.

Why this answer

Before you can eliminate waste, you must visualize the current state to know what is actually happening.

Practice this question →

37

MCQhard

Your team is struggling with 'gold plating' (adding unnecessary features). How does this affect the value stream?

A.It increases lead time without providing additional customer value.

B.It reduces lead time by keeping developers productive.

C.It has no impact on the value stream.

D.It improves the overall quality of the product.

AnswerA

Gold plating adds unrequested features that consume capacity and lengthen the queue, increasing lead time while delivering no additional customer value. It satisfies the stem's value-stream constraint by showing waste that inflates cycle time without improving flow efficiency or customer outcomes.

Why this answer

Gold plating — adding features or polish beyond what the customer requested — consumes capacity without delivering additional customer value. In value-stream terms, this extra work increases lead time (and WIP) while producing no corresponding value, making it a form of waste (muda) that should be eliminated.

Exam trap

DAF often tests the misconception that gold plating improves quality or keeps developers productive — candidates pick 'improves overall quality' or 'reduces lead time' because extra work feels valuable, but Lean defines value strictly from the customer's perspective, and unrequested features are waste.

How to eliminate wrong answers

Option B is wrong because gold plating does not reduce lead time; it lengthens it by adding unrequested work, even if developers appear busy. Option C is wrong because gold plating directly impacts the value stream by adding non-value-adding steps and increasing cycle time. Option D is wrong because gold plating does not improve quality in the customer's eyes — it may introduce defects, complexity, and maintenance burden, and it often reflects a misunderstanding of requirements rather than genuine quality improvement.

Practice this question →

38

MCQmedium

A team discovers that their cycle time is highly variable. What is the most likely culprit from a Lean perspective?

A.Having a very small backlog.

B.Lack of process standardization.

C.The use of an electronic board.

D.Too many team members.

AnswerB

Variable cycle time stems from inconsistent task sequencing, uneven work content and ad-hoc handoffs, which process standardisation eliminates by fixing the best-known method and takt-aligned work elements. Standard work creates a predictable baseline, so deviations surface as abnormalities rather than random variation, directly addressing the variability the team observes.

Why this answer

In Lean thinking, cycle time variability is primarily driven by inconsistent work methods, not by workload size or tooling. Lack of process standardization means each work item may follow a different path, with different handoffs, definitions of done, and decision points, which produces unpredictable durations. Standardized work is a foundational Lean countermeasure because it creates a stable baseline from which variation can be measured and reduced.

Exam trap

DAF often tests the misconception that variability comes from external factors like team size or tooling, when Lean attributes it to unstable, non-standardized processes.

How to eliminate wrong answers

Option A is wrong because a small backlog actually reduces variability by limiting the number of competing work items and shortening queue times — it is a flow-friendly condition, not a cause of variance. Option C is wrong because an electronic board is merely a visualization tool; whether physical or digital, a board does not by itself introduce cycle-time variation, and poor board hygiene is a symptom rather than the root cause. Option D is wrong because team size is not inherently a source of variability — larger teams can be stable if roles, WIP limits, and working agreements are standardized; the issue is coordination and process discipline, not headcount.

Practice this question →

39

Multi-Selecteasy

Which TWO of the following are common types of 'Waste' (Muda) that teams should look for?

Select 2 answers

A.Waiting for information or approvals.

B.Collaborative code reviews.

C.Excessive motion or context switching.

D.The use of automated build tools.

E.Regular team retrospectives.

AnswersA, C

Waiting is one of the classic Lean wastes: idle time while people await information, approvals or dependencies. It delays flow and adds no value, making it a recognised Muda category that teams should actively identify, satisfying the question's requirement for a common waste type.

Why this answer

Option A (Waiting for information or approvals) is correct because waiting is one of the classic seven wastes of Lean/Muda — any idle time where work is blocked by a dependency, handoff, or approval gate adds no value and delays flow. Option C (Excessive motion or context switching) is correct because unnecessary movement and task-switching are recognized forms of waste; in knowledge work, context switching destroys focus and throughput, analogous to the 'motion' and 'transportation' wastes in manufacturing. Option B (Collaborative code reviews) is not waste — it is a value-adding quality practice that catches defects early and spreads knowledge.

Option D (The use of automated build tools) is not waste — automation reduces manual effort and errors, directly eliminating waste rather than creating it. Option E (Regular team retrospectives) is not waste — retrospectives are a deliberate improvement activity that helps teams identify and remove waste.

Practice this question →

40

MCQmedium

What is the relationship between 'Flow' and 'Value' in Lean?

A.Flow is the mechanism that enables value delivery.

B.Value is achieved by stopping all flow.

C.Flow is only for manufacturing, not software.

D.Flow and value are completely unrelated.

AnswerA

Flow is the smooth, uninterrupted movement of work through the value stream; without it, work queues, waits and partially completed items delay delivery. Value is only realised when increments reach the customer, so flow is the enabling mechanism through which that value is actually delivered.

Why this answer

In Lean, value is defined from the customer's perspective as what they are willing to pay for, and flow is the uninterrupted movement of work or materials through the value stream that delivers that value. Flow is the mechanism — the smooth, continuous progression of work — that enables value to reach the customer without delays, rework, or waste. Thus flow enables value delivery.

Exam trap

The trap is treating flow and value as separate or even opposing concepts — candidates must recognize that flow is the enabler of value delivery, not an independent or conflicting principle.

How to eliminate wrong answers

Option B is wrong because stopping flow creates waste (waiting, inventory) and prevents value delivery — Lean seeks to maximize flow, not halt it. Option C is wrong because Lean flow principles apply to software and knowledge work (e.g., Kanban, DevOps continuous delivery), not just manufacturing. Option D is wrong because flow and value are tightly coupled in Lean — flow is how value is delivered through the value stream.

Practice this question →

41

MCQhard

How should a team handle an 'emergency' request in a Kanban system that is already at its WIP limit?

A.Refuse the request at all costs.

B.Ask the team to work late to finish it.

C.Discuss the trade-off and decide if the emergency justifies exceeding the WIP limit.

D.Automatically prioritize the emergency and break all WIP limits.

AnswerC

Kanban WIP limits are explicit policies, not absolutes; an emergency requires a conscious trade-off decision. The team must decide whether the emergency's cost of delay justifies breaching the limit, and if so, what to pull or swarm to restore flow.

Why this answer

In Kanban, WIP limits are policies, not absolute laws, and the correct response to an emergency is to make the trade-off explicit: discuss what will be delayed or stopped if the emergency is pulled in, and decide consciously whether the emergency justifies exceeding the limit. This preserves the team's ability to manage flow while acknowledging that some situations genuinely warrant an exception.

Exam trap

DAF often tests the misconception that WIP limits are absolute rules that must never be broken, or conversely that emergencies automatically override all limits, when the correct Kanban answer is to make the trade-off explicit and decide consciously.

How to eliminate wrong answers

Option A is wrong because refusing the request at all costs is dogmatic — Kanban values explicit policies and conscious trade-offs, not rigid rule-following that ignores business reality. Option B is wrong because asking the team to work late addresses the symptom (capacity) rather than the system (WIP limit), and it leads to burnout without resolving the underlying flow problem. Option D is wrong because automatically prioritizing the emergency and breaking all WIP limits removes the team's ability to make a deliberate trade-off, which undermines the purpose of WIP limits and can cause cascading delays across all work in progress.

Practice this question →

42

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.

Practice this question →

43

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.

Practice this question →

44

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.

Practice this question →

45

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.

Practice this question →

46

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.

Practice this question →

47

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.

Practice this question →

48

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.

Practice this question →

49

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.

Practice this question →

50

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.

Practice this question →

51

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.

Practice this question →

52

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.

Practice this question →

53

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.

Practice this question →

54

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.

Practice this question →

55

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.

Practice this question →

56

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.

Practice this question →

57

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.

Practice this question →

58

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.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Foundations OF Lean questions.

Start 20-question session