Welcome.

Introduction to DevOps for Business Analysts Chris Knotts, PMP – ASPE Training and Techtown Training

I’ll discuss…

• A little about DevOps • A few examples of generic stakeholders as

described in the BABOK® Guide • Applying the DevOps context to stakeholder

roles • Pain points and enablers of roles associated

with successful DevOps style work

A few assumptions for the hour…

• Roles are associated usually with software projects, & always with overall IT workflow

• DevOps is not a codified set of principles

• Chris is not a BA

• BABOK® Guide 2.0 vs. 3.0 - ?

DevOps & Business Analysts – We will discuss:

• Level-set: “What is DevOps?”

• A typical enterprise environment and the life cycle of IT and software delivery projects

• Agility: the bridge to DevOps

• Continuous delivery and incremental workflows

• Major implications for IT project mangers

What is DevOps?

Source: www.devopsdays.com

Attribute Key Elements

High-trust, high- performance culture IT capabilities = strategic assets, not cost centers Highly automated processes; mature deployment pipeline Continuous delivery of software and IT value Commitment to continuous learning & improvement

Unified mission; aligned incentives across departments and teams; little fear/failure/blame, high quality of work life Projects, features and work flow through fast cycles times, systems are “anti-fragile,” IT processes & capabilities are aligned with overarching organizational needs Technical phases of projects supported by common tools and automation processes, collaboration replaces handoffs, codebase/IT infrastructure is agile and functional by default Features, projects and IT work follow a regular, iterative flow. Cycle time is short, workflow favors small frequent changes Disciplined feedback loops quickly travel back upstream for inclusion. Tools for monitoring, measurement and alerting implemented & effective. Shared knowledge repositories.

DevOps IS…

A simplified look at Consolidata’s enterprise

s

S e c u r I t y, G o v e r n a n c e S e c u r I t y, G o v e r n a n c e

Business Customer

Application

Development teams IT Operations, Production

Environments, Support

Change Management

A simplified look at the enterprise

Dev

Ops

Opposing missions

• Development teams rewarded for creating value when software is deployed

• Operations and infrastructure admin

teams penalized for downtime

Success!!

Working software or

feature DELIVERED

Sprints

Idea

The triumphant Agile team!

Opposing missions The triumphant Agile team!

Deploy & Support

Data

Security

Operation

& Systems

IT Operations

The triumphant Agile team!

Data

Security

Operation

& Systems

IT Operations

The business! (different departments, needs, stakeholders etc.)

Deploy & Support

The triumphant Agile team!

Data

Security

Operation

& Systems

IT Operations!!

The business! (different departments, needs, stakeholders etc.)

Customers / end users!!

Deploy & Support

1. Without a common goal, you will never achieve 2. Commit to values first…the practices will follow 3. Implementing DevOps (or any new way or work) is about

LEARNING…not getting it perfect 4. Agile practices allow adaptability and predictability 5. Articulate a vision and get buy in from your internal

customers 6. Find the MINIMUM requirements for a solution! 7. Optimize the whole! Limit work in progress (WIP)

anywhere possible 8. Build great teams

Lessons from Agile

Every member of a cross-functional team is responsible for the delivery process.

• One of the most important goals of a continuous delivery environment is to attach responsibility for the successful deployment of a piece of code (be it software features or infrastructure code) to the person who developed it

• Everyone is responsible for quality!

• When something is wrong (an outage, a broken build, a bug) the entire team’s priority becomes fixing it

• Let’s discuss how this works in the context of continuous integration and continuous delivery

Application Delivery & Cost of Defects

50% of defects introduced here

What are organizations trying to achieve with

DevOps type practices?

A simplified look at the enterprise A simplified look at an enterprise Welcome to the 21st century!

The deployment pipeline concept

Source: Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation

Continuous Delivery: Smaller batches of software work, more frequently, with less planning and more adaptability

BABOK® Guide 1.5.6

Generic Stakeholder Examples and Alternate Roles

Business Analyst Business Systems Analyst, Systems Analyst, Process Analyst, Consultant, Product Owner

Customer Segmented by market, geography, industry

Domain SME Broken out by organizational unit, job role

Implementation SME Project Librarian, Change Manager, Configuration Manager, Solution Architect, Developer, DBA, Information Architect, Usability Analyst, Trainer, Organizational Change Consultant

Operational Support Help Desk, Network Technicians, Release Manager

Project Manager Scrum Master, Team Leader

Supplier Providers, Consultants, etc.

Tester Quality Assurance Analyst

Regulator Government, Regulatory Bodies, Auditors

Sponsor Managers, Executives, Product Managers, Process Owners

Examples of generic stakeholders

Implementation SMEs • Developers/Software Engineers • Organizational Change Managers • System Architects • Usability Professionals

Project Manager Testers Regulators Sponsors Suppliers

BABOK® Guide 1.5.6

Generic Stakeholder Examples and Alternate Roles

Business Analyst Business Systems Analyst, Systems Analyst, Process Analyst, Consultant, Product Owner

Customer Segmented by market, geography, industry

Domain SME Broken out by organizational unit, job role

Implementation SME Project Librarian, Change Manager, Configuration Manager, Solution Architect, Developer, DBA, Information Architect, Usability Analyst, Trainer, Organizational Change Consultant

Operational Support Help Desk, Network Technicians, Release Manager

Project Manager Scrum Master, Team Leader

Supplier Providers, Consultants, etc.

Tester Quality Assurance Analyst

Regulator Government, Regulatory Bodies, Auditors

Sponsor Managers, Executives, Product Managers, Process Owners

Five of the most important roles impacted by DevOps trends

• Software & Enterprise Architects • Software Developers • IT Operations & Support • Software Testers • Change Managers • Anyone with a stake in application

outcomes!

Software & System Architects

A few typical challenges: • Legacy Technology • Mission Criticality • Technical Debt

DevOps-associated Enablers:

• Service Oriented Architecture • Component-Centric Design • Loose Coupling of Components • Simulators and Emulators

Software Developers A few typical challenges: • Definition of done • Agile Practices that end with dev teams • Long, or absent feedback loops • Measurement of enterprise value

DevOps-associated Enablers:

• Agile Practices… but they must scale! • “Deploy it yourself” with operational support • Treating infrastructure as code • Continuous delivery of software

IT Operations & Support

A few typical challenges: • Blame from all sides • Most enterprises engineered to penalize • Not responsible for most defects & failures

DevOps-associated Enablers:

• Peer-driven change management • Inclusion & collaboration early in projects • Technology enablers (automation tools, etc.)

Software Testers

A few typical challenges: • Accurate testing • Fast enough testing • People ignoring test results

DevOps-associated Enablers:

• Designing tests as part of the product • Component oriented testing • Using tests to automate deployment • Making quality everyone’s responsibility

Change Managers

A few typical challenges: • Imposed change management • Slow delivery of value • Lack of leadership support • Inefficiencies arising from fearful culture

DevOps-associated Enablers:

• Peer-driven change management • Engineering change as the “product” • Leadership-driven change

To sum up:

• Stakeholders are oriented around teams and projects

• Quality is tied to value – and is everyone’s responsibility, from requirements and code creation to deployment

• Technical non-functional requirements (and technical debt) receive equal priority to functional requirements

• Deliver often, deliver early, learn and adapt. Roll planning into your continuous processes

• Testing and QA is not a separate function: it is a key enabler of continuous delivery

• Expect failure and plan for the contingency

References & recommended reading

• Continuous Delivery, Jez Humble and David

Farley

• Leading the Transformation: Applying Agile

and DevOps Principles at Scale, Gary Gruver

and Tommy Mouser

• The Phoenix Project: A Novel About IT,

DevOps & Helping Your Business Win, Gene

Kim, George Spafford, Kevin Behr

Thank you!

www.aspe-sdlc.com www.techtowntraining.com