Simon Raik Allen - How to Convince your CIO you want to be Agile
•Download as PPT, PDF•
0 likes•661 views
This document provides tips for convincing a CIO to adopt agile practices. It discusses choosing a small initial project, letting executives experience agile firsthand, and focusing on goals like working software rather than using every agile technique. Planning, managing risks and technical debt, showcasing results, and retrospectives are emphasized. The overall message is to thoughtfully plan an introduction to agile tailored to your organization's needs rather than trying to fully implement agile or make unrealistic promises.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Simon Raik Allen - How to Convince your CIO you want to be Agile
Similar to Simon Raik Allen - How to Convince your CIO you want to be Agile (20)
More from AgileNZ Conference
More from AgileNZ Conference (20)
Recently uploaded
Recently uploaded (20)
Simon Raik Allen - How to Convince your CIO you want to be Agile
- 1. How To Convince Your CIO You Want to be Agile Simon Raik-Allen MYOB @simonraikallen Your pic
- 5. +
- 6. CHAOS Report • Executive Support • User Involvement • Requirements • Project size (optimization)
- 7. QUALITY FEATURES INNOVATION PRODUCT SUCCESS TIME TO MARKET
- 8. Types of IT Groups
- 9. The Business Engineering uivfication
- 10. The Business Users Engineering
- 11. VALUE WASTE
- 12. What do execs eat in the wild?
- 13. Data
- 15. “If you decide to cancel the project, you’ll at least have working software” Working Software
- 21. E.E.F.
- 26. The Goal Is Let your exec experience life in an Agile environment The Goal Is Not Have your project be a smashing success at all cost Its Also Not Use every Agile technique in the book
- 27. What is executive porn? A plan Also developer repellant.
- 28. THE AGILE PLANNING PLEDGE I WILL NOT WING IT I WILL ALWAYS THINK AHEAD I WILL EVALUATE CONTINGENCIES SEARCH FOR PITFALLS AND CONTINUOUSLY PLAN AND RE-PLAN A MILLION RANDOM TYPING MONKEYS CANNOT TAKE MY JOB
- 29. Elements of a Plan • Hypotheses • Spikes • Possible outcomes • Story order (risk) • Feature release map • Team distribution • User testing checkpoints • Estimated burn up chart
- 30. Reporting
- 32. The Show Case
- 33. Technical Debt
- 34. DOs DON’Ts Understand your own situation Become one with your goals Choose a small project Take on only a few techniques Plan Plan & Re-plan Treat debt with responsibility Over sell it – time or money Say “Agile” Hide behind cards Waffle Succumb to EEF Screw it up And…
- 35. Retros
- 36. Thanks for listening… Simon Raik-Allen MYOB @simonraikallen Your pic
Editor's Notes
- Consulting | Product (consumer) | Product (advertiser) | Enterpirse
- Difference is transparency
- Agilists obsessed with not forward thinking things “hypothesis” is your out for early optimization
- Everyone should be involved in reporting Its not good that team members are disconnected to the results Why? Next slide.
- Good for you and the team. Not great for execs Team leads etc, yes. Good opportunity for execs to encourage the team Make it clear to them what the purpose is Otherwise, they become the focus and take over
- Good for you and the team. Not great for execs Team leads etc, yes. Good opportunity for execs to encourage the team Make it clear to them what the purpose is Otherwise, they become the focus and take over