1 / 45

Agile Demystified

Agile Demystified. Cesario Ramos. The idea behind the Agile Manifesto Why do we do these things? What about engineering principles?. Respond To Change. Promise the business Respond to change To stop whining Skills Technologies Process Soft enough!.

zilya
Download Presentation

Agile Demystified

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. Agile Demystified Cesario Ramos

  2. The idea behind the Agile Manifesto • Why do we do these things? • What about engineering principles?

  3. Respond To Change

  4. Promise the business • Respond to change • To stop whining • Skills • Technologies • Process • Soft enough!

  5. At the start they say ‘it will take us 10 months’

  6. Then they disappear from view! doing something, not clear what… then pop up after 8 months and say there might be some delay!!!

  7. One month before the deadline they pop up again…. and ‘we need 3 more months to finish’

  8. So finally in month 13 the testing can begin  Plan shows it should be finished in a month! …but issues are discovered

  9. Promises of Working software are not enough

  10. Working software means… • The business gets working software every month! • Could be put into actual use • It has real value, could be validated on customers. • Proves that there is actual progress

  11. IT no longer asking for trust but provides evidence. • Goes on month after month after month • stops when the business decides there is enough value added!

  12. Scrum In order to do this the business has to do some things in return

  13. OFTEN Face to Face feedback!!

  14. Do NOT ‘HELP’ IT by telling how to do things…

  15. The idea behind the Agile Manifesto • Why do we do these things? • What about engineering principles?

  16. Production vs. Product development What are characteristics of production and product development? What does it mean for the approach? Designator | author | April 06, 2009 |

  17. Origins in Lean manufacturing since 1950’s • High quality, high productivity and low cost • Highly successful

  18. The New New Product Development Game • Hirotaka Takeuchi • Ikujiro Nonaka Harvard Business Review, 1986.

  19. Complex Adaptive System A Complex Adaptive System (CAS) is a dynamic network of many agents acting in parallel, constantly acting and reacting to what the other agents are doing. The control of a CAS tends to be highly dispersed and decentralized. John H. Holland

  20. Lean concepts

  21. VALUE VALUE STREAM PERFECTION PULL FLOW

  22. Hand-offs Delay Task Switching Overproduction Defects Inventory Relearning

  23. How can we eliminate it? • Partially done work • Divide work into small batches • Limit WIP • Extra Features • Do NOT construct a signed list of everything upfront • Hand Offs • Face-to-face communication, cross functional teams • Delays • Cross functional teams, regular and short feedback cycles • Defects • Inspect to prevent defects, move testing to the front

  24. Some evidence for agility

  25. Overproduction of features Jim Johnson. The Standish Group International Inc. 2002

  26. Origins of defects Human 5% Environment 5% Logic/Design 28% Documentation 2% Data 6% Interface 6% Others 7% Tom Gilb. 2002 Requirements Errors 41%

  27. What can we do about it?

  28. Prioritized, refined and written down in collaboration between business and development

  29. Could be good enough to gain 80% of the benefits

  30. Implemented and accepted throughout the project

  31. The idea behind the Agile Manifesto • Why do we do these things? • What about engineering principles?

  32. [en.wiktionary.org] • Any apparently uselessactivity which, by allowing you to overcome intermediate difficulties, allows you to solve a larger problem. • I was doing a bit of yak shaving this morning, and it looks like it might have paid off. • The actually uselessactivity you do that appears important when you are consciously or unconsciously procrastinating about a larger problem. • I thought I'd get more work done if I just fixed a problem with my .emacs file, but then I spent the whole afternoon yak shaving.

  33. Verification • STOP discussing things with minimal facts…. • Kent Beck: No discussion should take longer than 30 minutes without writing/looking at some code to verify stuff. Programmers + Code > Programmers + Time

  34. Continuously improving the feedback speed!

  35. Fast Feedback • Getting the architecture right first…. Then we can add feature by feature easily right…? Hmmm… what if when implementing the first feature it proves that the infrastructure is wrong? • We build a couple of features and then refactor ending up with the architecture. • Generalize to remove duplication • Building exactly and only what is needed!!!

  36. Fast Feedback • Automatic Tests • Let the computer provide us feedback • Peer Reviews • Let your peer provide you with feedback • Spread knowledge • Take the first bullet • Refactor to the Open Closed

  37. ?

  38. Agile Demystified Cesario Ramos

More Related