3. NATIONWIDE IT
#51: COMPUTERWORLD BEST
PLACES TO WORK IN IT
200 AGILE / LEAN
STANDING TEAMS >2500 APPLICATIONS
23
BUSINESS UNITS
5100 IT ASSOCIATES
OF
AND
BALANCE
INNOVATION
DISCIPLINE DEVELOPERS & TESTERS
>2600
50PRIMARY
TECHNOLOGIES
4. 4
ORGANIZATIONAL STRUCTURE
I & O
Cindy
Nationwide IT
Jim
Tools
Run
Platform
Enterprise Applications
Nationwide Financial
Business UnitsShared Services
5. 5
10 YEARS AGO, WE SET OUT TO BUILD A GLOBALLY COMPETITIVE
IN-HOUSE SOFTWARE DEVELOPMENT CAPABILITY
AGILE DEVOPS LEAN CMMI
How we deliver
software with
high quality
How we deliver
with speed,
efficiency, and
low risk
How we
manage IT at
enterprise
scale
How we provide
industry
validation of our
progress
WHERE WE STARTED
6. 6
WHERE WE STARTED
AGILE DEVOPS LEAN CMMI
DevOps house
Methodology
Deployment tooling
Practices
Simplify
Organize
Experiment
Motivate
Tool adoption
Continuous improvement
Self-service
Immersive pairing
Availability (SRE)
Pipeline as a product
• Architecture
• Ownership
• Prioritization
• Funding model
Model lines: speed,
practitioner led
Business planning: Minimum
Marketable Product (MMP),
single embedded owner
Infrastructure engineering
Developer experience
DevOps Handbook
Senior leadership
sponsorship
IT Delivery Model
transformation
• Software development
model
• Lean management
• Suppliers
2015 2016 2017 2018
12. Introduced lead time metrics for
all 200 development teams
Empower teams to pick their
course guided by lead time
Drive towards daily, zero
downtime deployments
THE NORTH STAR –
LEAD TIME
14. Development teams must make
their own journey
Tech Consulting and DevOps
leaders are expert climbers
Cross-pollinate
Support the Delivery Pipeline as
a single product
SUPPORT MODEL
SHERPAs
• Tech Consulting
• Build Capability SMEs
COMING SOON
• Immersive Pairing
• Monthly DevOps Dojo
• Delivery Pipeline Support
15. High volume of flooded cars
Business ask: optimize online
claims process
IT response: collaborative
design and implementation in 8
hours
Results: streamlined online
claims process by 40%
HURRICANE HARVEY
16. WE STILL NEED HELP
Leader Experience
Matrixed Org Model
Value Stream
Architecture
Jim
2016 – harvest efficiencies to invest in capabilities
Talk about guiding principles
2017 – we’ll spend the rest of the talk here
Jim
Systems thinking
PDCA
Cindy
Team gave ideas for speed. Grounded ideas in Handbook. Team read book and found new experiments.
Results (to date) include:
- significant reduction in lead time (over 60%)
- increased frequency in deployment
- significant reduction in time to run automated tests (20X factor)
- integrating security and performance testing into CI/CD flow
- reduction of manual activities, waste and wait states
Cindy
Cindy
Jim
Help excitement
Self-service
1-pager
Mountain as a metaphor – we can’t climb for you
Jim
Lead time is our north star because we were able to easily measure it
Jim
Talk about Rocket.Chat
Jim
Immersive Pairing – committed to being practioner led. Adoption should be the same way
Cindy
Business Need
Hurricane Harvey represented a change in business conditions, as what is normally a wind event became a flooding event. Our online Claims work flow was not optimized for Auto flood claims because those aren’t typically a high volume scenario. As a result, our Executive Business leaders requested the IT team to find a way to increase the efficiency of our Claims Self-Service web site so that our Members would be able to create these types of claims more quickly.
Actions
Collaborative approach, design, Github, RocketChat, Modern Web Architecture, automation testing to quickly certify, autonomy of the team, Zero Downtime process, Splunk dashboard.
Outcome
After receiving the request at 10:00 am, the IT team was able to make changes in production by 6:00 pm on the same day. The creative ideas from the team eliminated 40% of the web pages needed to create an Auto Claim and improved the messaging to our Members on the ways in which Nationwide is here to serve them in their time of need.
Cindy
We recognized how even the best tools for developers need automation and integration to prevent context switching and to get the most value. Leaders deserve the same. Monthly ops review culture. Leaders are not prioritizing a data and decision making dashboard and automation for themselves. Still in the “newspaper business”.
Are we optimizing for speed or are we meeting a IT staff efficiency need. They side effects to the whole value stream are often negatively and significantly effective. Vertical overwhelms horizontal in Model 2. If you have 2, you have to invest in horizontal. Overengineer towards horizontal. Value stream architecture (vs functional architecture). Not a lot of examples of success in industry. Unicorns are in model 3. Legacy enterprises start in 1. Who has successfully done it. How did they do it?
Influencers: Mark Schwartz’s book about you cannot run a business without IT. IT leaders have needed to earn a seat at the table. But now, all business leaders will be IT leaders.