www.ranger4.com

DevOpstastic

Optimising DevOps

OnDemand Application Deployments

Mark Roberts, IT Specialist, IBM

www.ranger4.com

DevOpstastic

Let’s Think About…

• From continuous integration to continuous delivery

• Supporting the software delivery lifecycle• Continuous delivery demonstration• UrbanCode Deploy user experience• The investment case for UrbanCode Deploy

www.ranger4.com

DevOpstastic

41%experience development

delays

34%experience deployment

delays

45%experience production

delays

4-6 weeksto deliver

codechanges

Operations/Production

Development/TestCustomers

BusinessOwners

Costly, error prone manual processes and efforts

to deliver software across an enterprise

CHALLENGES

Upgrade risk due to managing multiple application configurations

and versions across servers

Slow deployment to development and test environments leave teams

waiting and unproductive

The impact of a lack of continuous delivery

www.ranger4.com

DevOpstastic

Customers

Desire for fast and continuous innovation

Line of Business

Requirements

Dev & Test Teams

Code & Tests

Operations Team

Business Services

1st Gap

2nd Gap

Delivery Challenges

Today’s business and technical needs are pushing traditional delivery approaches to the breaking point

People

Process

Information

www.ranger4.com

DevOpstastic

Across the software development lifecycle

www.ranger4.com

DevOpstastic

Across the software development lifecycle

www.ranger4.com

DevOpstastic

From requirements to implementation & test

• Who is working on what?• What is the business value of each change?

www.ranger4.com

DevOpstastic

Development implementation

• What code changed for requirement xyz? What is the technical risk?

• Why has file Conversion.java changed, who changed in and when did it change?

www.ranger4.com

DevOpstastic

Building software

• What code changes have been committed by developers?

• What implementation work has been recently completed?

• What is the status of unit testing?

www.ranger4.com

DevOpstastic

Getting ready to deploy applications

• What content is ready for deployment?

• Through which environments has each version progressed?

• What requirements are satisfied by this deployable content?

www.ranger4.com

DevOpstastic

The big pictureFrom requirement to a deployed application

www.ranger4.com

DevOpstastic

Across the software development lifecycle

www.ranger4.com

DevOpstastic

Investment Case

CONSISTENCY & VISIBILITY• Create a consistent process across all environments• Validate through development and QA• Obtain ‘license’ to deploy to production

CONTROL & GOVERNANCE• Implement an audited process for deployment• Make all environments visible, but control who can do what

INTEGRATION ACROSS THE LIFECYCLE• Linked data – no more spreadsheets of links and references• Track changes and deploy what is needed at the right time• Create an executable plan and track delivery progress