--- title: "Lean model" subject: "ICT Project Management" chapter: 4 key: "semester_7/ict_project_management:lean-model" source: https://www.bctengineer.com/q/semester_7/ict_project_management/lean-model site: BCT Engineering --- # Lean model ICT Project Management · Chapter 4: Project Management - Asked in: year not given - Video: [Lean Software Development Explained in Nepali | Lean Software Development Lecture Video | Agile Tool](https://www.youtube.com/watch?v=fpjSPjKQUUE) — ICT Training Nepal - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_7/ict_project_management/lean-model - Whole chapter: https://www.bctengineer.com/md/semester_7/ict_project_management/chapter-4 ## Question What do you mean by Lean model? Explain it in detail. ## Short answer The Lean model applies lean manufacturing principles to software, focusing on eliminating waste and maximizing value. Its seven principles include eliminating waste, amplifying learning, deciding late, delivering fast, empowering the team, building integrity in, and seeing the whole. It reduces waste and improves quality but needs a disciplined team. ## Answer The **Lean model** applies the principles of lean manufacturing (originating from the Toyota Production System) to software and project development. Its central idea is to deliver maximum customer value with minimum waste. Mary and Tom Poppendieck adapted it to software as "Lean Software Development". #### Seven principles of lean software development 1. **Eliminate waste**: remove anything that does not add value, such as unused features, extra documentation, waiting and task switching, defects, and handoffs. 2. **Amplify learning**: short feedback cycles, experiments, tests and reviews. 3. **Decide as late as possible**: keep options open until facts are known. 4. **Deliver as fast as possible**: short iterations give early feedback and value. 5. **Empower the team**: let people closest to the work make decisions. 6. **Build integrity in**: quality is built into the product through automated testing and continuous integration. 7. **See the whole**: optimise the whole system, not individual parts. #### Types of waste (in software) | Manufacturing waste | Software equivalent | |---|---| | Inventory | Partially completed work | | Over-production | Extra features | | Waiting | Delays for approvals | | Defects | Bugs and rework | | Motion | Task switching | #### Tools Value stream mapping, Kanban board, pull systems, continuous improvement (kaizen), 5 whys. ```text Backlog -> [Doing] -> [Review] -> [Done] (Kanban: limit work in progress) ``` #### Advantages Less waste, faster delivery, lower cost, better quality and satisfied customers. #### Limitations Needs a mature, disciplined team; less suitable for projects with fixed scope and heavy documentation needs. **Example:** An IT support team uses a Kanban board and limits work in progress to three tickets per person. This reduces waiting and shortens resolution time. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. What is the central idea of the Lean model? A. Maximise documentation B. Decide everything early C. Deliver maximum customer value with minimum waste D. Add as many features as possible Answer: C. Lean comes from the Toyota Production System and focuses on eliminating waste. (Key point: Central idea) 2. What is the software equivalent of inventory waste? A. Extra features B. Partially completed work C. Bugs and rework D. Task switching Answer: B. Inventory maps to partially done work; over-production maps to extra features. (Key point: Waste mapping) 3. What does 'Decide as late as possible' mean? A. Keep options open until facts are known B. Delay delivery of the product C. Avoid making any decisions D. Let management decide everything Answer: A. Late decisions rely on facts rather than guesses. (Key point: Decide late) 4. What is the purpose of limiting work in progress on a Kanban board? A. To increase the number of tasks started B. To remove the need for a board C. To add more documentation D. To reduce waiting and shorten completion time Answer: D. Limiting WIP reduces task switching and waiting, speeding up delivery. (Key point: Kanban WIP) ## Related in ICT Project Management - [Lean production](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Alean-production) — ICT Project Management, chapter 10 - [Project life cycles in detail](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Aproject-life-cycles) — ICT Project Management, chapter 4 - [Conventional waterfall model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Awaterfall-model) — ICT Project Management, chapter 4 - [Iterative and incremental model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Aiterative-incremental-model) — ICT Project Management, chapter 4 - [Agile model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Aagile-model) — ICT Project Management, chapter 4 - [Project management maturity model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Apm-maturity-model) — ICT Project Management, chapter 10 ## Related in other subjects - [Lean canvas and its blocks](https://www.bctengineer.com/question.md?key=semester_7%2Fentrepreneurship_development%3Alean-canvas-vs-business-model-canvas) — Entrepreneurship Development, chapter 4 - [Waterfall model: advantages and limitations](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Awaterfall-limitations) — Software Engineering, chapter 1 - [Book store process model](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Abook-store-process-model) — Software Engineering, chapter 2 - [Queuing model, Kendall, M/D/8/15/LIFO](https://www.bctengineer.com/question.md?key=semester_8%2Fsimulation_and_modeling%3Aqueuing-model-mdlifo-8) — Simulation and Modeling, chapter 4