The Impact of DevOps on the Business Analyst · • Continuous integration and deployment processes...

© ASPE 2019 1

The Impact of DevOps on the Business Analyst

© A S P E 2 0 1 9

Michael Roberts

2

Age:

Location:

Occupation:

Company:Certifications:

44

North Carolina

Dir of Customer Engagement

ASPE, a Cprime Company

© A S P E 2 0 1 9

Who am I?

3

© A S P E 2 0 1 9

What we will discuss today…

Current state of most SDLC organizations

The challenges they face

What DevOps is and how it can be implemented

Applying the DevOps context to generic stakeholders as

described in the BABOK® Guide

Pain points and enablers of those roles

Real-Life BA Questions about DevOps

5

© A S P E 2 0 1 9

What are you here for?

6

I’m here to

learn about

Azure-

DevOps.

My company

is talking

about

DevOps.

I work with

dev teams

and I’m

interested.

© A S P E 2 0 1 9 7

Question?

Who has heard of Technical Debt?

Who has heard of Technical Equity?

© A S P E 2 0 1 9

What most orgs look like…

8

© A S P E 2 0 1 9

The Relationship between DevOps and… everything else

9

Business

Analysis

Step 1:Determine feasibility and

return on investment

The Idea

Idea:Idea generated by the

business unit or product

management

App Dev

Step 2:Requirements given to

App Dev group/team

QA & Testing

Step 3:App Dev gives code to

QA/Testing team/group

IT Ops

Step 5:IT Operations manages

the deployed code and the

infrastructure associated

with it

Release Mgmt

Step 4:QA gives to Release

group to deploy

Delivery

© A S P E 2 0 1 9

What it’s supposed to look like…

10

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

Product Yes

No

Yes

No

Yes: Production

Something

breaks: Revert

back

© A S P E 2 0 1 9

But there are problems…

11

Problems with handoffs

Business

Analysis

Step 1:Determine feasibility and

return on investment

The Idea

Idea:Idea generated by the

business unit or product

management

App Dev

Step 2:Requirements given to

App Dev group/team

QA & Testing

Step 3:App Dev gives code to

QA/Testing team/group

IT Ops

Step 5:IT Operations manages

the deployed code and the

infrastructure associated

with it

Release Mgmt

Step 4:QA gives to Release

group to deploy

One Major Problem: Snowflakes

13

Snowflakes in the Wild!

© ASPE, Inc. 14

New Code

Windows Server 2016 Std.

Windows Server 2016 Std.

Windows Server 2016 Data

Center Ed.

Win Update – 7.5.8



What solves this problem?

Configuration Management

A tenant of DevOps!

© A S P E 2 0 1 9

Manifestation of those problems…

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.

© A S P E 2 0 1 9

The Main Constituents in DevOps

16

Development IT Operations

© A S P E 2 0 1 9


17


1. Rewarded for creating value

when software is deployed.

2. Deploy frequently to delivery

value.

© A S P E 2 0 1 9


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

© A S P E 2 0 1 9

What is DevOps?

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

© A S P E 2 0 1 9

The DevOps Principles Mindset

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.”

24

CAMS • Culture

• Automation

• Measurement

• Sharing

© A S P E 2 0 1 9

DevOps Culture

• Inspiration was Agile.

• If they don’t communicate, collaborate and give feedback,

waste of time and effort.

• Common ground → Maximize customer value.

• Maximize Flow.

• Foster respect – Often referred to as “hugops.”

• Failure = Opportunity to improve ≠ Blame 25

CAMS

© A S P E 2 0 1 9

DevOps Automation

• Something that you’d otherwise do as hand. Example: deployment.

• “Lazy admin” – Make their own job easier, but not recognized as a valuable organizational feature.

• With scale, these items are important.• Dev side automation – unit testing, acceptance testing and CI. • Eliminate boundary between dev side automation and ops side

automation.

26

CAMS

© A S P E 2 0 1 9

DevOps Measurement

• “If you want to improve something, you have to be able to

measure it.”

• Normally Ops responsibility but Dev should be helping

capture things too.

• Export useful data and service features.

• “Feature release promises 2x faster load times”

27

CAMS

© A S P E 2 0 1 9

DevOps Sharing

• Aligning stakeholders – shared vision, current practices and

flows.

• Shared input, shared responsibility.

• Thoughts and opinions must be heard.

• Transparency – which is hard for some IT Ops folks.

28

CAMS

© A S P E 2 0 1 9

The DevOps Principles Mindset

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.

29

CALMS • Culture

• Automation

• Lean

• Measurement

• Sharing

© A S P E 2 0 1 9

Top Predictors Of IT Performance from 2014…

…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

31Source: Puppet Labs 2014 State Of DevOps

© ASPE 2019 32

“You build it,

you run it” -Werner Vogels

CTO, Amazon

© A S P E 2 0 1 9

What DevOps teams are asked to do

• Automate manual IT work

• Collaborate and share resources across IT departments

• Standardize and virtualize infrastructure assets (servers,

databases, test environments)

• Release software faster …much faster

• Empower developers to self-service and be responsible for

the performance of their own products

• Monitor and measure performance and health of systems and

software

• Capture feedback and continuously improve “the system”

33

© A S P E 2 0 1 9

Continuous… everything!

34

Building and testing every change you make to your system.

That requires working off of a shared trunk, not feature

branches.

Continuous Integration (CI)

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

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)

© A S P E 2 0 1 9

The deployment

pipeline concept

Source: Continuous Delivery:

Reliable Software Releases

through Build, Test, and

Deployment Automation

35

© A S P E 2 0 1 9

Amazon Deployment Stats

11.6 secondsMean time between deployments (weekdays)

1,079Max # of deployments in a single hour

10,000Mean # of hosts simultaneously receiving a deployment

30,000Max # of hosts simultaneously receiving a deployment

36Source: John Jenkins, Amazon.com

May 2011

© A S P E 2 0 1 9

Real Life Tool Chain

38

Plan &

ManageWork

Req.Mgmt

Release

AutomationArtifactMgmt

SourceMgmt

BuildMgmt

CodeQuality &

Review

DefectMgmt

Test Mgmt

CodeSecurity

Preferred Emerging

Plan Build DeployTest

Open Stack

Sonatype

Lifecycle

JenkinsJIRAGit

/StashSonar Fortify Quality Center Artifactory uDeploy

Crucible/

FisheyeConfluence

RDNG Veracode

Concourse

(for cloud)

Cloud

Formation

© A S P E 2 0 1 9

Tooling is important, but…

39

© A S P E 2 0 1 9

How does DevOps apply to BA?

40

?

© A S P E 2 0 1 9 41

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

And so does the BACCM™…Change

ValueWHAT

ChangeWHY

Value

42Source: IIBA Core Concept Model

© A S P E 2 0 1 9

There are 3 Requirement Levels…

43

“Business Requirements”/Objectives

Stakeholder/User Requirements

Solution Requirements

© A S P E 2 0 1 9

…multiple Requirement Types…

44Source: Why-What-How Consulting

Ho

wS

olu

tion

Wh

at

Sta

kehold

er/

use

rW

hy

Busin

ess

StaticBehavior

External

Interfaces

Functions

Design

Constraints

Quality

AttributesData

ProcessesBusiness

Rules

Solution Ideas

Objectives(SMART)

Scenarios

© A S P E 2 0 1 9

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

48

Software & System Architects

© A S P E 2 0 1 9

Stakeholder Help

49


• 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

© A S P E 2 0 1 9

Stakeholder Help

50


• 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

© A S P E 2 0 1 9


• 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

51

Software Testers

© A S P E 2 0 1 9


• 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

52

Change Managers

© A S P E 2 0 1 9

Some DevOps Questions from BAs

• What DevOps tools should every BA be using?

• How can BAs enable DevOps in their organization?

• Will DevOps be the end of BAs?

• Does the BABOK play nicely with DevOps principles?

• How Do BAs fit into DevOps?

54

© A S P E 2 0 1 9

“What do I need to learn?”

57

http://aspetraining.com/subjects/devops-training-courses

Use discount code PROGRESS

to enroll in Foundations of Agile

or Fundamentals of DevOps,

free of charge.

© A S P E 2 0 1 9 58

In conclusion…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.

© A S P E 2 0 1 9 60

Questions? & Thank you!

Michael Roberts(919) 816-1651

[email protected]

CONNECT WITH ME ON LINKEDIN!

The Impact of DevOps on the Business Analyst · • Continuous integration and deployment processes...

Documents

Transcript of The Impact of DevOps on the Business Analyst · • Continuous integration and deployment processes...