Managing Releases in the Cloud


Published on

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.

Published in: Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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 presentationA 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 administratorsI’ll 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
  • Cross stream impacts by processSystem functionality and process expertsTools for estimating, business case value templates, etc.
  • User 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.
  • We 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 it’s 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. We’ll 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.
  • 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.
  • 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.
  • Communicate the enhancements to your users and also provide easy to find links to training materials. The more informed they are the better. I’ve included a template that you can use as an example. It can be found at??
  • We do monthly minor enhancements and we do major enhancementstwice a year.
  • What is Super Care? Describe what we do. First couple of weeks we measure the training usage. Get them to complete training before triage.
  • ×