Help people deliver software

just a little bit better

@DavidJWest | dwest@Tasktop.com

Sitting in the intersection of tools and process

For many DevOps is used to describe the process of release

automation. DevOps is the desire by development to use automation to

help build bridges with operations. Model driven deployment coupled

with improved reporting and transparency enables operations and

development to work together by providing a common language and

trusted set of techniques. But the promise of DevOps is so

much more than release, it should be about building a strong

set of working practices between operations and development that

foster trust and cooperation and in so doing so reduce waste

and increase value. Agile has provided a framework that allows

development teams to collaborate more effectively. Agile has changed

the lifecycle and practices development use. But can the Agile

lifecycle be employed across to operations, and what

would the broader lifecycle look like?

Microsoft approach

dev2Ops.org

IBM

HP

Lots of similar

yet different

points of view

An holistic approach to DevOps is required…

People

Collaboration

Measurement

Flow

Release

Automation

Virtualization

Architecture P

rocess

Classic Agile

Tasks /

Management

Operations

Scaled Agile

Release Automation Build Automation

Continuous Delivery Continuous Integration

Assets/

Automation

Portfolio

Mgt

Project

Mgt

Require

ments

Develop

ment Test

Operations

Portfolio

Mgt

Project

Mgt

Require

ments

Develop

ment Test

Operations

Team level

Scrum process

Traditional

planning and

release

approach

Lean Startup

Ideas

Many things but….

People work well

together when

they are working

off the same pile

of work…

After Integration

Test results are recorded in test tools

during test execution

• Spreadsheets used to communicate

defects to other groups

• Email and rekeying used to manage

defects in development

• Manual process for status report and

reporting

Defects flow into project

management, development and

requirements

• Work is allocated to the defects in

development

• Status is reported in project

management

• Status of requirements are

updated in requirements

Operations send email and update

spreadsheets for ticket information

• Spreadsheets are used for

ticket status reporting and

analytics

• Email used for high severity

defects and issues

• Information is aggregated

periodically to create total

quality metrics

Tickets / Problems flow seamlessly

into the Agile development process

• High importance tickets are moved

into sprints

• Status of applications is reported in

real time

• Project team and operations can

collaborate in context

Pattern Applies to Example

Example other patterns

Release Automation Build Automation

Linked

Automated

Automated

But can the Agile lifecycle be employed

across to operations, and what would

the broader lifecycle look like?