Why agile
- 1. Why to move to agile
- 2. Introduction
- 3. Expectations
- 6. Individuals and interactions over processes and tools
- 7. Working software over comprehensive documentation
- 8. Customer collaboration over contract negotiation
- 9. Responding to change over following a plan
- 12. Comparison Process Traditional Development Agile Development Measure of Success Conformance to plan Response to change, working software Management Culture Command and Control Leadership/Collaborative Requirements and Design Big and up front Continuous/emergent/just-in- time Coding and Implementation Code all features in Code and unit test, deliver parallel/test later serially Test and Quality Assurance Big, planned/test late Continuous/concurrent/test early Planning and Scheduling PERT/detailed/fix scope, Two-level plan, fix-date, estimate time and resource estimate scope
- 14. You will hit the wall
- 15. Barriers to agile adoption
- 16. There will be resistance
- 18. Problems solved?
- 20. Credits Survey data: http://www.versionone.com/state_of_agile_development_survey/11/ Agile Manifesto http://agilemanifesto.org/
- 21. Pictures Why to move to agile: http://yogaalliance500.com/wp-content/uploads/2011/09/nicki-doane-yoga-teacher1.jpg Introduction http://blog.advancedcopy.com/wp-content/uploads/2011/05/Shaking_Hands.jpg Expectations http://dilbert.com/strips/comic/2008-04-08/ Problems of Waterfall http://www.royalcanoeclub.com/wp-content/uploads/2012/04/Waterfall-kayak.jpg Introduction to agile http://upload.wikimedia.org/wikipedia/commons/thumb/8/89/Agile_Software_Development_methodology.svg/320px- Agile_Software_Development_methodology.svg.png Individuals and interactions over processes and tools http://saris.kcn.unima.mw/kcnconnect/wp-content/uploads/2012/07/meeting.jpg Working software over comprehensive documentation http://aaron.sakovich.org/blog/images/installation_successful.jpg Customer collaboration over contract negotiation http://marketculture.files.wordpress.com/2012/09/istock_customer-metrics.jpg Responding to change over following a plan http://clockblocking.files.wordpress.com/2011/04/road-line-painted-around-fallen-tree-branch.jpg You will hit the wall http://1.bp.blogspot.com/-NEb9NMo2ByQ/T9wik7JOBNI/AAAAAAAAAF4/T5Y0dbVY1cA/s1600/great_wall_of_china+(1).jpg There will be resistance http://viewfromventress.org/files/2011/05/civil-war-cannon.jpg Problems solved? http://jordanalexander.files.wordpress.com/2010/08/math1.jpg Expectations check http://www.chalumeaulawgroup.com/wp-content/uploads/2012/05/checklist.jpg Thank you for your attention http://westlothiankarateassociation.files.wordpress.com/2012/08/bigstock_karate_boy_bowing_149219.jpg
- 22. Thank you for your attention!
- 23. Contact Information Sven Schnee Agile Project Manager Twitter: @MrSnow76 LinkedIn: http://www.linkedin.com/pub/sven-schnee/27/932/5a5 Luis-Miguel Goncalves Agile Project Manager Twitter: @lgoncalves1979 LinkedIn: http://www.linkedin.com/in/luismsg
Editor's Notes
- #2: Luis introductionGood friend, university with bossWorking agile many yearsWorkshop in this company2 mins
- #3: Luis:DeveloperNokiaSven:Developer 10+ yearsAgile Project ManagerBeginning Agile CoachingAsk for the roles in the roomPMsDevelopersProject ManagersLine Managers/Managers4-5 mins
- #4: Ask them about their expectations:Note them on the flipchart3 mins
- #5: Luis:Ask audience for their biggest challenges with the waterfall approachBig bangMany problems at the endLacking qualityDelayed releasesStress3-4 mins
- #6: This is just an overview:Cornerstones of AgileTechnical doing not in scopeCoding-Dojos conferences or further workshops1-2 mins
- #7: Business people and developers must work together daily throughout the project.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.3-5 mins
- #8: Working software is the primary measure of progress.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.Simplicity--the art of maximizing the amount of work not done--is essential.2 mins
- #9: Our highest priority is to satisfy the customer through early and continuous deliveryof valuable software.Continuous attention to technical excellence and good design enhances agility.1 mins
- #10: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.The best architectures, requirements, and designs emerge from self-organizing teams.3-4 mins
- #11: Luis:1-2 mins+ 10 mins flipchart
- #12: Luis:2-3 mins
- #13: Luis3-4 mins
- #14: Luis:3 mins
- #16: Sven:Its not that easyMentality changeNot everyone is a team playerWay of working is drastically changed1-2 mins
- #17: Sven:2-3mins
- #18: Not everyone likes changeChange brings you out of your comfort zoneConflict will arise1 min
- #19: Sven:2 3 mins
- #20: Luis:3-4mins
- #21: Luis:2-3 mins