Your SlideShare is downloading. ×

Agile and waterfall


Published on

brief overview on running projects with both agile and waterfall methodologies combined

brief overview on running projects with both agile and waterfall methodologies combined

Published in: Business, Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Challenges of running a combined waterfall and agile project or Why neither is best
  • 2. Firstly
    • What does "agile" and "waterfall" mean?
    • "Agile leaders lead teams
    • None-agile ones manage tasks"
  • 3. Waterfall
      • Manage activities
      • Granular
      • Sequential process
      • Requirements , design, build, test, release (maintain)....then fix
      • Highly structured
      • Well documented
      • Best suited to situations where 
    •       change is uncommon?
  • 4. Agile
      • Manage time
      • Highly collaborative
      • Customer is involved in the process
      • Regular delivery of 'products'
      • Flexible
      • Continuous Improvement
        • to both product
        • and process
  • 5. Agile manefesto
    • " Individuals and interactions over processes and tools.
    • Working software over comprehensive documentation.
    • Customer collaboration over contract negotiation.
    • Responding to change over following a plan."
  • 6. Bringing the two together
    • Agile methodologies generally promote a project management process that encourages stakeholder involvement, feedback, objective metrics and effective controls .
  • 7. Bringing the two together
    • Waterfall methodologies rely more on a defined set of requirements and tasks that cascade through the stages of the project to a 'neatly controlled' end.
  • 8. So what are the 'challenges' ?
  • 9. Challenges
      • Reporting 
        • Structured reports v Timeboxed daily standups and end sprint meetings
      • Financial management
        • Fixed costs v time and materials
        • Spending what we have wisely
      • Time  / resource management
        • Understanding what is achievable with what you have
  • 10. Challenges
      • Change 
        • Formal change management as opposed to change as part of the process
        • Not being afraid of change!
      • Managing customer expectations
        • Customer is part of the team not just a point of delivery
        • Delivering (not nesc deploying) products after each cycle
        • Customer understanding that they have a part to play in planning and re-planning each delivery 
  • 11. Challenges
      • Managing business expectations
        • We need to be paid, when will this happen (T&M v's fixed cost)
      • Communicating the 'plan'
        • A defined set of task against time as opposed to ...not?
  • 12. OR What can we do in the amount of time and resource  we have?  as opposed to We have to get this done in this much time
  • 13. Soooo...
    Chalk and cheese....right?
  • 14. Maybe not
      • Define long term but not short term goals and integrate into a longer term plan 
        • iterations within a defined period of time
      • Mini waterfalls with agile processes within them
      • Highlight reports = end sprint report
      • Be flexible
        • Waterfall - Plan, Release, Documentation processes
        • Agile - Development 
      • Prince2 can be / is agile (ish) 
  • 15. Finally
    • It all depends on the customer, project, environment, team ...
    • if it really is a challenge ....
    • (as opposed to an opportunity)
    • don't do it
  • 16. Like good a good UI
    • If you are aware of the challenges with the method you are using to run the project, you're doing it wrong
    • because
    • If you find yourself working all day maintaining the methodology....
    • who's taking care of business?