2. - FW no longer a
bottleneck for the
business
- Development costs
reduced from
$100M/yr. to $55M/yr.
- ~140% increase in the
number of products
under development
- Capacity for innovation
increased from ~5% to
~40%
3. Requirements Scheduling Development
Integration &
Qualification
Waterfall Development Model
Resources
ScheduleScope
Waterfall Approach: Do
Enough up front planning
To lock in all three corners
4. Requirements Scheduling Development
Integration &
Qualification
Waterfall Development Model
Resources
ScheduleScope
Waterfall Approach: Do
Enough up front planning
To lock in all three corners
Waterfall Reality: Discoveries
during development and difficulties
with integration/qualification results
in frequent and costly schedule slips
5. Agile Development Model
Drops of working
Complete code on
A fixed interval
Plan
Qual Dev
Plan
Qual Dev
Plan
Qual Dev
Plan
Qual Dev
Drops of working
Complete code on
A fixed interval
• Fully qualified code drops on a fixed schedule
• Frequent small integrations
• Short planning and development cycles
• Delivering to a well prioritized product backlog
8. Transforming Traditional Enterprise Software
Development Processes
Enterprise Level
Continuous
Improvement
Planning &
Prioritized
Backlog
Applying DevOps
Principles at
Scale
Business
Objectives
9. Business Objectives (Don’t “Do Agile”)
Define
your value
proposition
Understand your
cost & cycle-time
drivers
Either automate, eliminate, or engineer out the
drivers that aren’t key to the value prop
10. Mini-milestone
Objectives
Cascading Objectives
to Track Progress
ConversationsLearnings
Agile Adjustments
Having real-time
metrics is essential for
the speed of agile &
aligning the org.
But don’t manage by
metrics.
Use the metrics to
understand where to
have conversations
about what is not
getting done.
Interative Approach to Agile Management
11.
12. Long Term Predictability for SW Schedules
Do we really need the predictability of our current planning processes?
Are our current planning processes really that accurate?
50% of all SW is never used or does not meet the business objectives!
100%
Accuracy
Planning Investment
13. One of the biggest challenges with
Agile Planning at the enterprise
level is getting the organization to
accept the uncertainty in SW
development and appreciate the
flexibility and opportunity.
14. Locking in Capacity over time
100%
Capacity
Time Horizon
Long-range commitments < ~50% of Capacity
Mid-range commitment < ~80%
of Capacity
Delivery
15. Transforming Traditional Enterprise Software
Development Processes
Enterprise Level
Continuous
Improvement
Planning &
Prioritized
Backlog
Applying DevOps
Principles at
Scale
Business
Objectives
16. Business Objectives
Increase the quality and frequency of feedback
Reduce the time and resources between release branch & production
Improve deployment repeatability/env. stability
Testing in an Operational like environment as close to dev. as possible
19. Ensuring the architecture/build system is ready
Comp A v1 Comp B v1
Comp D v1 Comp E v1 Comp F v1
Comp C v1Comp B v2Comp B v1Comp A v2
Comp D v2 Comp E v2
Comp C v2
Comp F v2
20. Automated system test architecture
• Component based approach to the automated test architecture
Data Magic
Navigation
Page Objects
28. CD - Picking the right tool for the job
Orchistrator
Trigger
Scripte
d
Env
Deploy
ment
EDD
Auto
Testing
29. Scripting Environments - Variances
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Common Script Common Script Common ScriptCommon Script
Environment descriptors
30. Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Comm
on
Script
Common ScriptCommon ScriptCommon Script
Environment descriptors
Deploy Workflow Complexity
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Comm
on
Script
Common ScriptCommon ScriptCommon Workflow
Environment descriptors
32. Finding the offending component quickly improves production
Configure Servers/Routing Device1:
Deploy Code2:
Run a System Test3: ? ? ? ? ? ? ? ? ? ? ? ?
33. Finding the offending component quickly improves production
Configure Servers/Routing
Device and Validate Data
1:
Deploy Code & Validate
Successful Deployment
2:
Run a System Test3: Code Validated
34. Transforming Traditional Enterprise
Software Development Processes
“Applying DevOps and Agile Principles at Scale
E-mail: gbgruver@gmail.com
Blog: largescaleagile.com
Twitter: @GRUVERGary
Notes de l'éditeur
These next two slides got dropped for some reason. I am okay with better slides but I need to keep the content
1Understand your value proposition
2-Define your cost drivers
Either automate or engineer out the drivers that aren’t focused on value prop
I added some text
I need to accuracy vs planning investment graph in here somehow.
I need to accuracy vs planning investment graph in here somehow.
A judo graphic would be nice if it work but I would understand if it does not work with the theme
I need to accuracy vs planning investment graph in here somehow.
Katie, can we put a slide here that has a bunch graphic type people where we are trying to find who committed the offending code. I have an idea that might work where we build with colors focusing it down to a smaller group of people and then one person. Start with a hole page of people colored when you are doing qrtly releases. Then focus CI and daily builds down to 5 and then 1 with the build process.
Hard to do testing on real product
Next best thing is an emulator, sometimes you are limited
So instead use a simulator on the servers….always fighting the battle to find the least expensive testing. But at the same time, you have to test across the pipeline. Is there a way to test in a cheaper, less expensive.