1

Continuous Delivery Best Practices for the Enterprise

April 30th, 9:00 am PST

2

Today’s Drive-In Guest Speaker – Steve LeWarne

Drive-In Guest Speaker

Steve LeWarne

Director, Solutions Architect

Serena Software, Inc.

Drive-In Host

Mark Levy

DevOps Evangelist

Serena Software, Inc.

@deparko

3

Continuous Delivery

“Building software so that it is in a state where it can always be put into production.”“Continuous Delivery” – Jez Humble and David Farley 2010

“Our highest priority is to satisfy the customer through early and continuous delivery

of valuable software.” Agile Manifesto – 1st of 12 principles - 2001

Not a “thing you do”, but rather a “state of being” achieved through:

• Requirements Management

• Continuous Integration

• Automated Testing

• Automated Deployments

• Configuration Management

• Automated Infrastructure Provisioning/Infrastructure as code, etc., etc.

4

1. The Culture (“Hacking Culture” – Jesse Robbins)

2. Enterprise Release Management

3. Large Number of Tools and Practices

4. Large and Complex Legacy Applications

5. Mainframe

6. Lack of Automated Testing

7. Lack of Automated Deployments

8. Limited/Shared Testing Environments

9. Tightly Coupled Release and Deployments

10. Multiple Different Pipelines

Enterprise Continuous Delivery “Top 10” Challenges

5

• Continuous Delivery for an Team/Application:

• Typically driven by single department/line-of-business (LOB) manager or executive

• Consistent toolset

• Agile is the prevalent methodology

• Regulatory/compliance concerns are minimal

• Focus is on delivering artifacts to production

• Multiple commercial CD “Framework” products are available

• Continuous Delivery for the Enterprise

• Usually involves multiple silos/LOBs within the organization

• Understanding and support at senior executive level is inconsistent/immature

• Wide variety of competitive tools in use.

• Mix of waterfall, iterative, and agile methodologies

• Regulatory/compliance concerns are high

• Delivering artifacts to production is important, but adherence to process is paramount.

• Limited selection of commercial tools to address typical challenges

“Enterprise” Continuous Delivery

6

Enterprise Continuous Delivery Scenarios

Dev Integration Test Production

Quality/Release Mgmt/

Shared Services

• Standard quality tools

• No standard process/

visibility tool

• No standard deploy

tool

Operations

• Leverages operations

automation tools

• May only manage

infrastructure, not

deployments

Quality/Release

becomes bottleneck to CD

Team-1: Dev team is “achieving CD”

Team-3: Dev team is “achieving CD”

Team-2: Dev team is waterfall

Manual

Deploy

7

Where to Start?

Continuous Delivery for at the Enterprise Level?

Continuous Delivery for a Team/LOB?Continuous Delivery for a Team/LOB?Continuous Delivery for a Team/LOB?

88

How to Start – The Mantra

• What matters to the business?

• Define and measure success

• See the system

• Eliminate waste

• Incremental changes/quick wins

• Focus on continuous improvement

• Ask for help

9

How Responsive are you to the Business?

• How do you measure success?

• Average cycle time for moving a business request from Development to Production?

• Number of business requests implements this week, month, year?

• Cost of moving a unit of change through your application lifecycle?

• Percentage of a release focused on technical debt?

• Develop metrics to support what matters to the business

1010

Automate Almost Everything

• People should not move the “bits”

• Automate code and configuration deployments with a single set of

deployment processes across all environments

• All pre-prod deployments should be rehearsals for the final deploy into prod

• Quick incremental wins with big impact

1111

Orchestrate the Release ProcessStreamline and accelerate the release lifecycle

• Single system of record for release planning and execution

– Schedules

– Milestones

– Gates and Approvals

• Automatic cycle-time capture

• Ensure audit trails for compliance and learning

12

Quality/Release Management

Enterprise Example - Before

Distributed Development

Production Change Control

(ITSM)

24 Tools/Methods

• Leveraged Development Change and Deploy Tools

• Email/Spreadsheet tracking

• Lack of “Enterprise” Visibility

• Audit compliance was a major challenge.

Manual Entry/Approval

Dev Integration Test Production

1 Tool/Method

Mainframe DevelopmentMainframe Development • (Select) Mainframe users had permissions to deploy.

• Manual/error-prone deployments

13

Quality/Release Management

Enterprise Example – Future State

Distributed Development

Production Change Control

(ITSM)

24 Tools/Methods

Dev Integration Test Production

1 Tool/Method

Mainframe DevelopmentMainframe Development

Release Control

Mainframe Development

Deployment Automation

14

• Are you targeting Team/App CD, or Enterprise CD?

• Talk to the business, agree on what success means

• Automate your deployments

• Automate and control your release process (governance/compliance)

• Incremental changes are key

• Culture change takes time, focus on quick wins in order to speed change.

• Serena can help.

Contact your Account Manager or slewarne@serena.com to get started.

Summary

15

Questions?

Please use the Q&A panel to submit your questions

Hidden Costs

of Open Source

Software

New Whitepaper Deployment Automation

Get the

Community

Version

SDA Mobile App

16

Want to See More?

16

serena.com/sda

17

Thank you!