Study guide: Agile Project Implementation Approaches

Course Outline

  1. From Planning to Implementation
  2. Waterfall Predictive Method
  3. Agile Adaptive Method
  4. Scrum Framework and Roles
  5. Applying Kanban to the Robbery Example
  6. Kanban Workflow and Characteristics
  7. Comparing Implementation Approaches
  8. Hybrid Project Management
  9. Selecting an Implementation Approach
  10. User Stories and Agile Principles
  11. Traditional and Agile Development

1. From Planning to Implementation

โ˜… 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.

  • The implementation approach determines how the project plan becomes actual results.

๐Ÿ“Œ 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

  • Frequent change and customer feedback can favor Agile practices, while important regulation or documentation can call for more predictive controls.

Memory Hook

Planning defines what to achieve; implementation organizes how the team executes the work.

2. Waterfall Predictive Method

Key Concepts & Definitions

  • Predictive approach: One in which project work progresses through defined phases in sequence.

โ˜… Must-know

  • A typical Waterfall sequence consists of:
    • Requirements
    • Design
    • Development
    • Testing
    • Delivery

๐Ÿ“Œ 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 typically involves substantial upfront planning, early clarification of requirements, phase-specific purposes, detailed documentation, progress measured against a plan, and formal management of changes.

๐Ÿ“Œ 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.

  • The project proceeds through:
    • Requirements definition
    • Architectural design
    • Approvals
    • Contractor procurement
    • Construction
    • Inspection
    • Handover

Memory Hook

Requirements โ†’ design โ†’ develop โ†’ test โ†’ deliver.

3. Agile Adaptive Method

Key Concepts & Definitions

  • Agile: A flexible, iterative approach to project management, particularly when requirements, priorities, and stakeholder expectations may change.

โ˜… Must-know

  • ๐Ÿ”„ Agile work follows a repeating cycle of:

    1. Planning
    2. Development
    3. Delivery
    4. Feedback
    5. Learning
    6. Adaptation
  • 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:

    • Adaptability
    • Collaboration
    • Customer value
    • Feedback
    • Working results
    • Continuous improvement
  • Agile work is iterative and incremental, flexible, customer-focused, collaborative, adaptive, value-driven, self-organizing, continuously improving, and delivered frequently.

Memory Hook

Deliver, get feedback, learn, adapt, and repeat.

4. Scrum Framework and Roles

Key Concepts & Definitions

  • Sprint: A fixed time period in which a usable and potentially releasable deliverable is completed.
  • Product Backlog: The list of all deliverables for the project.
  • Increment: A usable addition to the product that meets the Definition of Done and builds on all previous Increments.

โ˜… Must-know

  • Scrum is an Agile framework for addressing complex adaptive problems while delivering valuable deliverables iteratively.

  • ๐Ÿ”„ Scrum organizes work through:

    1. Product Backlog
    2. Sprint
    3. Increment
    4. Feedback
    5. Next Sprint
  • 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.

Memory Hook

Backlog โ†’ Sprint โ†’ Increment โ†’ feedback โ†’ next Sprint.

5. Applying Kanban to the Robbery Example

Essential Points

  • In the Kanban jewelry-store robbery example, tasks C, E, and F are To Do, D is In Progress, B is under Review, and A is Done.

๐Ÿ“Œ Kanban may suit the robbery exercise as a practice model, but it is not suitable for the actual robbery.

6. Kanban Workflow and Characteristics

Key Concepts & Definitions

  • Kanban: A flow-based approach that makes work visible and helps teams manage work as it moves through a process.

โ˜… Must-know

  • ๐Ÿ”„ Work moves through four stages:

    1. To Do: deliverables not yet started
    2. In Progress: deliverables being worked on
    3. Review: deliverables being tested
    4. Done: completed deliverables
  • Kanban emphasizes these characteristics:

    • Visible workflow
    • Continuous flow rather than Sprints
    • Work-in-progress limits based on capacity
    • A pull system
    • Transparency
    • Flow improvement
    • Continuous workflow adjustment

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.

7. Comparing Implementation Approaches

โ˜… Must-know

  • The five implementation approaches are Waterfall, which plans comprehensively and executes sequentially; Agile, which delivers incrementally, gathers feedback, and adapts; Scrum, which structures Agile work into Sprints; Kanban, which visualizes work, manages flow, and limits work in progress; and Hybrid, which combines predictive and adaptive approaches.

๐Ÿ“Œ 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.

  • Waterfall is associated with stable requirements, Agile with changing requirements, Scrum with iterative product work, Kanban with continuous workflow, and Hybrid with mixed conditions.

8. Hybrid Project Management

Key Concepts & Definitions

  • Hybrid approach: Combines predictive and adaptive practices within the same project, with its design depending on the project requirements and characteristics.

โ˜… Must-know

  • Hybrid project management can combine approaches selectively across different parts of a project, remain flexible where appropriate, and use predictive elements to provide control and structure.

Further detail

  • For a phone app, predictive elements can include:

    • Budget
    • Contract
    • Security requirements
    • Launch deadline
  • In the phone-app example, the Hybrid approach pairs a fixed framework with flexible product development.

  • In the robbery example, predictive elements are:

    • Defining the overall objective
    • Defining constraints
    • Defining roles
    • Defining the time limit

Memory Hook

A fixed framework can contain flexible product development.

9. Selecting an Implementation Approach

โ˜… Must-know

  • ๐Ÿ”„ Approach selection proceeds by:
    1. Identifying the project's characteristics
    2. Considering the most important characteristics
    3. Choosing the best-fitting approach

Further detail

  • Relevant characteristics include:
    • Uncertainty
    • Change
    • Complexity
    • Stakeholders
    • Delivery
    • Constraints
    • Flow
    • Regulation

10. User Stories and Agile Principles

Key Concepts & Definitions

  • User Story: Expresses a requirement from the user's perspective.

โ˜… Must-know

  • The basic User Story format is: โ€œAs a [user], I want [goal], so that [benefit].โ€

๐Ÿ“Œ 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:

    • Independent
    • Negotiable
    • Valuable
    • Estimable
    • Small
    • Testable
  • User Stories help teams:

    • Understand user needs
    • Estimate work
    • Prioritize requirements
    • Plan Sprints
    • Discuss acceptance criteria
    • Maintain focus on value

Memory Hook

INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.

11. Traditional and Agile Development

โ˜… 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 clarifies requirements before the project starts, follows a linear sequence of development phases, and assesses outcomes at the end, while Agile continually enhances the process and repeats its phases iteratively.

๐Ÿ“Œ 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.

Memory Hook

Waterfall fixes scope and varies time and cost; Agile fixes time and cost and flexes scope.

Synthesis Tables

Waterfall and Agile Comparison

DimensionWaterfallAgile
ApproachPredictiveAdaptive
DevelopmentSequentialIterative or incremental
ScopeDefined earlyCan evolve
FeedbackMainly at the endContinuous
DeliveryMainly at the endFrequent increments

Scrum and Kanban

DimensionScrumKanban
StructureFrameworkFlow-management approach
Work rhythmSprintsContinuous flow
PlanningSprint-basedContinuous
RolesDefined Scrum rolesNo equivalent mandatory Scrum roles
Work in progressManaged within a SprintExplicit WIP limits commonly used
Primary focusProduct development through iterationsFlow and throughput

Test yourself

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?

Take the quiz โ†’

Study with flashcards

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.

See the flashcards โ†’

Related classes

Make your own study guides

Upload your class notes and Revizly writes a study guide, a quiz and flashcards in about a minute.

Study guide maker