PMI Ireland Annual Conference 2012 - Agile First Steps
1 like567 views
The document discusses taking first steps towards adopting agile practices. It recommends making work visible, establishing roles and teams, and establishing a flow of work. Specifically, it suggests using boards to visualize work, defining Scrum roles like Product Owner and Scrum Master, and focusing on continuous flow through techniques like limiting work in progress.
More Related Content
![Agile Developers Create Their Own Identity[1]](https://cdn.slidesharecdn.com/ss_thumbnails/agiledeveloperscreatetheirownidentity1-12795469184258-phpapp02-thumbnail.jpg?width=560&fit=bounds)
Similar to PMI Ireland Annual Conference 2012 - Agile First Steps (20)
![UNIT 3 INTERNATIONAL BUSINESS [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/unit3internationalbusinessautosaved-250828123159-46ee6bdc-thumbnail.jpg?width=560&fit=bounds)
PMI Ireland Annual Conference 2012 - Agile First Steps
- 1. I’ll go up and find out what they need and the rest of you start coding! PMI Ireland 2012 AGILE – FIRST STEPS
- 2. This material is Copyright Protected under the following Creative Commons License: Attribution-‐ShareAlike 3.0 Please use this material freely and derive further work from it. BUT, attribution must be given to the original author, and these same rights must govern all derived works. Please use the following attribution: “Colm O’hEocha, AgileInnovation Ltd. 2012: www.agileinnovation.eu”
- 3. AgileInnovation Copyright © 2012 AgileInnovation
- 4. Process Control Models OPEN-LOOP CLOSED-LOOP Analytical - Predictive Empirical - Adaptive Set Target Controller Set Target Controller Inspect AIM & FIRE FIRE & AIM Copyright © 2010 AgileInnovation
- 5. Copyright © 2010 AgileInnovation
- 6. Sense + Act -‐> Agility • Iteration Plan • Team Board • Daily Stand-‐Up… Set Target Adapt Controller Inspect • Clean Design & Code • Late Elaboration (e.g. User Stories) • Pair Programming • Shared Code Ownership • Customer Reviews & • Test Driven Development….. Feedback • Retrospectives • AutoTest….. Copyright © 2011 AgileInnovation
- 7. Flipping the Iron Triangle FIXED Scope/ Resources Requirements Schedule Value Driven Plan Driven ESTIMATED Resources Schedule Scope/ Requirements Quality Quality Copyright © 2010 AgileInnovation
- 8. Copyright © 2010 AgileInnovation
- 9. Software Development as Sport Copyright © 2011 AgileInnovation
- 10. Scrumbut vs. Scrumbutt Sure we do Scrum, but… Ø We do ‘feature length’ sprints Ø Our stories span several sprints Ø We work from a requirements spec Ø We don’t bother with retrospectives Ø Our manager approves our estimates Ø Our QA team is offshore Ø “Iteration 0” or ”Pre-Sprint” Ø “Hardening Sprints” Ø … Copyright 2010 AgileInnovation Limited
- 11. First Steps… 1. Make the Work Visible 2. Put Roles and Teams in Place 3. Establish a Flow of Work
- 12. Make the Work Visible
- 14. Primary Product Owner Portfolio Management Applications Product Owner Product Owner Product Owner Architecture Team Platform Segment A Segment B Customer A Customer B
- 15. Project Manager Scrum Master (Position of Authority) (Servant-‐Leader) " Plan & Coordinate " Facilitate Practices " Staff & Assign " Enforce Constraints " Track & Report " Remove Impediments " Risk & Issue Mgt " Block Distractions " Evaluate & Reward " Carry Food & Water " … " … Copyright © 2010 AgileInnovation
- 16. Align Teams with Value Flow Product Backlog Product Backlog Product Backlog Product Backlog Product Backlog
- 17. Align Teams with Value Flow Product Backlog Product Backlog Product Backlog
- 18. Communication and Co-‐Location Probability of Communicating at least once a week 30% 25% 20% 15% 10% 5% 0% 0 20 40 60 80 100 0 Separation Distance (meters) Copyright © 2010 AgileInnovation Source: Tom Allen
- 19. Flow
- 20. Lessons from Queuing Theory Copyright 2010 AgileInnovation Limited
- 21. Copyright 2010 AgileInnovation Limited
- 22. Stop Starting – Start Finishing
- 23. Effects of Multi-‐Tasking Psychological: • 20% Context Switching Loss • Distraction Hangover Systems: • Delayed Feedback • Longer Cycle Times Research shows that drivers using mobile phone have a higher accident rate than anyone except very drunk drivers
- 24. Out-‐Learn the Competition Information Generation • Maximise Information Value • Minimise Information Cost 100% Chance 100% Chance of Success Copyright © 2011 AgileInnovation of Failure
- 25. Copyright © 2010 AgileInnovation
- 26. Regular Demos
- 27. The Agile Adoption Curve The Agile Adoption Curve and ‘Chasms’ Consideration Investigation Routinization Awareness Acceptance Adaptation Adoption Infusion Pilot “We’re “Fail to different” Scale” Initiation Adoption Assimilation Copyright © 2010 AgileInnovation
- 28. Expect Resistance Enlist Support: • Top-‐Down: Executive Sponsor • Bottom-‐Up: Champions • Outside-‐In: Professional Coach
- 29. Evolutionary Change -‐ PDCA Plan – Do – Check -‐ Act • Decide on Small Changes • Implement/Experiment • Inspect the Results • Optimise/Stabilise/Embed • Repeat Copyright © 2010 AgileInnovation
- 30. Training is necessary but insufficient… ScrumAlliance – CSM, CSD, CST, CSP… Scrum.org – PSD, PSM, PST… Copyright © 2010 AgileInnovation
- 31. Facilitate Feedback Educate Coach Notice Support Copyright © 2010 AgileInnovation
- 32. Approved Supplier Lean Start Up to €5000 to Enterprise LeanPlus Up to 50% of €70,000 Ireland “Lean LeanTransform Up to 50% of >€70,000 Competitiveness Program”
- 33. Colm O’hEocha AgileInnovation [email protected]
- 34. This material is Copyright Protected under the following Creative Commons License: Attribution-‐ShareAlike 3.0 Please use this material freely and derive further work from it. BUT, attribution must be given to the original author, and these same rights must govern all derived works. Please use the following attribution: “Colm O’hEocha, AgileInnovation Ltd. 2012: www.agileinnovation.eu”