Agile and waterfall


Published on

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

Published in: Business, Technology

Agile and waterfall

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