Coursya originals · Free PDF ebook

Agile vs. Waterfall: Choosing the Right Approach

Choose a delivery approach using uncertainty, feedback, change cost and dependencies, with a worked visitor-centre example and a practical decision note.

Agile, Scrum & Kanban

Choose a delivery approach using uncertainty, feedback, change cost and dependencies, with a worked visitor-centre example and a practical decision note.

This guide compares planning patterns through a project with both physical and digital work. It explains predictive, adaptive and hybrid choices and connects them to scope, quality, governance and supplier interfaces.

Start with the decision

Choose an approach that helps this project learn, coordinate and deliver value. Both approaches need plans, decisions and evidence. An unclear requirement and an unknown technical method create different learning needs. Fast feedback is valuable when it can influence the next decision.

Try a clickable booking prototype with five visitors this week. For the entrance, inspect drawings, survey the site and review compliance before committing to installation.

Scope and requirements

The level of early detail should match the work and the cost of change. Frequent delivery still needs coherent technical decisions and working interfaces. The approach depends on people being able to perform the feedback and delivery work. Useful control can coexist with different delivery rhythms.

The physical entrance needs compliance evidence and inspections. The booking pilot needs recorded user feedback, quality checks and a clear rollout decision. Both need accountable owners.

Schedule and funding

Compare credible forecasts rather than treating a preferred date as evidence. A delivery approach changes the learning pattern, not the need for usable results. Commercial commitments need to support the work’s uncertainty and controls. A project can contain work with different learning and commitment patterns.

The booking launch needs a confirmed opening capacity and staffing pattern. The entrance rollout needs the visitor communication ready. Different rhythms still meet at readiness decisions.

Design a hybrid deliberately

A hybrid approach needs an integration logic you can explain. Use a small comparison to make assumptions visible. A delivery choice should remain useful as the project learns. Finish with a clear explanation the sponsor and team can challenge.

Recommend a defined entrance package plus iterative booking pilots, linked by a shared readiness gate. Seek the survey and integration-test evidence before committing the full rollout.

Contents

  1. Start with the decision
  2. Predictive and adaptive planning
  3. Understand the type of uncertainty
  4. Look at the cost of feedback
  5. Scope and requirements
  6. Architecture and integration
  7. Team capability and access
  8. Governance and documentation
  9. Schedule and funding
  10. Quality and acceptance
  11. Supplier arrangements
  12. Dependencies between the approaches
  13. Design a hybrid deliberately
  14. Work the selection matrix
  15. Revisit the approach when facts change
  16. Your approach decision note

Using the PDF

Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.

Frequently asked questions

How does the visitor-centre team choose an approach?

It can test a booking prototype with five visitors in a week. For the physical entrance, the team needs drawings, a site survey and compliance checks before it commits to installation.

How many pages are in the ebook?

The ebook contains 19 pages.

How can I download the ebook?

Use the download button on this page to open the ebook and save a copy.

Share this article