Salesforce Deployment: From Production Hacker to Agile Guru
4 likes559 views
The document discusses a presentation by Kevin Boyle on Salesforce deployment and release management strategies, emphasizing the importance of a deployment solution that is user-friendly, reliable, and predictable. It outlines the evolution of release management from individuals making direct changes in production to large teams employing integrated management with version control and continuous integration. The document also includes a safe harbor statement regarding forward-looking statements and potential risks associated with Salesforce's operations.
Salesforce Deployment: From Production Hacker to Agile Guru
- 1. Salesforce Deployment From Production Hacker to Agile Guru Kevin Boyle Head of Salesforce Tools Division, Gearset kevin@gearset.com @gearsethq
- 2. 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 any litigation, risks associated with completed and any 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 and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These 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. Safe Harbor
- 12. There will be a picture of an egg timer here…
- 13. What does a great deployment solution look like? A great deployment solution should adhere to the following principles • It should be easy to use • It should give you confidence • It should have predictable results • It should automate the bits that are annoying
- 14. Evolution of Salesforce Release Management
- 15. Levels of complexity Indviduals • Make changes straight in production Small teams • One sandbox for developers, pushing changes to a single production org Large teams • Individual developer orgs sharing changes via source control and automated deployment to production orgs
- 16. Individuals: No release management Pros • Works well for individuals without the need for additional services, and has zero overhead Cons • Can easily introduce bugs • No audit trail for changes • Everything is in one persons head so you have a very bad bus factor
- 17. Small teams: Basic release management Pros • Nice balance in complexity with some isolation between development and production Cons • Developers can easily trample on each others work • Can be hard when it comes to deployment time to know which changes should be added to the ChangeSet or the package.xml
- 18. Large teams: Integrated release management Pros • The best way to management your releases, with no disadvantage from a team or business point of view Cons • Can be complex to set up, with lots of moving parts such as a Continuous Integration server (Jenkins) and Version Control software (git)
- 20. Demo!
- 21. Next steps 1. Come and ask us questions 2. Grab a sticker so I don’t need to bring them back to the UK 3. Get a copy of our whitepaper on release management and let us know what you think
- 22. Thank you