Get DevOstastic (The DevOps Transformation)

www.ranger4.com

DevOpstastic

Get DevOpstasticThe Ranger4 DevOps Transformation

Framework

www.ranger4.com

DevOpstastic

How Conflict Manifests

• Development feel it takes too long for IT Operations to provision new environments for them

• They may start asking for access to production systems

• When an outage occurs, fingers are pointed and a ‘blame game’ ensues – ‘war rooms’ are set up

• A single person may be lauded as a hero as he or she steps in at all hours to save the day (but is the only person with the knowledge to fix the situation)

• The first time an outage is reported is via a customer

• People are working much longer than contracted hours in attempt to get through an unplanned workload

www.ranger4.com

DevOpstastic

Shipping more, higher quality code to end users

faster through exceptional collaboration between

business and IT and within IT.

www.ranger4.com

DevOpstastic

Why now?

www.ranger4.com

DevOpstastic

Why a DTF

There is a need to define a process for embracing DevOps that is:

– Quantifiable and measurable– Structured and defined– Comprehensive and customizable

www.ranger4.com

DevOpstastic

Reasons to do DevOps

• Reduction in release/deployment time• Increase in volume of releases (ideally on demand)• Increase in software quality• Less time spent testing• Reduction in time spent resolving defects• Reduction in number of outages (ideally pre-empted)• Improved Mean Time To Recovery (ideally zero)• Reduction in technical debt• Delighted end users• Improvement in staff morale and associated productivity

boost• Applications monetizing earlier increasing income• A thriving business

www.ranger4.com

DevOpstastic

Three Core Parts

1 Culture

2 Interactions

3 Automation

www.ranger4.com

DevOpstastic

Step 1:Gain executive

sponsorship

www.ranger4.com

DevOpstastic

Step 2:Establish Project

Stakeholders

www.ranger4.com

DevOpstastic

DevOps Culture Looks Like:

• People recognise and believe they have a common purpose

• Work is conducted in a frictionless and transparent manner

• The focus is on the end-user experience

• Goals are visible and shared

www.ranger4.com

DevOpstastic

Part One: Culture

1. Identify and document high level business goals

2. Baseline metrics (survey)3. Identify desired future state4. Review DevOps teams patterns5. Plan and execute organizational change6. Define shared goals and publish7. Review rewards system8. Education and certification

www.ranger4.com

DevOpstastic

DevOps Teams: Anti-patterns

Type A: Separate Silos

Dev

Ops

With thanks to Matthew Skelton

www.ranger4.com

DevOpstastic

DevOps Teams: Anti-patterns

Type B: Separate DevOps Silo

Dev

Ops

With thanks to Matthew Skelton

DevOps

www.ranger4.com

DevOpstastic

DevOps Teams: Anti-patterns

Type C: “We don’t need Ops.”/NoOps

Dev

Ops

With thanks to Matthew Skelton

DevOps

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 1: Smooth Collaboration

Dev

Ops

With thanks to Matthew Skelton

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 2: Fully Embedded

Dev

Ops

With thanks to Matthew Skelton

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 3: Infrastructure as a Service

Dev

Ops

With thanks to Matthew Skelton

DevOps

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 4: DevOps as a Service

Dev

Ops

With thanks to Matthew Skelton

DevOps

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 5: Temporary DevOps

Dev

Ops

With thanks to Matthew Skelton

DevOps

www.ranger4.com

DevOpstastic

DevOps Teams: Patterns

Type 6: Enterprise DevOps

Dev

Ops

www.ranger4.com

DevOpstastic

Education and Certification

www.ranger4.com

DevOpstastic

Part 2: Interactions

• Requirements Management• Build and Configuration Management• Release and Deployment

Management• Testing• Application Performance

Management• Continuous Delivery Assessment

www.ranger4.com

DevOpstastic

Measure current maturity

www.ranger4.com

DevOpstastic

The DevOps Maturity Scale

1

5

4

3

2

Optimising DevOps

Managed DevOps

Starting DevOps

Fundamental DevOps

Not started DevOps

DevOps DONE – fine tuning and tied tightly to business goals.

Automated build, cross-functional teams, product-focused, cultural

change happening

Thinking about cultural change, starting to write scripts, looking at test

automation

Outages, war-rooms, blame, unplanned work, delays and defects.

Happy people with integrated toolchain to pre-empt failure, automate test and

deployment – Continuous Delivery

www.ranger4.com

DevOpstastic

Gartner CD Maturity Scale

www.ranger4.com

DevOpstastic

Requirements Management Maturity

Level 1 Level 2 Level 3 Level 4 Level 5Written Requirements

Organized Structured Traced Integrated

Documented and shared, regular collaboration between teams, backup and restore enabled

Formatted consistently, stored and secured. Version tracked and easily accessible to those with rights

Types (e.g. functional/non-functional) are specified. Attributes and prioritization is applied. Querying and filtering is possible.

Determine and track requirements relationships, has a hierachy of requirements: user needs, features and use cases. Coverage analysis reports implemented.

Requirements management fully integrated with software development environment: used directly in design, development, change tracking, testing and PM.

www.ranger4.com

DevOpstastic

Release and Deployment Management Maturity

Level 1 Level 2 Level 3 Level 4 Level 5Manual Packaged Scripted Complex On DemandBespoke, unpractised process. Authorization and sign off incidental. Roll back via back up copy or scripts.

Some packages (e.g. MSIs) and scripts. Release authorization considered.

Multiple scripts allowing automation. Can deploy to multiple parts of route to live. Possible roll back through redeployment. Some version control.

Can deploy composite applications. Role based security available. Multiple platforms services through single interface.

Push button deployments when code is ready – continuous delivery and deployment achieved. Full auditability and compliance.

www.ranger4.com

DevOpstastic

Identify Bottlenecks

www.ranger4.com

DevOpstastic

Collect Business Metrics

Metric Frequency

Current Target

Frequency of Release Per week 1 OnDemand

Frequency of Defect Per week 55 5

Frequency of Outage Per month 6 1

Elapsed Time to Release

Hours 27 1

Time to Resolve Defect Hours 3 0.2

MTTR Hours 6 0.1

www.ranger4.com

DevOpstastic

Write Business Case

www.ranger4.com

DevOpstastic

Part 3: Automation

www.ranger4.com

DevOpstastic

Pace Layers for DevOps

Systems of

Record

Systems of

Differentiation

Systemsof

Innovation

Traditional

Dev

Ops

Change

Governance

+

+

-

-

www.ranger4.com

DevOpstastic

Write Business Case

www.ranger4.com

DevOpstastic

What You Get in the DTF

• A workbook with clear activities and tasks

• Maturity models• Survey templates• Goal templates• Checklists• Business case templates• Project template

www.ranger4.com

DevOpstastic

Get DevOpstastic