Agile for CIOs
-
Upload
magentys -
Category
Technology
-
view
420 -
download
0
Transcript of Agile for CIOs
Agile for CIO’s (who may not get it yet)
By Carl Bruiners
Who am I?
Carl Bruiners
Agile - a way to deliver
Its more than just changing a workflow, adopting process or practice change. It’s a set of principles that guides your journey
Requirements
Analysis
Design
Code
Test
If Testing shows the requirement has not been met then the time has been lost
Feedback loop takes time as code is deployed and devs wait for test results
Only when code is written is it identified that it can’t meet the design
Waterfall…
Requirements
AnalysisCode/Test
DesignTest
Feedback loop is continuous and happens throughout each cycle
Deliver incremental changes into production quicker for faster results
Team collaboration up front removes Chinese whispers
Collaborate
Agile…
Agile is not a silver bullet
The selling point…
Often the reality…
Its all about people…
Aligning Culture (behaviors and beliefs)…
“Deciding what not to do is as important as deciding what to do"
Steve Jobs, Apple
How to delivery using Agile
Its more than just changing a workflow, adopting process or practice change. It’s a set of principles that guides your journey
Collaboration & Communication
• Collaboration with customer – deliver only what's needed• Get to see working outcomes every 1-4 weeks• Implement by feature not by task (design, code, test)• Feedback to delivery team sooner• Quality as part of process – testing is continuous• Continuous improvement built into cycle
Benefits of Agile
Six Sigma – Duplication of identical product. Good in manufacturing.
Waterfall – Planned in advance, struggles to embrace change, cannot be emergent
Agile – Emergent, unique each time, constant business collaboration
Six Sigma vs Waterfall vs Agile
The Agile umbrella
• Self Organizing* • Empowering• Collaborative• Active Customer Involvement • Frequent Delivery• Incremental• Time-Based*• Disciplined • Continuous Integration* • Feature Driven
• Adaptive• Goal Driven• Iterative • Lean • Emergent Approach
What is Agile development?
• Customer satisfaction by rapid, continuous delivery• Working software is the principle measure of success • Changes in requirements are anticipated and welcomed• Close, daily cooperation between business and developers• Face-to-face conversation is the best form of communication • Self-organizing teams• Regular adaptation to changing circumstances
Agile principles
Continuous improvement
Case study: Travis Perkins improving environment builds
Taking a 2 week process and making it 2 hours
不足Meaning: insufficient, lacking, deficiency, not enough, inadequate, not worth, cannot, should not
bù zú
Blame…
The savings…
Myths about Agile
Don’t let these myths put you off from taking the Agile journey…
Pragmatic does not equal compromised
Being pragmatic…
Its an engineering thing…
Agile is simple
Agile doesn’t work on large scale projects
Agile doesn’t lend itself well to highly regulated industries
One ring to rule them all…
Agile has little governance…
Common Pitfalls
Things that have caused pain to other organisations…
Its an IT thing…
Lack of prioritisation
Command and Control
Survival of the fittest
Tidal wave
Mike CohnDave SnowdenEric ReisRoman PilcherRon JefferiesKent BeckCarl BruinersClarke ChingSimon Cromarty
Further reading
Questions