47
Managing Releases in the Cloud Administrators André Pimentel: CA Technologies Deb Weller: Isilon Systems Heather Ramsdell: salesforce.com

Managing Releases in the Cloud

Embed Size (px)

DESCRIPTION

Managing the software development life cycle in the cloud is different than traditional client-based systems and application. In this session, you'll learn ideas and tools to help develop and execute an effective release management strategy for your Salesforce org.

Citation preview

Page 1: Managing Releases in the Cloud

Managing Releases in the CloudAdministrators

André Pimentel: CA Technologies Deb Weller: Isilon SystemsHeather Ramsdell: salesforce.com

Page 2: Managing Releases in the Cloud

Safe HarborSafe 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 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, 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 litigation, 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-K for the most recent fiscal year ended January 31, 2010. This documents and others 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 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: Managing Releases in the Cloud

Release Management Maturity CycleService Evolves Overtime

Limited Complexity/User Base

Re

lea

se

Mg

mt

Se

rvic

e

Low

High

Extensive

2

3Implementation

Collaboration

Communication

5Configuration

Mgmt/ Change Sets

Apex/Visualforce/ IDE Eclipse

6

1

4

Refine/Optimize

Page 4: Managing Releases in the Cloud

André PimentelSenior Director,

Global Bus Operations

Page 5: Managing Releases in the Cloud

About

CA Technologies is an IT management software and solutions company with

expertise across all IT environments—from mainframe and physical to virtual

and cloud. CA Technologies manages and secures IT environments, enabling

our customers to deliver more flexible IT services.

CA Technologies SFDC Statistics:• 4,800 Users, 68 Countries, 31 Currencies• Over 1 million page views per month• 46 Custom Objects/ 18 Custom Tabs• System Usage:

• Marketing, • PRM being rolled out, • CPQ using Sterling Commerce, • custom TAQ application, • customized opportunity tracks stages at product line item level

• AppExchange Apps: • Mobile Administration, • Referencestor, • Jigsaw, • Outlook plug, • Click-to-Dial

• 2 full sandboxes, 5 configuration sandboxes, 14 development sandboxes

Page 6: Managing Releases in the Cloud

Why We Need a Governance Process

Massive Demand– Over 100 enhancement requests in the queue

– Sales, Marketing, Services, Education, Support leveraging the platform

Executive Mandate– If the pipeline is not in Salesforce it will not be recognized

– All deals must originate from a Salesforce opportunity (includes renewals)

User Adoption– No longer an issue

– With increased adoption you get:• Increased demands on the IT team

• System integration throughout the enterprise means more complexity

• Multiple requests into IT from multiple groups reduces focus on delivery of key corporate

initiatives

Page 7: Managing Releases in the Cloud

Business and IT Engagement Model

IMPLEMENTATIONVALUE ANALYSIS SUPPORTCollaboration

Cross Stream Impacts

Strategy

Drivers

Objectives

Metrics

Business Process

Business Cases

Workflow

Structure

Requirements

Estimating

Customization

Development

Configuration

ProductionSupportFixes

IssueResolution

CommunityCollaboration

Bug Fixes

User Support

Knowledge Docs

SupportMetrics

Business IT

Current Governance Process

Page 8: Managing Releases in the Cloud

Engaging with Each Functional Area

Regional Sales Operations,Finance, Support,

Services, Marketing etc.Bi-weekly Value Analysis Meetings

Project StakeholdersWeekly Project Meetings

User CommunityWeekly Support Queue Review Meetings

Current Governance Process

Page 9: Managing Releases in the Cloud

Managing the QueueRelease Management Service

Page 10: Managing Releases in the Cloud

Release Management ServiceTraceability Matrix locks down scope

Page 11: Managing Releases in the Cloud

Release Management ServiceUse Cases

Page 12: Managing Releases in the Cloud

Release Management Service Final Step

– Communicate!

Page 13: Managing Releases in the Cloud

Detailed Checklist to Get Started Today

Establish a dedicated Operations team

Develop the Release cadence– Does 90 days work for you?

– Is it realistic?

Define & document the prioritization process

Lock down scope and keep it in an easy to review format– A Traceability Matrix helps keep the team focused on what’s in and what’s not

Put a communication plan in place

Get the IT Team onboard– Work closely with IT

– Don’t expect to just hand over requirements, walk away, and come back when it’s

time to test

Page 14: Managing Releases in the Cloud

Release Cadence

Page 15: Managing Releases in the Cloud

Deb WellerIsilon Systems, Inc.

Enterprise Architect

Page 16: Managing Releases in the Cloud

All About Isilon Systems, Inc.

• Salesforce.com customer since 2002• 380 internal users in Sales, Marketing, Customer Support,

Field Service and Operations worldwide• 2000+ Customer Portal and Partner Portal users • AppXchange packages include Eloqua, Jigsaw, Brainshark,

Email to Case Premium, DemandTools, DBAmp• Integrations with several external systems increase the need

for a consistent release management policy• Sandboxes: 2 Full, 5 Config-only,

many Developer!

As a global leader in scale-out storage, Isilon delivers powerful yet simple solutions for enterprises that want to manage their data, not their storage. Unlike traditional enterprise storage, Isilon stays simple no matter how much storage is added, how much performance is required or how business needs change in the future. Headquartered in Seattle, Washington, Isilon Systems, Inc. includes offices in 10 countries.

Page 17: Managing Releases in the Cloud

IT Taskforce

Monthly meeting (can be called more frequently)

Representatives from the business groups meet to

prioritize IT effort on projects

Tracking via ProjectForce* customized Force.com app– High level and Detailed Requirements

– Action items, Issues, Risks and burn rate

– Key red-yellow-green indicators

– Documentation for systems under SOX audit controls

* Available on appexchange

Page 18: Managing Releases in the Cloud

IT Taskforce – Project Force

http://sites.force.com/appexchange/listingDetail?listingId=a0N30000001fkfpEAA

Page 19: Managing Releases in the Cloud

Release Management Options

Force.com IDE Client app based on the

Eclipse platform

Developer-focused

Support for version control

and team development

Can migrate code and

metadata between orgs

Cloud Deploy Administrator-focused

Released in Spring 10

Define connections

between orgs

Create change sets for

migration of code and

config between orgs

Page 20: Managing Releases in the Cloud

Cloud Deploy

Use Sandboxes to make and test changes

Create Deployment Connections to define flow between

Sandbox instances and Production

Create Change Sets to package changes between

Sandboxes and Production via Deployment

Connections

Monitor Deployments to view Deployments in Progress

and Completed Deployments

Page 21: Managing Releases in the Cloud

Sandboxes

Sandboxes (Developer and Configuration Only) can

now be refreshed daily!

Sandboxes can be deleted at any time

Full sandboxes can only be refreshed every 29 days

Always use sandboxes!– Give your developers personal Developer sandboxes

– Reserve Full and Config sandboxes for major project work

– Coordinate with your admins on strategy for refresh

– Limit access to sandboxes at a project level

Great sandbox tips are available in SF Online Help

Page 22: Managing Releases in the Cloud

Sandboxes – Structural Example

Page 23: Managing Releases in the Cloud

Deployment Connections

Set up Deployment Connections to define orgs and

directions that Change Sets can be copied

Page 24: Managing Releases in the Cloud

Change Sets

Change sets can be set up bi-directionally and with

multiple orgs

Contain metadata – items you can configure with Setup

Can only be modified until they are uploaded, but you

can clone Change Sets that were previously uploaded

to add new items

Check dependencies for objects in your Change Set

Validate your Change Sets before deploying – Review any error messages that would happen on deployment

Page 25: Managing Releases in the Cloud

Change Sets

No version control, but you can get creative on naming

conventions to organize your Change Sets – Pre-pend project names

– Use specific project IDs or change order IDs

– Add meaningful descriptions when creating change sets

Excellent best practices for Change Sets are available

on SF Online Help

Page 26: Managing Releases in the Cloud

Change Sets – Available Components

– Analytic Snapshot

– Apex Class, Trigger, S-

Control

– App, Tab

– Button or Link

– Custom Field, Object,

Report Type, Setting

– Dashboard, Report

– Document, Folder

– Email Template, Letterhead

– Home Page Layout and

Component

– List View

– Page Layout

– Profile

– Record Type

– Static resource

– Validation Rule

– Visualforce Page and

Component

– Workflow Rule, Email Alert,

Field Update, Outbound

Message, Task

Page 27: Managing Releases in the Cloud

Deployment– Change Sets

Page 28: Managing Releases in the Cloud

Documentation - Salesforce Content

Use a Salesforce Content workspace to track

configuration notes for your Salesforce org– Information on specific projects

– Datasheets from AppXchange packages

– UAT Testing Notes

Can upload multiple versions, tag docs and have your

administrators subscribe to the workspace for updates

Page 29: Managing Releases in the Cloud

Documentation - Salesforce Content

Page 30: Managing Releases in the Cloud

Communication

Use Salesforce Chatter to optimize communication

around changes to Salesforce.com

Provides a searchable tool with instant notification!

Allows dissemination of changes to specific groups of

users via Chatter Groups

Consider other collaboration tools like Ideas and

Answers to engage your internal users and solicit input

for changes

Page 31: Managing Releases in the Cloud

Cloud Deploy Takeaways

Create sandbox methodology to support specific

projects and sustainability

Agree among business and IT teams on access,

naming conventions and refresh strategy

Set up your Deployment Connections to support your

sandbox strategy

Use Change Sets to migrate changes and

dependencies between sandboxes

Communicate changes to your users using Salesforce

Chatter!

Page 32: Managing Releases in the Cloud

Release Management Maturity CycleService Evolves Overtime

Limited Complexity/User Base

Re

lea

se

Mg

mt

Se

rvic

e

Low

High

Extensive

2

3Implementation

Collaboration

Communication

5Configuration

Mgmt/ Change Sets

Apex/Visualforce/ IDE Eclipse

6

1

4

Refine/Optimize

Page 33: Managing Releases in the Cloud

Additional referencesBest Practices: - 9 steps to effective change management http://www.salesforce.com/customer-resources/learning-center/

details/best-practices/steps-to-effective-change-management.jsp

- Application Lifecycle https://na1.salesforce.com/help/doc/en/salesforce_development_lifecycle.pdf

- Change Sets – Admin tip sheetAttached to chatter for DF10 Release Mgmt Session

- Check list for getting startedAttached to chatter for DF10 Release Mgmt Session

Appexchange: - Projectforce:

http://sites.force.com/appexchange/listingDetail?listingId=a0N30000001fkfpEAA

Page 34: Managing Releases in the Cloud

Questions?

Page 35: Managing Releases in the Cloud

D I S C O V E R

Visit Customer Success Team at Campground

Discover

Training

Learning Paths

Experience

Product

Demos

Learn about Customer

Resources

the products, services and resources

Meet Success Experts

S U C C E S S

Find us at the Customer Success Team area of Salesforce.com Campground at Moscone North

Learn about how to win prizes including 10 iPads & more!

that help you achieve

Page 36: Managing Releases in the Cloud

Appendix

Page 37: Managing Releases in the Cloud

Appendix - Release Cadence

Page 38: Managing Releases in the Cloud

Appendix - Change Request Process Flow

Page 39: Managing Releases in the Cloud

Deployment– Change Sets

Page 40: Managing Releases in the Cloud

Deployment– Change Sets

Page 41: Managing Releases in the Cloud

Deployment– Change Sets

Page 42: Managing Releases in the Cloud

Deployment– Change Sets

Page 43: Managing Releases in the Cloud

Deployment– Change Sets

Page 44: Managing Releases in the Cloud

Deployment– Change Sets

Page 45: Managing Releases in the Cloud

Example: Multi-Project Delivery Cycle with 6 Sandboxes

Production Instance

Production Support

Staging

live

full copy

configuration-only, test data

configuration-only, training data

legend

DevIntegration

Long Projects

Training

Dev

Dev

Dev Rollup / Integration

Short Projects

developer

Page 46: Managing Releases in the Cloud

Managing Releases in the Cloud

Page 47: Managing Releases in the Cloud

How Could Dreamforce Be Better? Tell Us!

Log in to the Dreamforce app to submit

surveys for the sessions you attendedUse the

Dreamforce Mobile app to submit

surveysEvery session survey you submit is

a chance to win an iPod nano!

OR