As much as development and operations communities are embracing DevOps best practices some are missing something critical - the people ! While taking a renewed look at our tools to mature deployment pipelines and leverage automation, it’s the integration of the functional disciplines or more specifically teams that requires the most attention to establish and sustain success. Sponsored by SAIC.
9. SAIC.com
P U B L I C S E C T O R
S U M M I T
Company Information
9
• SAIC® is a premier technology integrator solving our
nation's most complex challenges across the defense,
space, federal civilian, and intelligence markets. Our
offerings include high-end solutions in systems
engineering and integration and enterprise IT.
• Headquartered in Reston, Virginia, SAIC has approximately
23,000 employees (post Engility acquisition) and annual
revenues of about $6.5 billion. SAIC’s office facilities are
located to support its diversified workforce in the
domestic and global markets.
10. SAIC.com
P U B L I C S E C T O R
S U M M I T
Services , outcomes, and XLAs
10
The traditional measurement of service and outcomes is
changing
11. SAIC.com
P U B L I C S E C T O R
S U M M I T
Our First DevOps Steps
11
Building up to a bad conclusion is no longer an option
12. SAIC.com
P U B L I C S E C T O R
S U M M I T
Go Faster Be Stable
12
Agile Development ITIL Service Management
….and what about Security ?
Non-systems thinking gave rise to methods of management that enforced
silos
13. SAIC.com
P U B L I C S E C T O R
S U M M I T
The Result: Impedance Mismatch
13
Cultural impedance/ Technical Impedance
14. SAIC.com
P U B L I C S E C T O R
S U M M I T
Corollary 1: It’s about the business
14
It’s not about you, your team, or your tools
15. SAIC.com
P U B L I C S E C T O R
S U M M I T
Corollary 2: Value is Subjective
15
Lies, damned lies, and statistics (metrics) – S. Clemens
16. SAIC.com
P U B L I C S E C T O R
S U M M I T
Corollary 3: Culture Trumps Strategy
16
Good luck with that !
17. SAIC.com
P U B L I C S E C T O R
S U M M I T
Technology: A value multiplier or sore multiplier
17
The pace of change demands iterative delivery in software, infrastructure, AND services
18. SAIC.com
P U B L I C S E C T O R
S U M M I T
SAIC’s DevOps Philosophy
18
DevOps is a cultural and professional movement that extends Agile, Lean, and ITSM principles to accelerate the
delivery of value via software and infrastructure changes by emphasizing collaboration and communication
between development and IT operations, business owners, and users. – ITSM Academy www.itsmacademy.com
Key Principles:
• Build cohesive teams: encourage cross domain participation
and collaboration from business, users, software
developers, and other IT professionals.
• Optimize / Automate Everything: use automating tools and
techniques to build in consistency, reliability, and efficiency
in the software release process. Treat infrastructure as code.
• Institute strong source control practices: source control
application code, configuration items, and infrastructure.
• Test early and often: automate code testing as it is checked
and include environment configuration and infrastructure.
• Improve continuously: teams must invest time evaluating
and improving their software lifecycle process.
• DevSecOps: Security at design and throughout delivery.
Software developers, and other IT professionals build in and
test security compliance at every stage of the software
lifecycle. Incorporates automate compliance controls.
DevOps
Principles
Continuous
Integration /
Delivery
Operations
Infrastructure
as Code
DevSecOps
Continuous
Testing • Monitoring /
Performance
feedback
• Automated event
recovery
• Automated security
compliance
DevOps Main Components
• Infrastructure
provisioned and
managed as code
• Monitor and enforce
compliance dynamically
• Developers continuously check
in code to central repository
• Automated build process
• Deployment pipelines integrated
for warranty and utility
• All code changes are
automatically built, tested, and
prepared for production release
• Produce deployment artifacts
• Central repository for code,
configuration items, and
infrastructure build scripts
CALMS - Culture, Automation, Lean, Measurement, Sharing
19. SAIC.com
P U B L I C S E C T O R
S U M M I T
Enabling and Complementary
But where to start ?
19
20. SAIC.com
P U B L I C S E C T O R
S U M M I T
Tailored delivery based on best practices
20
Infrastructure/Platform/SW as a Service (App Dev, monitor, deploy,
scale)
Stage Deploy
PracticesProcessesTeams
Continuous Integration
Continuous Testing
• Project set up –
• Concept, Discovery,
Infrastructure
• Architecture epics
• Business epics
• Build Teams
• Prepare initial
groomed product
backlog –
(estimated story
points and
prioritized)
• Create Release
Roadmap (release
planning)
• PM/ScrumMaster/BAs/PO
• Tech/Dev Lead
• Architecture (EA/Business)
• Security / Operations /Prod
Support
Plan
Dev Environment Staging Production
Environment
Test/QA
Scrum
master IT Ops IT Ops
Continuous Delivery
Operate
Continuous Monitoring
Test
Develop Build Test
Development
teams
Product Owner
Conduct Sprint Planning & Establish Sprint Backlog
Elaborate Architecture & Design
Develop, Unit Test, Peer Review & Document
Conduct Continuous Integration Testing
Review, Demo, & Conduct Sprint Retrospective
Performance Testing
Acceptance Testing
Document & Training
Package and Release,
etc.
Operations & Sustainment
Performance & Reporting
Service Desk & Problem
Reporting
Continuous Improvement
Deploy Release
Conduct Post-
deployment
User Training
Agile Sprints
Development
teams
DevSecOps
Feedback
Optimization / Automatin
A target rich environment
21. SAIC.com
P U B L I C S E C T O R
S U M M I T
Lifecycle Integration
21
Seek relationships and develop an ecosystem that fits your
requirements and the business, not your vendors. DevOps toolchains
are based on their requirements and fit for purpose.
Tooling enables and constrains, depending on their application
22. SAIC.com
P U B L I C S E C T O R
S U M M I T
Implementing DevOps Smartly
22
• Have a clear plan - ( An organizational plan) CULTURE
• Stakeholder participation
• Full involvement internally and externally ( Get people trained / on the same page)
• Start inside and work outside (cup of coffee)
• Use the Seven Step Continual Service Improvement process or PDCA
• Examine internal processes (apply Lean)
• Evaluate the full business value stream (Theory of constraints)
• Establish common processes, models, and tool chains
• Assess results, Share experiences
• Sustain the momentum / Promote Collaboration
“Maximize the velocity to value to the end user with improved volume of quality services”