Managing Releases in the Cloud

  • Published on
    24-Jan-2015

  • View
    301

  • Download
    2

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.

Transcript

PowerPoint Presentation

Managing Releases in the CloudAdministratorsAndr Pimentel: CA Technologies Deb Weller: Isilon SystemsHeather Ramsdell: salesforce.com

1Safe 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.2Release Management Maturity CycleService Evolves OvertimeLimitedComplexity/User BaseRelease Mgmt ServiceLowHighExtensive23ImplementationCollaborationCommunication5Configuration Mgmt/ Change SetsApex/Visualforce/ IDE Eclipse614Refine/Optimize

33Andr Pimentel

Senior Director, Global Bus Operations4AboutCA Technologies is an IT management software and solutions company with expertise across all IT environmentsfrom 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

Why We Need a Governance Process

Massive DemandOver 100 enhancement requests in the queueSales, Marketing, Services, Education, Support leveraging the platformExecutive MandateIf the pipeline is not in Salesforce it will not be recognizedAll deals must originate from a Salesforce opportunity (includes renewals)User AdoptionNo longer an issueWith increased adoption you get:Increased demands on the IT teamSystem integration throughout the enterprise means more complexityMultiple requests into IT from multiple groups reduces focus on delivery of key corporate initiatives

Cross stream impacts by processSystem functionality and process expertsTalk to Izzett about including the ADM SaaS estimator as a screenshot or two in my Dreamforce presentation

A slide on measurements of success. Measuring the ROI of each enhancement.

Add a slide with the sample communicationAnything that we can add around Branding, Communication, etc. Do any examples that we can as these are advanced administrators

Ill be on the G & the R of the GROW acronymMaybe show our use case template, Traceabilty Matrix, what documents we do, etc. and this is how we audit the release

Business and IT Engagement ModelIMPLEMENTATIONVALUE ANALYSISSUPPORTCollaboration

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

BusinessITCurrent Governance ProcessCross stream impacts by processSystem functionality and process expertsTools for estimating, business case value templates, etc.

Engaging with Each Functional AreaRegional Sales Operations,Finance, Support,Services, Marketing etc.Bi-weekly Value Analysis Meetings

Project StakeholdersWeekly Project MeetingsUser CommunityWeekly Support Queue Review Meetings

Value Analysis Implementation SupportCurrent Governance ProcessUser community We engage with key stakeholders within the different business areas. The user community consists of Operations Specialists to Director level participants. The key is to have participants that are knowledgeable in their areas, understand the priorities of their business, and most importantly, are empowered to make critical prioritization decisions.

Managing the Queue

Release Management ServiceWe have created a tracker in Sharepoint where we keep the enhancement list for the CA Service Desk application. We track status such as scheduled or testing. We keep tabs on which release its in (either monthly enhancement or major release) and also the most critical metric which is the ranking. We meet every two weeks with all key stakeholders and review the prioritized items. Well discuss and vote on which items make the release. Allows everyone to understand what is happening in the platform and we hash out dependencies with other workstreams.

Release Management ServiceTraceability Matrix locks down scope

Prioritize, lock down the scope and create your bible of sorts for the release. For each line in the matrix we also depict what document will be updated. For example, there will be a configuration document linked to the matrix line item. This facilitates the ability to go back and review specific functionality and understand where it originated.These will also be grouped by functionality to determine which business process documents need to be updated and how training will be built.If we have scope changes we will convene a Systems Steering Committee to make a decision. For the most part we have scope pretty well defined and if we change things we will for the most part swap things out.Release Management ServiceUse Cases

Detailed requirements are driven from the line items in the Traceability Matrix. Use Cases are a great way to capture in business terms what the expected functionality should be.Release Management Service

Final StepCommunicate!

Communicate the enhancements to your users and also provide easy to find links to training materials. The more informed they are the better. Ive included a template that you can use as an example. It can be found at??Detailed Checklist to Get Started TodayEstablish a dedicated Operations teamDevelop the Release cadenceDoes 90 days work for you? Is it realistic?Define & document the prioritization processLock down scope and keep it in an easy to review formatA Traceability Matrix helps keep the team focused on whats in and whats notPut a communication plan in placeGet the IT Team onboardWork closely with ITDont expect to just hand over requirements, walk away, and come back when its time to test

We do monthly minor enhancements and we do major enhancements twice a year.Release Cadence

What is Super Care? Describe what we do. First couple of weeks we measure the training usage. Get them to complete training before triage.Deb WellerIsilon Systems, Inc.Enterprise Architect

15All About Isilon Systems, Inc.Salesforce.com customer since 2002380 internal users in Sales, Marketing, Customer Support, Field Service and Operations worldwide2000+ Customer Portal and Partner Portal users AppXchange packages include Eloqua, Jigsaw, Brainshark, Email to Case Premium, DemandTools, DBAmpIntegrations with several external systems increase the need for a consistent release management policySandboxes: 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.IT TaskforceMonthly meeting (can be called more frequently)Representatives from the business groups meet to prioritize IT effort on projectsTracking via ProjectForce* customized Force.com appHigh level and Detailed RequirementsAction items, Issues, Risks and burn rateKey red-yellow-green indicatorsDocumentation for systems under SOX audit controls

* Available on appexchange

17IT Taskforce Project Force

http://sites.force.com/appexchange/listingDetail?listingId=a0N30000001fkfpEAA18Release Management OptionsForce.com IDEClient app based on the Eclipse platformDeveloper-focusedSupport for version control and team developmentCan migrate code and metadata between orgs

Cloud DeployAdministrator-focusedReleased in Spring 10Define connections between orgsCreate change sets for migration of code and config between orgs

19Note specific dev sessions for Force.com IDE and also Developer Lounge resourcesCloud DeployUse Sandboxes to make and test changesCreate Deployment Connections to define flow between Sandbox instances and ProductionCreate Change Sets to package changes between Sandboxes and Production via Deployment ConnectionsMonitor Deployments to view Deployments in Progress and Completed Deployments

20Full sandboxes contain a complete copy of your data from your production org

Users are created with the sandbox name appended for example, deb.weller@isilon.com.FULL1

Other emails on records are not altered be sure to use a product like DataLoader or CRM Fusions DemandTools to remove emails from Contacts and Leads before testing! Tip: blank out the email field for any record that contains the @ sign

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 daysAlways use sandboxes!Give your developers personal Developer sandboxesReserve Full and Config sandboxes for major project workCoordinate with your admins on strategy for refreshLimit access to sandboxes at a project levelGreat sandbox tips are available in SF Online Help

21Full sandboxes contain a complete copy of your data from your production org

Users are created with the sandbox name appended for example, deb.weller@isilon.com.FULL1

Other emails on records are not altered be sure to use a product like DataLoader or CRM Fusions DemandTools to remove emails from Contacts and Leads before testing! Tip: blank out the email field for any record that contains the @ sign

Sandboxes Structural Example

22-Deployment ConnectionsSet up Deployment Connections to define orgs and directions that Change Sets can be copied

23Change Sets are available under Setup / App Setup / Deploy - set up your Deployment Connections first to define which orgs and directions change sets can be copied. You have to authorize the connection in both the sending and the target org. Change SetsChange sets can be set up bi-directionally and with multiple orgsContain metadata items you can configure with SetupCan only be modified until they are uploaded, but you can clone Change Sets that were previously uploaded to add new itemsCheck dependencies for objects in your Change SetValidate your Change Sets before deploying Review any error messages that would happen on deployment24Use sandboxes and change sets as disaster recovery - Backup production items into a fresh sandbox, use as a backup in case you need to roll back changes in production

Use change sets to move production items to sandbox Change SetsNo version control, but you can get creative on naming conventions to organize your Change Sets Pre-pend project namesUse specific project IDs or change order IDs Add meaningful descriptions when creating change setsExcellent best practices for Change Sets are available on SF Online Help

25Use sandboxes and change sets as disaster recovery - Backup production items into a fresh sandbox, use as a backup in case you need to roll back changes in production

Use change sets to move production items to sandbox Change Sets Available ComponentsAnalytic SnapshotApex Class, Trigger, S-ControlApp, TabButton or LinkCustom Field, Object, Report Type, SettingDashboard, ReportDocument, FolderEmail Template, LetterheadHome Page Layout and Component

List ViewPage LayoutProfileRecord TypeStatic resourceValidation RuleVisualforce Page and ComponentWorkflow Rule, Email Alert, Field Update, Outbound Message, Task

26Deployment Change Sets

27Documentation - Salesforce ContentUse a Salesforce Content workspace to track configuration notes for your Salesforce orgInformation on specific projectsDatasheets from AppXchange packagesUAT Testing NotesCan upload multiple versions, tag docs and have your administrators subscribe to the workspace for updates28Documentation - Salesforce Content

29CommunicationUse Salesforce Chatter to optimize communication around changes to Salesforce.comProvides a searchable tool with instant notification!Allows dissemination of changes to specific groups of users via Chatter GroupsConsider other collaboration tools like Ideas and Answers to engage your internal users and solicit input for changes

30=Cloud Deploy TakeawaysCreate sandbox methodology to support specific projects and sustainabilityAgree among business and IT teams on access, naming con...