30
Release Management for Large Enterprises 7 5 Principles of Highly Successful Releases Rajan Chowhan, salesforce.com, Technical Solution Architect @rajanchowhan Srini Konakalla, salesforce.com, Director-Strategic Services @srinikona

Release Management for Large Enterprises

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Release Management for Large Enterprises

Release Management for Large

Enterprises

7 5 Principles of Highly Successful Releases

Rajan Chowhan, salesforce.com, Technical Solution Architect

@rajanchowhan

Srini Konakalla, salesforce.com, Director-Strategic Services

@srinikona

Page 2: Release Management for Large Enterprises

Safe Harbor

Safe harbor statement under the Private Securities Litigation Reform Act of 1995:

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if

any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-

looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of

product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of

management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments

and customer contracts or use of our services.

The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our

service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth,

interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other l itigation, risks associated

with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain,

and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling

non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the

financial results of salesforce.com, Inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This

documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.

Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may

not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently

available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

Page 3: Release Management for Large Enterprises

Rajan Chowhan

Technical Solution Architect - Strategic Services

@ rajanchowhan

Page 4: Release Management for Large Enterprises

Srini Konakalla

Director - Strategic Services

@srinikona

Page 5: Release Management for Large Enterprises

What is release management?

and why should I care?

http://www.flickr.com/photos/20408885@N03/3570184759

Page 6: Release Management for Large Enterprises

What?

Release Management

Page 7: Release Management for Large Enterprises

Why?

Page 8: Release Management for Large Enterprises

Reduce Risk

“This just does not work

for me” – Sales Executive

“I just thought it would look

a little different than this” –

Operations Manager http://blogs-images.forbes.com/glennllopis/files/2011/04/risk.jpg

Page 9: Release Management for Large Enterprises

Increase Stability

“Rajan fixed the bug in the case page rendering but introduced 2

others!”

“That change that Srini made has stopped people entering orders!”

“It tested fine in the UAT environment, so why is

production down!”

Page 10: Release Management for Large Enterprises

All While Improving Throughput!

Backlog

Steve is the…..

http://www.picarro.com

Page 11: Release Management for Large Enterprises

How good is your release process?

No regression

Zero bugs

100% user satisfaction

Your backlog is always empty

(“the business” users just cannot fill

it!).

Rollback – what’s that?!?

You would let Dr. Evil (and mini me!) mess

with your org, knowing your tests will pick up

bugs… ??

Page 12: Release Management for Large Enterprises

5 Principles for Large Organizations

DiQUAD

Page 13: Release Management for Large Enterprises

Principle #1

Define an Environment Strategy upfront

Hint: Ad-hoc sandbox proliferation is not good.

Plan for

LDV

Page 14: Release Management for Large Enterprises

Example: Environment Strategy for Small orgs

Dev

Config Full Copy

Dev

Prod

Development

Test Integration

1 Full copy

sandbox

Development

Configuration Only

Full Copy

Types of Sandboxes

Page 15: Release Management for Large Enterprises

Example: Environment Strategy for Larger orgs

Production

Quarterly

Release #1

Dev 1

Dev n

Test Cycle 1

Test Cycle 2 [External

Integrations]

Stage

Dev 1

Dev n

Test

Load Test

Dev 1

Dev n

Test Cycle 1

Test Cycle 2 [External

Integrations]

Dev 1

Dev n

Test

Support

Innovation

Quarterly

Release #2

Monthly

Release #1

Monthly

Release #2

10 Full

copy

sandboxes

Page 16: Release Management for Large Enterprises

Principle #2

Bring the pain forward

Integrate code early in the development process

Page 17: Release Management for Large Enterprises

The Tools

Everything You Need to Build

Apps

Eclipse Force.com IDE

Instantly Set Up Dev Environments

Force.com Sandbox

Easy Access to Code and Schema

Metadata API

Change Sets

Easy Tool for Admins to Migrate Changes

Page 18: Release Management for Large Enterprises

Continuous Integration

Continuous Integration (CI) is a technique used to quickly identify the many

issues that arise when integrating code. Code repositories and build servers are

core components.

Page 19: Release Management for Large Enterprises

Demo Continuous Integration

Page 20: Release Management for Large Enterprises

Principle #3

Build Quality In

100% Code Coverage is not enough!

William Deming: “Cease dependence on mass inspection

to achieve quality. Improve the process and build quality

into the product in the first place”

Page 21: Release Management for Large Enterprises

Build Quality - Best Practice

Diagram invented by Brian Marick

Page 22: Release Management for Large Enterprises

Demo Regression Testing

Page 23: Release Management for Large Enterprises

Principle #4

Measure, measure, measure!

Impact of change

Page 24: Release Management for Large Enterprises

Measure, Measure, Measure

Measurement How?

How much change is happening?

Source code deltas

How often is it happening?

Release cycles

What types of change?

Triggers, pages, fields, workflows etc.,

What are the results of those

changes?

# of bugs introduced, severity of bugs,

downtime (in minutes, in dollars),

Page 25: Release Management for Large Enterprises

Measure: Value Stream Mapping

Page 26: Release Management for Large Enterprises

Principle #5

Lather, Rinse and Repeat

Automate Deployment

Page 27: Release Management for Large Enterprises

Summary

Define an environment strategy upfront. Plan for LDV.

Bring the pain forward. Integrate code early.

Build quality in. 100% code coverage is NOT enough.

Measure. Measure. Measure.

Lather, Rinse and Repeat. Automate Deployments.

Page 28: Release Management for Large Enterprises

Coming Soon

Sandbox templates. Winter’13 pilot feature

Fast Deploy. Summer’12 pilot feature.

Page 29: Release Management for Large Enterprises

Rajan Chowhan

Technical Solution Architect – Strategic Services

@rajanchowhan

Srini Konakalla

Director - Strategic Services

@srinikona

Page 30: Release Management for Large Enterprises