โ Must-know
๐ Project planning defines the scope, WBS, schedule, resources, budget, risks, and milestones, whereas implementation organizes work, workflow, execution rhythm, team coordination, cost control, adaptation, and progress monitoring.
๐ An implementation approach should fit project characteristics: stable requirements may suit predictive methods, uncertain requirements may suit adaptive methods, continuous workflow may suit Kanban, iterative work may suit Scrum, and a mix of fixed and uncertain elements may suit a hybrid approach.
Further detail
Planning defines what to achieve; implementation organizes how the team executes the work.
โ Must-know
๐ Waterfall may be appropriate when requirements are stable, the solution is understood, changes are limited, dependencies require sequential execution, documentation or regulation is important, or a defined final deliverable is required.
Further detail
๐ Waterfall offers a clear, predictable sequence, extensive documentation, and clear milestones, but it is less adaptable, depends on early requirements definition, delays feedback, and can make change or rework costly.
Requirements โ design โ develop โ test โ deliver.
โ Must-know
๐ Agile work follows a repeating cycle of:
Agile does not mean having no plan; it means planning continuously and adapting the plan as new information emerges.
Agile may be appropriate when requirements or stakeholder expectations can change, innovation and feedback matter, solutions can be delivered incrementally, the environment changes quickly, or learning occurs during development.
Waterfall is predictive and sequential, with scope defined early, feedback mainly at the end, detailed upfront planning, and delivery mainly at the end; Agile is adaptive and iterative or incremental, with evolving scope, continuous feedback and planning, and frequent increments.
Further detail
Agile emphasizes:
Agile work is iterative and incremental, flexible, customer-focused, collaborative, adaptive, value-driven, self-organizing, continuously improving, and delivered frequently.
Deliver, get feedback, learn, adapt, and repeat.
โ Must-know
Scrum is an Agile framework for addressing complex adaptive problems while delivering valuable deliverables iteratively.
๐ Scrum organizes work through:
The Product Owner prioritizes work to maximize project value and manages the Product Backlog.
Further detail
Developers create the product Increment and organize their development work.
The Scrum Master helps the team understand and implement Scrum.
Scrum applies Agile through fixed Sprint durations, intermediate results, regular coordination, reassessed priorities, feedback reviews, retrospectives, and team self-organization.
Backlog โ Sprint โ Increment โ feedback โ next Sprint.
๐ Kanban may suit the robbery exercise as a practice model, but it is not suitable for the actual robbery.
โ Must-know
๐ Work moves through four stages:
Kanban emphasizes these characteristics:
Further detail
๐ A Kanban work-in-progress limit restricts how many items can be worked on simultaneously, helping limit multitasking, identify bottlenecks, and improve project flow.
โ Must-know
๐ Waterfall is predictive, Agile is adaptive, Scrum and Kanban apply Agile, and Hybrid combines approaches; these approaches operate at slightly different levels.
๐ Scrum organizes work into Sprints with defined roles and Sprint-managed work in progress, while Kanban manages continuous flow with commonly used explicit work-in-progress limits and no equivalent mandatory Scrum roles.
Further detail
๐ Scrum focuses on product development through iterations, whereas Kanban focuses on flow and throughput.
โ Must-know
Further detail
For a phone app, predictive elements can include:
In the phone-app example, the Hybrid approach pairs a fixed framework with flexible product development.
In the robbery example, predictive elements are:
A fixed framework can contain flexible product development.
โ Must-know
Further detail
โ Must-know
๐ A User Story describes what the user needs and why, a project task describes the work the team must perform to deliver the story, and acceptance criteria define what must be completed for the story to count as complete.
Further detail
A User Story example is: โAs a student, I want to see my timetable on my phone, so that I can quickly check where I need to be.โ
A good User Story should generally be:
User Stories help teams:
INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.
โ Must-know
๐ Waterfall proceeds through fixed, separate phases, whereas Agile uses progressive, iterative stages and delivers preliminary results during the project.
๐ In Waterfall, the project's scope is set while time and cost vary; in Agile, time and cost are fixed while scope remains flexible.
Further detail
๐ Waterfall allows stakeholder influence to diminish as the project advances, whereas Agile presents a preliminary result after each iteration, enables requirement adjustments, and maintains ongoing stakeholder influence.
Waterfall supports comprehensive documentation, whereas Agile relies on a self-organizing team and daily communication.
The Agile principles listed include customer satisfaction through continuous, quick delivery of valuable software; adapting to evolving requirements even late in development; frequent delivery of functional software; collaboration between clients or business and developers; motivated, trusted people; in-person conversation as the most effective communication; functioning software as the primary progress measure; sustainable development; technical excellence and good design; simplicity as maximizing undone work; self-organizing teams; and teams that continually adjust to changing conditions.
Waterfall fixes scope and varies time and cost; Agile fixes time and cost and flexes scope.
| Dimension | Waterfall | Agile |
|---|---|---|
| Approach | Predictive | Adaptive |
| Development | Sequential | Iterative or incremental |
| Scope | Defined early | Can evolve |
| Feedback | Mainly at the end | Continuous |
| Delivery | Mainly at the end | Frequent increments |
| Dimension | Scrum | Kanban |
|---|---|---|
| Structure | Framework | Flow-management approach |
| Work rhythm | Sprints | Continuous flow |
| Planning | Sprint-based | Continuous |
| Roles | Defined Scrum roles | No equivalent mandatory Scrum roles |
| Work in progress | Managed within a Sprint | Explicit WIP limits commonly used |
| Primary focus | Product development through iterations | Flow and throughput |
Take a 30-question practice quiz on Agile Project Implementation Approaches, with every answer explained.
1. A project manager has already defined the project scope, WBS, schedule, resources, budget, risks, and milestones. Which activity is most directly part of implementation rather than planning?
2. A team is developing a solution whose requirements are uncertain and expected to evolve as users provide input. Which implementation approach best fits this project characteristic?
Memorize the key concepts of Agile Project Implementation Approaches with 76 flashcards.
Which activities define project planning?
Scope, WBS, schedule, resources, budget, risks, and milestones.
Which activities organize project implementation?
Workflow, execution rhythm, team coordination, cost control, adaptation, and progress monitoring.
What determines how a project plan becomes actual results?
The implementation approach.
Upload your class notes and Revizly writes a study guide, a quiz and flashcards in about a minute.
Study guide maker