--- title: "Agile model" subject: "ICT Project Management" chapter: 4 key: "semester_7/ict_project_management:agile-model" source: https://www.bctengineer.com/q/semester_7/ict_project_management/agile-model site: BCT Engineering --- # Agile model ICT Project Management · Chapter 4: Project Management - Asked in: year not given - Video: [What Is Agile Methodology? | Introduction to Agile Methodology in Six Minutes | Simplilearn](https://www.youtube.com/watch?v=8eVXTyIZ1Hs) — Simplilearn - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_7/ict_project_management/agile-model - Whole chapter: https://www.bctengineer.com/md/semester_7/ict_project_management/chapter-4 ## Question What do you mean by agile model? Explain it in detail. ## Short answer The agile model is an iterative, incremental approach valuing flexibility, collaboration and quick delivery. Based on the Agile Manifesto, it uses short sprints with continuous feedback. It handles change well but is hard to predict for large projects and needs experienced teams. ## Answer The **agile model** is an iterative and incremental approach to software development that values flexibility, customer collaboration and quick delivery of working software. It is based on the Agile Manifesto (2001). #### Agile Manifesto values - Individuals and interactions over processes and tools. - Working software over comprehensive documentation. - Customer collaboration over contract negotiation. - Responding to change over following a plan. #### Principles Early and continuous delivery, welcome changing requirements, frequent delivery in weeks, daily cooperation between business and developers, motivated teams, face-to-face communication, working software as the main measure of progress, sustainable pace, simplicity and regular reflection. #### Process (Scrum example) ```text Product backlog -> Sprint planning -> Sprint (2-4 wks) ^ | daily scrum | v Feedback <- Sprint review <- Working increment ``` - **Roles**: Product Owner, Scrum Master, Development Team. - **Artifacts**: product backlog, sprint backlog, increment. - **Events**: sprint planning, daily stand-up, sprint review, retrospective. Other agile methods: Extreme Programming (XP), Kanban, Crystal, FDD. #### Advantages - Quick delivery and early feedback. - Handles changing requirements well. - High customer involvement and satisfaction. - Reduced risk through small increments. #### Disadvantages - Hard to predict final cost and time for large projects. - Needs experienced, self-organised team and constant user availability. - Less documentation can create maintenance problems. - Difficult with fixed-price contracts. | Agile | Waterfall | |---|---| | Adaptive | Predictive | | Short iterations | Single long pass | | Change welcome | Change resisted | **Example:** A startup builds a food-delivery app in two-week sprints, releasing ordering first and adding payment and tracking later based on user feedback. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. According to the Agile Manifesto, what is valued over comprehensive documentation? A. Contract negotiation B. Following a plan C. Working software D. Processes and tools Answer: C. The manifesto prefers working software over comprehensive documentation. (Key point: Manifesto values) 2. Which is the set of Scrum roles? A. Sponsor, Auditor, Tester B. Product Owner, Scrum Master, Development Team C. Project Manager, Analyst, Vendor D. Customer, Architect, Trainer Answer: B. Scrum defines these three roles. (Key point: Scrum roles) 3. Why is agile difficult with fixed-price contracts? A. Final cost and time are hard to predict for large projects B. It produces no working software C. It forbids customer contact D. It requires full documentation up front Answer: A. Adaptive scope makes cost and time hard to fix in advance. (Key point: Disadvantage) 4. How does agile compare with waterfall? A. Agile is predictive with one long pass B. Both resist change C. Agile has no iterations D. Agile is adaptive with short iterations and welcomes change; waterfall is predictive Answer: D. Agile is adaptive, iterative and welcomes change, whereas waterfall is predictive. (Key point: Agile vs waterfall) ## Related in ICT Project Management - [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 - [Lean model](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Alean-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 - [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 - [Conceptual, specification, implementation model classification](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Ahospital-conceptual-specification-implementation) — Object Oriented Analysis and Design, chapter 2