successfully applying agile in infrastructure/media/hdifusion/files/...national agile practice...
TRANSCRIPT
SESSION 305 Wednesday, November 1, 3:00pm - 4:00pm
Track: DevOps and Agile
Successfully Applying Agile in Infrastructure
Robert Woods National Agile Practice Director, MATRIX Resourecs [email protected]
Session Description Infrastructure teams have seen the success (and failures) development teams have had using Agile. Perhaps they’ve even been told they’re going to be Agile. But the thing is, not every Agile framework fits every environment, and infrastructure can often struggle to see the benefits of applying Agile methods. This session shows how infrastructure teams can find the right Agile methods for their unique environments and enjoy the same successes seen in other parts of the organization.
Speaker Background Robert Woods has been in IT for twenty years, having started his career in infrastructure. He worked his way up from help desk support to senior systems engineer and eventually project manager in infrastructure. Since that time, Robert helped organizations apply Agile principles across multiple industries and is currently the southwest region lead for Agile transformations at MATRIX
Successfully Applying Agile in Infrastructure
Robert WoodsDirector National Agile Practice
Why has Agile seen so much success?
The 3 P’s of Successful
Agile Adoption(in order of importance)
People
Principles
Process
The People
The Principles
The Processes
Why is Agile so difficult to apply in Infrastructure?
The 3 P’s of unsuccessful
Agile Adoption(in order of perceived
importance)People
Principles
Process
Techniques for Successfully Applying Agile methods in Infrastructure
Principles
Process
People Agile People
o Start with a change in how we think about our work (Lean Principles)
o Train to Cater
o Break down knowledge silos (peer reviews, peer training, no SPoOF!)
o Create teams to swarm larger efforts
o Encourage innovation and technology growth
Principles
Process
People
Agile Principles
o Simplicity
o Retrospection
o Face to Face Communication
o Motivated Individuals (Leadership Principle)
o Value Delivered
o Work regularly with customers
o Sustainable Pace
o Technical Excellence
o Welcome Change
o Self-Organizing Teams
Principles
Process
People
Agile Processes
Why can’t Infrastructure be Scrummy like everyone else??
Transparency and Continuous Flow in a Pull System (Kanban\Scrumban)• Pull work across when
ready
• Slice where applicable
• WIP Limits
• Bottlenecks
• Maximize flow (Lean Manufacturing)
Design Build
Project Work
Reality Checks:
• Support Tickets
• Drive-By’s
• Crashes
• KTLO
• Documentation
1. Review time spent on non-project work in retrospect.
2. Create visibility to that work to eliminate surprises.
3. Plan for the unplannable.
4. Try to cut down on first in first out and focus on value delivered.
Measuring for Continual Improvement
Agile Infrastructure Metrics that Mean Something
• Uptime
• Cycle Time
• Lead Time
• Cost of Delay
• % of Project work vs KTLO
• Changability (how often are we asked to change course and do we)
• % work automated
• Technical Debt Remediation
• Improved Quality Statistics
Holistic Agile:Developing the Future Agile Company
Agile is no longer an IT thing
…never was.
Questions?
