First 50 of 190 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Lean customer value, value streams and pull
What are the five core principles of Lean thinking in the correct sequential order as defined by Womack and Jones?
- Value, Value Stream, Flow, Pull, Perfection Correct answer.
- Flow, Value, Pull, Value Stream, Perfection
- Value Stream, Value, Perfection, Flow, Pull
- Pull, Flow, Value Stream, Value, Perfection
Explanation
The 5 core Lean principles in sequence are: 1. Specify Value from the customer's perspective, 2. Map the Value Stream, 3. Create Flow, 4. Establish Pull, and 5. Pursue Perfection through continuous improvement.
Question 2Lean customer value, value streams and pull
Why is 'Perfection' considered the 5th principle of Lean, even though absolute perfection is rarely achievable in practice?
- Because it justifies firing employees who make any mistake
- Because it establishes a mindset of continuous, relentless pursuit of zero waste and 100% customer value Correct answer.
- Because regulatory standards require Lean certified firms to prove zero defects
- Because it allows companies to charge 500% higher prices
Explanation
Pursuing Perfection creates an enduring organizational culture of Kaizen-constantly striving to eliminate waste and deliver higher value, knowing improvement is an endless journey.
Question 3Lean customer value, value streams and pull
Which overall summary best reflects the ultimate goal of Lean IT Foundation certification mastery?
- To maximize IT department server hardware procurement budgets
- To deliver maximum customer value with minimal waste through continuous flow, pull systems, visual management, and team-driven continuous improvement (Kaizen) Correct answer.
- To replace all human employees with artificial intelligence algorithms
- To pass audit inspections without modifying existing legacy IT processes
Explanation
The ultimate goal of Lean IT is maximizing customer value while minimizing waste, empowering people, establishing smooth flow and pull, and embedding a culture of continuous improvement.
Question 4Lean customer value, value streams and pull
In Lean IT, how is 'Customer Value' primarily defined?
- By internal IT managers based on technical elegance and code complexity
- By the customer, as any capability or deliverable for which they are willing to pay or invest resources Correct answer.
- By third-party software vendors through published feature release roadmaps
- By regulatory bodies setting compliance frameworks for enterprise IT
Explanation
Lean examines value from the customer perspective and translates actual needs into measurable service outcomes. Willingness to pay or invest resources is a useful lens, but required safety, security and legal controls can remain necessary even when they do not directly transform the customer deliverable. Do not remove them indiscriminately.
Question 5Lean customer value, value streams and pull
What does a Voice of Customer (VOC) translation matrix or CTQ (Critical to Quality) tree do?
- Translates generic customer needs into specific, measurable IT quality requirements Correct answer.
- Converts legacy database schemas into modern cloud JSON formats
- Maps network bandwidth usage across corporate branches
- Calculates monthly employee payroll deductions
Explanation
A Critical to Quality (CTQ) tree translates broad, qualitative Voice of Customer (VOC) statements into specific, measurable operational requirements (CTQs).
Question 6Lean customer value, value streams and pull
Which type of activity adds no direct value to the customer, but is necessary due to regulatory, legal, or technical requirements?
- Value-Add (VA)
- Necessary Non-Value Add (NNVA) Correct answer.
- Non-Value Add (NVA)
- Kaizen Blitz
Explanation
Necessary Non-Value Add (NNVA) activities create no direct value for the customer but are mandatory under current laws, regulations, or constraints (e.g., audit logging, compliance reporting).
Question 7Lean customer value, value streams and pull
In a Voice of Customer (VOC) study for an online banking app, users state: 'I want the application to load instantly on my phone.' What is the most appropriate Critical to Quality (CTQ) metric for IT to monitor?
- App landing page full interactive render time < 1.5 seconds Correct answer.
- Number of lines of Swift code written by mobile developers
- Monthly cloud hosting invoice amount in USD
- Average age of the database administration team
Explanation
CTQs translate subjective user needs into precise, objective operational metrics. 'Load instantly' translates directly to 'page render time < 1.5 seconds'.
Question 8Lean customer value, value streams and pull
What is the relationship between 'Customer Value' and 'Voice of Customer' (VOC)?
- VOC is the process/method used to capture and understand what the customer defines as Customer Value Correct answer.
- Customer Value and VOC are mutually exclusive concepts in Lean IT
- VOC is measured in dollars, whereas Customer Value is measured in hours
- Customer Value is captured from internal IT staff, while VOC comes from competitors
Explanation
Voice of Customer (VOC) represents the feedback, requirements, and expectations expressed by customers. Lean practitioners analyze VOC to determine true Customer Value.
Question 9Lean customer value, value streams and pull
Which of the following is considered 'Non-Value Add' (NVA / Pure Waste) in an IT deployment process?
- Writing core business logic code specified by the user
- Waiting 4 days for a supervisor's signature on a change approval form that is automatically approved without inspection Correct answer.
- Running automated unit tests required for compliance
- Configuring security access roles requested by HR
Explanation
Rubber-stamp approvals that add no inspection value or risk reduction represent pure Non-Value Add (NVA) waste.
Question 10Lean customer value, value streams and pull
When constructing a Critical to Quality (CTQ) tree for an IT disaster recovery service, what represents the correct hierarchical breakdown from top to bottom?
- Customer Need -> Quality Drivers -> Specific Measurable Requirements (CTQs) Correct answer.
- Specific Measurable Requirements (CTQs) -> Customer Need -> Quality Drivers
- Quality Drivers -> Specific Measurable Requirements (CTQs) -> Customer Need
- Server Hardware -> Operating System -> Customer Need
Explanation
A CTQ tree branches top-down: 1. Customer Need (broad expectation) -> 2. Quality Drivers (key operational areas) -> 3. Specific Measurable Requirements (quantitative CTQ metrics).
Question 11Structured improvement, root causes and learning
Which term describes the Japanese concept of the physical location where the actual work is performed?
- Kaizen
- Gemba Correct answer.
- Kanban
- Muda
Explanation
Gemba (or Genba) translates to 'the real place'-in IT, it refers to the location where value creation happens (e.g., service desk floor, developer workspace, datacenter).
Question 12Structured improvement, root causes and learning
What is the primary role of a Lean IT Leader during a 'Gemba Walk'?
- To inspect workstations and reprimand employees for minor dress code violations
- To go to where work is done, observe actual processes, listen, show respect, and support problem solving Correct answer.
- To present financial revenue reports to executive stakeholders via slide decks
- To audit software license keys on developer laptops
Explanation
A Lean leader goes to the Gemba (the workplace) to observe real work in real time, understand operational realities, ask questions, show respect to workers, and help identify roadblocks.
Question 13Structured improvement, root causes and learning
Which aspect of Lean culture encourages team members to view failures and errors as opportunities to learn and improve?
- Blameless culture / Psychological safety Correct answer.
- Strict disciplinary protocol
- Performance-contingent financial penalties
- Top-down micro-management
Explanation
Lean IT requires a blameless culture and psychological safety where mistakes are viewed as system defects to be analyzed and solved, not opportunities to punish individuals.
Question 14Structured improvement, root causes and learning
Which behavior is characteristic of a Lean IT Leader acting as a coach?
- Giving direct solutions and orders for every incident ticket
- Asking open-ended Socratic questions to help team members analyze root causes and develop their own problem-solving skills Correct answer.
- Completing all technical tasks themselves to ensure perfection
- Ignoring operational problems until annual budget reviews
Explanation
Lean leaders coach by asking guiding questions (e.g., 'What is the target condition?', 'What did you observe at Gemba?') to empower employees to solve problems independently.
Question 15Structured improvement, root causes and learning
How does Lean IT define 'Respect for People'?
- Giving employees expensive gifts at annual holidays
- Empowering workers to solve problems, engaging their minds, providing a safe workspace, and removing operational friction Correct answer.
- Never holding employees accountable for process deadlines
- Allowing teams to skip all quality testing steps
Explanation
Respect for People means valuing employees' intelligence, involving them in process improvement, giving them tools to succeed, providing safety, and removing waste that frustrates their work.
Question 16Structured improvement, root causes and learning
In Lean IT leadership, what is 'Policy Deployment' (Hoshin Kanri)?
- A method to align strategic organizational goals with daily operational execution and Kaizen activities Correct answer.
- A human resource policy governing employee vacation requests
- A network firewall policy blocking external internet traffic
- An insurance policy covering physical hardware theft
Explanation
Hoshin Kanri (Policy Deployment) is a strategic planning methodology that cascades high-level strategic goals into actionable, measurable operational targets across all organizational levels.
Question 17Structured improvement, root causes and learning
Which of the following is a key cultural indicator of a successful Lean IT transformation?
- Employees actively identify problems, suggest countermeasures, and collaborate on daily Kaizen improvements Correct answer.
- Management issues top-down commands with zero input from engineers
- Teams work in siloes to protect their departmental budgets
- All visual boards are hidden behind locked office doors
Explanation
A mature Lean culture exhibits bottom-up employee engagement, transparent problem reporting, continuous Kaizen, and shared accountability.
Question 18Structured improvement, root causes and learning
During an A3 problem-solving investigation into recurring production outages, a team discovers that system changes are regularly deployed without regression testing because developers face immense schedule pressure from business managers. How should a Lean IT Leader address this issue?
- Punish the developers for skipping testing guidelines
- Address the root cause by establishing executive alignment on quality standards, implementing automated guardrails (Poka-Yoke), and balancing workload (Heijunka) Correct answer.
- Order business managers to stop requesting new features permanently
- Hire external contractors to perform manual testing after production release
Explanation
A Lean leader looks beyond surface human error to resolve systemic organizational drivers: aligning business priorities, removing schedule overburden (Muri/Heijunka), and installing automated pipeline guardrails.
Question 19Structured improvement, root causes and learning
An IT executive notices that frontline engineers regularly identify operational wastes but refrain from initiating Kaizen improvements because previous suggestions were rejected without explanation. What critical Lean leadership element is missing?
- Empowerment, active listening, and a transparent feedback loop for Kaizen suggestions Correct answer.
- Financial penalties for failing to submit ideas
- A 100-page policy manual on suggestion submission
- Third-party external auditing of suggestion forms
Explanation
Lean culture requires leadership to empower workers, listen actively, review suggestions transparently, provide immediate feedback, and support team-led countermeasures.
Question 20Structured improvement, root causes and learning
Which practice exemplifies the Lean concept of 'Gemba' for a cloud infrastructure team whose environment is entirely virtualized in AWS/Azure?
- Visiting the physical building site of an AWS data center in Virginia
- Observing active deployment dashboards, cloud console logs, and pair-programming sessions directly alongside engineers during live operations Correct answer.
- Reading historical cloud billing invoices from 3 years ago
- Attending an offsite vendor marketing conference in Las Vegas
Explanation
In digital/cloud IT, Gemba is where digital work is actively performed and visualized-observing live code reviews, deployment pipelines, console monitoring, and pairing sessions.
Question 21Lean customer value, value streams and pull
In Lean IT, what does the Japanese term 'Muda' refer to?
- Overburden placed on people or systems
- Unevenness or variability in a process
- Waste or any activity that does not add value Correct answer.
- Continuous small incremental improvements
Explanation
Muda describes non-value-adding work in this teaching model. Distinguish avoidable waste from currently necessary non-value-adding safety, technical or compliance work. Improvement requires actual process evidence and an authorized safe alternative, rather than treating every control or documentation step as dispensable.
Question 22Lean customer value, value streams and pull
Which of the following is an example of the waste of 'Defects' in an IT software development context?
- Writing clean, self-documenting code that passes all automated unit tests
- Releasing software containing software bugs that require emergency hotfixes and rework Correct answer.
- Delivering a feature early to a customer who immediately uses it
- Automating build pipelines using continuous integration scripts
Explanation
Defects occur when a deliverable fails to meet quality standards, leading to rework, hotfixes, or incident tickets.
Question 23Lean customer value, value streams and pull
Which IT waste is demonstrated when a developer builds complex, unrequested software features that end users never utilize?
- Waiting
- Overproduction Correct answer.
- Motion
- Transportation
Explanation
Overproduction in IT means creating more output, features, code, or documentation than requested or needed by the customer.
Question 24Lean customer value, value streams and pull
Which of the following represents the waste of 'Waiting' in an IT service desk?
- A technician resolving an incident ticket in 5 minutes
- A user request sitting idle for 3 days awaiting manager approval before provisioning can begin Correct answer.
- An automated script resetting a user password instantaneously
- A team holding a 10-minute daily stand-up meeting
Explanation
Waiting waste occurs whenever work, information, or people sit idle waiting for an input, decision, approval, or upstream task to finish.
Question 25Lean customer value, value streams and pull
Which of the 3 Ms represents 'Overburden' on people, equipment, or systems?
- Muda
- Muri Correct answer.
- Mura
- Mudita
Explanation
Muri means overburden or unreasonable stress placed on employees or systems (e.g., pushing servers to 100% CPU capacity constantly or forcing staff to work double shifts).
Question 26Lean customer value, value streams and pull
How does Lean IT view 'Inventory' in a digital service environment?
- Hardware spare parts kept in physical storage rooms only
- Unreleased code branches, unassigned ticket backlogs, and pending change requests awaiting review Correct answer.
- Virtual machine disk snapshots stored on backup SAN storage
- Annual software license subscriptions purchased from enterprise vendors
Explanation
In digital environments, Inventory waste includes accumulated work items that are incomplete or unreleased: open ticket queues, unmerged code, untested builds, and pending approvals.
Question 27Lean customer value, value streams and pull
Which of the following is a classic example of 'Transportation' waste in an IT infrastructure environment?
- Physically moving backup tape drives between data centers across town, or manually transferring large data files between incompatible cloud buckets Correct answer.
- A server crashing due to insufficient RAM
- A developer waiting 2 hours for a database query to complete
- Creating an extra backup copy required by ISO 27001 audit guidelines
Explanation
Transportation waste involves unnecessary movement of materials, code, data, or files from one physical or logical location to another without adding value.
Question 28Lean customer value, value streams and pull
Which of the following describes the IT waste of 'Non-utilized Talent / Skills'?
- Assigning senior database architects to perform manual daily data entry tasks instead of leveraging their engineering capabilities Correct answer.
- Hiring external consultants to teach Lean techniques to staff
- Providing software development training to junior engineers
- Automating password resets using self-service portals
Explanation
Non-utilized Talent (the 8th waste added to Lean) occurs when employee skills, creativity, experience, or problem-solving abilities are underutilized or wasted on mundane repetitive tasks.
Question 29Lean customer value, value streams and pull
Which of the following is an example of the waste of 'Motion' in an IT service environment?
- An analyst clicking through 12 different menu screens and switching between 4 software portals to answer a single customer incident Correct answer.
- A server taking 5 seconds to respond to a ping request
- Writing extra code for features that were never requested
- Storing backup servers in an offsite warehouse
Explanation
Motion waste involves unnecessary movement of people, excessive clicks, navigating cumbersome interfaces, or toggling between disconnected software applications.
Question 30Lean customer value, value streams and pull
Which scenario demonstrates the simultaneous presence of all three Lean wastes: Muda (Waste), Muri (Overburden), and Mura (Unevenness)?
- A team maintains a steady, automated CI/CD pipeline with 10% WIP utilization every day
- An IT team experiences massive end-of-month deployment rushes (Mura), forcing engineers to work 16-hour days (Muri), leading to high defect rates and emergency hotfix rework (Muda) Correct answer.
- A team uses digital Kanban boards with strict WIP limits
- A manager conducts weekly Gemba walks to support continuous improvement
Explanation
Demand volatility at month-end is Mura (Unevenness). Overworking staff 16 hours/day is Muri (Overburden). The resulting defects and hotfix rework are Muda (Waste).
Question 31Lean customer value, value streams and pull
A DevOps team attempts to eliminate the waste of 'Overproduction' in their continuous delivery pipeline. Which practice directly combats Overproduction?
- Building features only when backed by validated customer user stories and released behind feature toggles based on actual demand Correct answer.
- Pre-building 50 unrequested experimental features in advance to keep developers busy
- Generating 1,000-page automated PDF logs for every minor code check-in
- Buying extra SAN storage arrays to hold unused code branches
Explanation
Developing software features strictly based on validated customer demand (Pull-based feature development) prevents building unrequested capabilities that waste engineering effort.
Question 32Lean customer value, value streams and pull
What is the main objective of Value Stream Mapping (VSM) in Lean IT?
- To generate detailed individual performance ratings for IT employees
- To visualize the end-to-end flow of material and information required to deliver a service and identify waste Correct answer.
- To replace standard ITIL service desk software with automated scripts
- To calculate annual server hardware depreciation costs
Explanation
Value Stream Mapping (VSM) creates a visual depiction of all steps-both value-adding and non-value-adding-required to bring an IT service or product from initial request to delivery.
Question 33Lean customer value, value streams and pull
What is 'Takt Time' in a Lean IT process?
- The total clock time an issue sits waiting in an unassigned queue
- The pace of production required to match the rate of customer demand Correct answer.
- The time required to reboot a physical database server
- The average duration of a daily team stand-up meeting
Explanation
Takt Time is the rate at which a product or service must be completed to satisfy customer demand. Formula: Available Operating Time / Customer Demand.
Question 34Lean customer value, value streams and pull
What is 'Lead Time' in an IT service management context?
- The time spent solely on active coding by a software developer
- The total elapsed time from when a customer submits a request until the final delivery/resolution is received Correct answer.
- The duration of the project manager's lunch break
- The time required to reboot a core router
Explanation
Lead Time measures the total elapsed time from the moment a request is initiated by the customer to when the completed deliverable is placed in the customer's hands.
Question 35Lean customer value, value streams and pull
In this supplied value-stream vocabulary, which listed metric counts active processing time only, explicitly excluding waiting and queue time?
- Lead Time
- Process Time (or Cycle Time) Correct answer.
- Takt Time
- Downtime
Explanation
The keyed option contains Process Time, which is the active-work measure defined in this question. Cycle time is defined differently across methods and may include elapsed time between start and finish. Document the measurement boundary and units before comparing values from different teams or using Little's Law.
Question 36Lean customer value, value streams and pull
An IT Service Desk receives 120 ticket requests in an 8-hour workday (480 minutes). What is the Takt Time for processing tickets?
- 4 minutes per ticket Correct answer.
- 15 minutes per ticket
- 0.25 minutes per ticket
- 480 minutes per ticket
Explanation
Takt Time = Available Operating Time / Customer Demand = 480 minutes / 120 tickets = 4 minutes per ticket. This means a ticket must be processed every 4 minutes to meet customer demand.
Question 37Lean customer value, value streams and pull
A software deployment value stream has a total Lead Time of 10 days, but the actual total Process Time (active work) is only 8 hours (1 day). What is the Activity Ratio of this value stream?
- 80%
- 10% Correct answer.
- 12.5%
- 90%
Explanation
Activity Ratio = (Total Process Time / Total Lead Time) × 100%. Here, 1 day of Process Time / 10 days of Lead Time = 1/10 = 10%.
Question 38Lean customer value, value streams and pull
In a 3-step IT onboarding value stream, Step 1 has a first-pass yield of 90%, Step 2 has 80%, and Step 3 has 90%. What is the Rolled First Pass Yield (RFPY) of the entire value stream?
- 86.7%
- 64.8% Correct answer.
- 90.0%
- 260.0%
Explanation
Rolled First Pass Yield (RFPY) is calculated by multiplying the first-pass yield percentages of each consecutive step: 0.90 × 0.80 × 0.90 = 0.648 or 64.8%.
Question 39Lean customer value, value streams and pull
What is the key difference between a Current State Value Stream Map and a Future State Value Stream Map?
- Current State shows historical performance from 5 years ago; Future State shows theoretical performance in 20 years
- Current State depicts how the process operates today with existing wastes; Future State depicts the target operating model with identified wastes eliminated Correct answer.
- Current State is drawn by external auditors; Future State is drawn by junior developers
- Current State includes costs; Future State includes employee job descriptions
Explanation
The Current State map captures actual current workflow and wastes observed at Gemba. The Future State map envisions how work will flow once waste elimination and improvement ideas (Kaizen bursts) are implemented.
Question 40Lean customer value, value streams and pull
A Lean IT team calculates an Activity Ratio of 4% for their user provisioning process. What does this metric indicate to management?
- 96% of the end-to-end time is spent actively adding value for the user
- 96% of the total lead time consists of waiting, queuing, or non-value-adding delays Correct answer.
- The provisioning system is operating at 96% energy efficiency
- 4% of employees are performing 96% of the work
Explanation
An activity ratio of4% means the measured active processing occupies4% of the defined end-to-end lead time;96% lies outside that active-work measure. This does not prove every remaining minute is avoidable waste or unnecessary control. Verify boundaries, necessary waits and customer requirements before redesigning the process.
Question 41Lean customer value, value streams and pull
A team measures the percentage of incident tickets resolved correctly on the first attempt without requiring rework or re-assignment. What metric are they evaluating?
- Mean Time to Detect (MTTD)
- First Pass Yield (FPY) Correct answer.
- Takt Time
- Capacity Utilization
Explanation
First Pass Yield (FPY) measures the percentage of units or requests that complete a process step correctly the first time without needing rework, correction, or scrap.
Question 42Lean customer value, value streams and pull
In value stream analysis, if a step has a Process Time of 15 minutes and a queue wait time of 45 minutes before starting, what is the total Lead Time for that individual step?
- 15 minutes
- 45 minutes
- 60 minutes Correct answer.
- 30 minutes
Explanation
Step Lead Time = Wait Time + Process Time = 45 minutes + 15 minutes = 60 minutes.
Question 43Lean customer value, value streams and pull
What is the primary danger of optimizing a single process step in isolation without viewing the end-to-end value stream?
- It guarantees immediate 100% cost savings for the firm
- It may create local optimization that shifts the bottleneck elsewhere or worsens overall value stream lead time Correct answer.
- It automatically reduces server hardware warranty periods
- It violates international ISO financial accounting standards
Explanation
Local optimization often speeds up a non-bottleneck step, causing work to pile up even faster at the true bottleneck, creating more inventory waste without improving overall throughput.
Question 44Lean customer value, value streams and pull
Which metric measures the proportion of total time in a value stream spent actively transforming work versus total elapsed time?
- Process Efficiency / Activity Ratio Correct answer.
- Server Uptime Percentage
- Customer Retention Rate
- Cost Variance Ratio
Explanation
Process Efficiency (Activity Ratio) = (Process Time / Lead Time) × 100%. It reveals how much of the process duration creates true value vs idle waiting.
Question 45Lean customer value, value streams and pull
What is the primary focus of 'Value Stream Mapping' compared to traditional process flowcharting?
- Process flowcharts focus only on micro-level steps, whereas VSM visualizes end-to-end flow, time metrics (Lead Time vs Process Time), and waste identification Correct answer.
- VSM is only used in car manufacturing, while flowcharts are only used in IT
- Flowcharts include cost data, whereas VSM includes server passwords
- There is no difference between VSM and process flowcharts
Explanation
While flowcharts map sequential activities, VSM provides a holistic view connecting customer demand, information flow, work flow, and critical time metrics (Lead Time, Process Time, Activity Ratio).
Question 46Lean customer value, value streams and pull
An IT organization maps a complex release value stream with 5 sequential steps. Step 1 FPY = 95%, Step 2 FPY = 90%, Step 3 FPY = 85%, Step 4 FPY = 90%, Step 5 FPY = 95%. The team wants to increase overall Rolled First Pass Yield (RFPY) above 75%. What is the current RFPY, and which step should be prioritized first for Kaizen?
- Current RFPY is 62.1%; prioritize Step 3 first because it has the lowest individual yield (85%) Correct answer.
- Current RFPY is 91.0%; prioritize Step 1 first
- Current RFPY is 45.0%; prioritize Step 5 first
- Current RFPY is 75.0%; no improvement is needed
Explanation
Current RFPY = 0.95 × 0.90 × 0.85 × 0.90 × 0.95 = 0.621 (62.1%). To raise overall yield most effectively, prioritize Kaizen on the step with the lowest yield (Step 3 at 85%).
Question 47Lean customer value, value streams and pull
A software value stream exhibits the following metrics: Total Lead Time = 20 days, Total Process Time = 10 hours (1.25 days). Takt time is 4 hours per release. The team implements continuous integration automation, reducing Lead Time to 5 days while Process Time drops to 5 hours (0.625 days). What is the new Activity Ratio, and how did process efficiency change?
- New Activity Ratio is 12.5%, representing a doubling of process efficiency from 6.25% Correct answer.
- New Activity Ratio is 25.0%, representing a quadrupling from 6.25%
- New Activity Ratio is 5.0%, representing a decrease in efficiency
- New Activity Ratio is 50.0%, representing complete perfection
Explanation
Original Activity Ratio = 1.25 days / 20 days = 6.25%. New Activity Ratio = 0.625 days / 5 days = 0.125 or 12.5%. Efficiency doubled from 6.25% to 12.5%.
Question 48Lean customer value, value streams and pull
An enterprise IT service stream has a Takt Time of 10 minutes. Step 1 Cycle Time = 8 mins, Step 2 Cycle Time = 14 mins, Step 3 Cycle Time = 7 mins. Which step violates Takt Time, and what operational condition results?
- Step 2 violates Takt Time; it creates a bottleneck where work piles up and customer demand cannot be met on time Correct answer.
- Step 1 violates Takt Time; it causes upstream server crashes
- Step 3 violates Takt Time; it runs too fast and generates extra cost
- None of the steps violate Takt Time; the system is in perfect balance
Explanation
Step 2 Cycle Time (14 mins) exceeds Takt Time (10 mins). Because Step 2 cannot keep up with customer demand pace, it becomes a bottleneck and causes queue build-up.
Question 49Lean customer value, value streams and pull
Which of the following describes a 'Pull system' in IT service delivery?
- Work is assigned to team members automatically based on strict calendar schedules regardless of capacity
- Work is initiated only when downstream demand exists and capacity is available to process it Correct answer.
- Upper management pushes new project requirements into sprint backlogs without consulting team leads
- Servers automatically push system updates to client machines during peak business hours
Explanation
In a Pull system, downstream steps signal upstream steps to produce work only when there is active demand and available capacity, preventing overproduction and inventory build-up.
Question 50Lean customer value, value streams and pull
In Lean IT, what does the concept of 'Flow' aim to achieve?
- Maximizing the batch size of software releases to once per year
- Ensuring work items move smoothly through the value stream without delays, interruptions, or backlogs Correct answer.
- Increasing the number of approval handoffs between IT departments
- Forcing developers to work 80 hours per week
Explanation
Flow means work moves continuously and smoothly from start to finish without stopping, waiting in queues, or being delayed by handoff friction.