the impact of devops on the business analyst · 1. devops requires a high trust culture, despite...

© ASPE, Inc. 1

The Impact of DevOps on the Business Analyst

Who am I?

© ASPE, Inc. 2

What we will discuss today…

© ASPE, Inc. 3

1. Current state of most organizations

2. What DevOps is and how it can be implemented

3. A few examples of generic stakeholders as described in the

BABOK® Guide

4. Applying the DevOps context to stakeholder roles

5. Pain points and enablers of roles associated with successful

DevOps style work

What are you here for?

© ASPE, Inc. 4

Remember these for this hour…

© ASPE, Inc. 5

• Roles are associated usually with software projects, & always

with overall IT workflow

• DevOps is NOT a codified set of principles like the BABOK®

Guide

Question?

© ASPE, Inc. 6

Who has heard of Technical Debt?

Who has heard of Technical Equity?

Current State

Here’s what most organizations look like

© ASPE, Inc. 7

The Common Vocabulary

© ASPE, Inc. 8

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

The Relationship between DevOps and… everything else

© ASPE, Inc. 9

Idea brought to the Business

Analysis group/team

STEP 1App Dev gives code to

QA/Testing team/group

STEP 3IT Operations manages the

deployed code and manages

infrastructure associated with

it.

STEP 5

Requirements given to App

Dev group/team

STEP 2QA gives to Release group

to deploy

STEP 4

Idea generated by the

business or product owner

IDEA

Business

AnalysisApp Dev

QA &

Testing

Release

MgmtIT Ops

Delivery

Business

Customer

Application Development

Teams

Security, Governance

IT Operations, Production

Environments, Support

Simplified Enterprise

© ASPE, Inc. 10

Change Management

What it’s supposed to look like…

© ASPE, Inc. 11

Dev Team Fast, early testing Larger, more complex tests Release

Product Yes

No

Yes

No

Yes: Production

Something

breaks: Revert

back

But there are problems…

© ASPE, Inc. 12

Idea brought to the Business

Analysis group/team

STEP 1App Dev gives code to

QA/Testing team/group

STEP 3IT Operations manages the

deployed code and manages

infrastructure associated with it.

STEP 5

Requirements given to App Dev

group/team

STEP 2QA gives to Release group to

deploy

STEP 4

Idea generated by the

business or product owner

IDEA

Business

AnalysisApp Dev

QA &

Testing

Release

MgmtIT Ops

The problem is snowflakes

© ASPE, Inc. 14

Manifestation of those problems…

© ASPE, Inc. 15

We need to

get software

releases out

faster.

IT Ops having

a hard time

keeping up

with Agile

teams.

CIO wants

push-button

deployments.

New tools

being used

but not

seeing the

benefits.We don’t

understand

tools to help

us manage

and deploy.Our production

environment

isn’t all the

same.

Unsure of

what DevOps

is and how it

pertains to

us.

We want to

understand how

to manage our

infrastructure

better.

We aren’t

allowed to

deploy more

than once a

month.

Our

deployments

are always

painful.

All

deployments

cause

multiple

issues.

The Main Constituents in DevOps

© ASPE, Inc. 16

Development IT Operations


© ASPE, Inc. 17


1. Rewarded for creating value

when software is deployed.

2. Deploy frequently to delivery

value.


© ASPE, Inc. 18


1. Rewarded for creating value

when software is deployed.

2. Deploy frequently to delivery

value.

1. Penalized for downtime.

2. Rewarded/bonused for

uptime.

3. Don’t change anything on

the system.

© ASPE, Inc. 19

IT Ops

Dev Teams

What is DevOps?

And how does it apply to me in a Business Analyst role?

© ASPE, Inc. 21

What are organizations trying to achieve with DevOps type practices?

© ASPE, Inc. 22

Smaller batches of software work,

deployed more frequently,

with less planning and

more adaptability

by people working better together.

The Goal of DevOps

© ASPE, Inc. 23

The DevOps Principles Mindset

© ASPE, Inc. 24

CAMS

The fundamental principles of DevOps as generally agreed upon by the

most influential early members of the DevOps community, were summed up

in the acronym “CAMS.”

• Culture

• Automation

• Measurement

• Sharing

The DevOps Principles Mindset

© ASPE, Inc. 25

CALMS• Culture

• Automation

• Lean

• Measurement

• Sharing

Jez Humble, a notably influential and early DevOps leader,

later suggested adding an “L” to the acronym, changing it

to “CALMS.” This was enthusiastically accepted and

widely endorsed.

DevOps Culture

© ASPE, Inc. 26

Collaboration, sharing, and visibility

Cross-functional teams

Automation that changes people’s jobs

New processes & work relationships

Everyone focused on Quality & Small batches and continuous processes improvement

Failure = Opportunity to improve ≠ Blame

DevOps pushes us toward a culture of:

Top Predictors Of IT Performance from 2014…

© ASPE, Inc. 27Source: Puppet Labs 2014 State Of DevOps

…that are still true today.

• Version control of all production artifacts

• Continuous integration and deployment

processes

• Automated acceptance testing

• Peer-review of production changes (vs. external

change approval)

• High trust culture

• Proactive monitoring of the production

environment

• Win-win relationship between Dev and Ops

Continuous… everything!

© ASPE, Inc. 28

When the CI build passes, it just automatically deploys to

production (or there are some other validations/performance

tests, etc). This should happen several times a day at least.

Continuous Deployment

Building and testing every change you make to your system.

That requires working off of a shared trunk, not feature

branches.

Continuous Integration (CI)

Behaving as if you were going to do Continuous Deployment,

but not actually deploying all those builds. Happens in

industries/products where it doesn't always make sense to do

that (firmware or mobile apps for example)

Continuous Delivery (CD)

The deployment

pipeline concept

Source: Continuous Delivery:

Reliable Software Releases

through Build, Test, and

Deployment Automation

© ASPE, Inc. 29

Monitoring

Code Security

Plan Code

PPMSource Code Mgmt

Build Test OperationalRelease

<COMPANY> DevOps Tools

Unit Test

System TestSpritz

Environment Provisioning

& Infrastructure as Code

Configuration Mgmt Tool(Selection in progress)

Data Masking

Code Quality

Continuous Deployment

Acceptance Test (Stage)

Deployment

Continuous Integration

CI Tool

for Salesforce

Artifact Mgmt

MS PowerShell

ALM

for Salesforce

Build Automation

Integration

ALM

Application Monitoring

Real Life Tool Chain

© ASPE, Inc. 30

Amazon Deployment Stats

© ASPE, Inc. 31Source: John Jenkins, Amazon.com

11.6 seconds

Mean time between deployments (weekdays)

1,079

Max # of deployments in a single hour

10,000

Mean # of hosts simultaneously receiving a deployment

30,000

Max # of hosts simultaneously receiving a deployment

May 2011

BABOK® Knowledge Areas still apply…

Business Analysis

Planning and

Monitoring

Strategy Analysis

Requirements

Analysis and

Design Definition

Solution

Evaluation

Elicitation and

Collaboration

Requirements Life

Cycle

Management

Refers to BABOK Guide v3, Figure 1.4.1, Page 5 32

And so does the BACCM™…Change

ValueWHAT

ChangeWHY

Value

33Source: IIBA Core Concept Model

There are 3 Requirement Levels…

“Business Requirements”/Objectives

Stakeholder/User Requirements

Solution Requirements

34

…multiple Requirement Types…

Source: Why-What-How Consulting

Ho

w

Solu

tion

Wh

at

Sta

keh

old

er/

user

Wh

y

Busin

ess

StaticBehavior

External

Interfaces

Functions

Design

Constraints

Quality

AttributesData

ProcessesBusiness

Rules

Solution Ideas

Objectives(SMART)

Scenarios

35

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

Stakeholder Help

© ASPE, Inc. 37

Software & System Architects

Stakeholder Help

© ASPE, Inc. 38


• Definition of done

• Agile Practices that end with dev teams

• Long, or absent feedback loops

• Measurement of enterprise value


• Agile Practices… but they must scale!

• “Deploy it yourself” with operational support

• Treating infrastructure as code

• Continuous delivery of software

Software Developers

Stakeholder Help

© ASPE, Inc. 39


• Blame from all sides

• Usually viewed as a cost center

• Most enterprises engineered to penalize

• Not responsible for most defects & failures


• IT as a major producer of value

• Peer-driven change management

• Inclusion & collaboration early in projects

• Technology enablers (automation tools, etc.)

IT Operations & Support


• Accurate testing

• Fast enough…or simply enough…testing

• People ignoring test results


• Designing tests as part of the product (TDD)

• Component oriented testing

• Using tests to automate deployment

• Making quality everyone’s responsibility

Stakeholder Help

© ASPE, Inc. 40

Software Testers


• Change management imposed from outside

the work center / CAB boards

• Slow delivery of value

• Lack of leadership support

• Inefficiencies arising from fearful culture


• Peer-driven change management

• Engineering change as a “product”

• Automating/mechanizing change (and thus

auditability & compliance)

• Leadership-driven change

Stakeholder Help

© ASPE, Inc. 41

Change Managers

In conclusion…

© ASPE, Inc. 43

1. DevOps requires a high trust culture, despite conflicting motivators for

Development and Operations teams.

2. Success with DevOps is contingent on your CI/CD implementation.

3. Automation is A component, not the ONLY component of DevOps.

4. Stakeholders will need support during a transformation to DevOps.

the impact of devops on the business analyst · 1. devops requires a high trust culture, despite...

Documents