1 / 20

Agile is so old hat, all the cool kids are doing lean now!

Richard Fennell Engineering Director BCS Edinburgh 11th May 2011. Agile is so old hat, all the cool kids are doing lean now!. The problem. Standish Group "CHAOS Summary 2009,”*

skip
Download Presentation

Agile is so old hat, all the cool kids are doing lean now!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Richard FennellEngineering Director BCS Edinburgh 11th May 2011 Agile is so old hat, all the cool kids are doing lean now!

  2. The problem Standish Group "CHAOS Summary 2009,”* "This year's results show a marked decrease in project success rates, with 32% of all projects succeeding which are delivered on time, on budget”… "44% were challenged which are late, over budget, and/or with less than the required features and functions and 24% failed which are cancelled prior to completion or delivered and never used.“ *http://www.standishgroup.com/newsroom/chaos_2009.php

  3. The Waterfall Process System Requirements Software Requirements Analysis Program Design Coding Testing Operations http://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdf

  4. Individuals and interactions Responding to change Working software Customer collaboration Following a plan Comprehensive documentation Contract negotiation Process and tools over over over over The Agile Manifesto a statement of values Source: www.agilemanifesto.org

  5. eXtreme Programming Source http://www.extremeprogramming.org

  6. eXtreme Programming Source http://www.extremeprogramming.org

  7. Sequential vs. overlapping development Requirements Design Code Test Rather than doing all of one thing at a time... ...agile teams do a little of everything all the time Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

  8. Scrum 24 hours Daily Scrum Meeting Backlog tasks expanded by team 10 - 30 days Sprint Backlog Potentially Shippable Product Increment Product Backlog As prioritized by Product Owner Source: Adapted from Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

  9. Scrum 24 hours Daily Scrum Meeting Backlog tasks expanded by team 10 - 30 days Sprint Backlog Potentially Shippable Product Increment Product Backlog As prioritized by Product Owner Source: Adapted from Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

  10. Crystal Clear It is part of the Crystal family, each box it’s own methodology that define: safety, efficiency and habitability Criticality of cost of failure More communication and coordination L – loss of life E – loss of essential monies D – loss of discretionary monies C – loss of comfort

  11. Crystal Clear It is part of the Crystal family, each box it’s own methodology that define: safety, efficiency and habitability Criticality of cost of failure More communication and coordination L – loss of life E – loss of essential monies D – loss of discretionary monies C – loss of comfort

  12. Crystal Clear It is part of the Crystal family, each box it’s own methodology that define: safety, efficiency and habitability Criticality of cost of failure More communication and coordination L – loss of life E – loss of essential monies D – loss of discretionary monies C – loss of comfort

  13. You can’t beat a wallboard Image Source: http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf

  14. Kanban Source http://ketiljensen.wordpress.com/2009/10/31/kanban-the-next-step-in-the-agile-evolution/

  15. Kanban Source http://ketiljensen.wordpress.com/2009/10/31/kanban-the-next-step-in-the-agile-evolution/

  16. Kanban Source http://ketiljensen.wordpress.com/2009/10/31/kanban-the-next-step-in-the-agile-evolution/

  17. Comparing the promises made • Waterfall makes a promise based on the triple constraint of scope, schedule and budget • Agile/Scrum makes a promise to a delivery date, but not to the exact scope of what will be delivered. This is constantly reprioritised • Lean/Kanban makes a completely different bargain, to regularly deliver high quality software based on an agreed SLA lead time

  18. Summary • Agile and Lean are not a magic bullets • Formality, process and documentation are not substitutes for discipline, skill and understanding • Interactive face to face communications are the cheapest and fastest channel for information exchange • Look at your processes and see where their techniques can be applied • Kanban may be an easier step than Agile for traditional Waterfall teams

  19. Reading List http://blogs.blackmarble.co.uk/blogs/rfennell/pages/reading-list.aspx

  20. Contact Richard Fennell Engineering Director, Black Marble Ltd. +44 (1274) 300175 http://www.blackmarble.co.uk http://blogs.blackmarble.co.uk/blogs/rfennell @RichardFennell

More Related