The Ideal Salesforce Development Lifecycle

6,053 views

Published on

It's common for organizations of all sizes to stumble a bit before adopting an effective Release Management strategy. Whether you are small or large, join us as we cover important best practices, like: How many Sandboxes and what kind do I need? How can Developers and Admins best compliment each other's efforts? What is the best way to promote changes from one environment to another? Why can't I do my development in Prod? Get actionable recommendations for making your Salesforce development team more customer-focused by making your release cycle cleaner and more efficient.

Audio: https://www.youtube.com/watch?v=SGiBNMahr6g

Published in: Technology, Business
0 Comments
21 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,053
On SlideShare
0
From Embeds
0
Number of Embeds
41
Actions
Shares
0
Downloads
0
Comments
0
Likes
21
Embeds 0
No embeds

No notes for slide
  • PM, BA, Dev, Product Owner, Admin, QA
    QA != Developer
    PO = QA!
  • 2 Parts: Geoff & I - Mention
  • PM, BA, Dev, Product Owner, Admin, QA
    QA != Developer
    PO = QA!
  • PM, BA, Dev, Product Owner, Admin, QA
    QA != Developer
    PO = QA!
  • The Ideal Salesforce Development Lifecycle

    1. 1. The Ideal Salesforce Development Lifecycle Geoff Escandon, Appirio, Technical Consultant, @gjescandon Brandy Colmer, Arrowpointe, Customer Success, @forcedotmom Joshua Hoskins, Appirio, Solution Architect, @jhoskins
    2. 2. 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 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.
    3. 3. Brandy Colmer Customer Success Director, Arrowpointe @forcedotmom
    4. 4. Geoff Escandon Technical Consultant, Appirio @gjescandon
    5. 5. Joshua Hoskins Salesforce MVP Solution Architect, Appirio @jhoskins
    6. 6. What had happen was... • • • Change Only in Prod No Testing No Formal Process Followed
    7. 7. What scenario applies to you? Reactive? • That “quick” production fix, wasn’t so “quick” • Skipped the Sandbox? Sloppy! • New Process not followed? Communication! Proactive? • No Process Defined • Efficiency Freaks
    8. 8. So, imagine this... • • • • Clear Repeatable Process from Idea to Release Confident Deployments Clear Communication (Actions, Roles & Vocabulary) #Awesome Deployments Frequent Deployments = Happy Users Happy Dev Team = Happy Customers
    9. 9. Purpose To give admins insight to why they have challenges and provide the tools and processes to improve
    10. 10. What’s in it for you? • • • Best Practices Confidence A Handy Dandy Cheat Sheet o Tools o Communication Role Matrix
    11. 11. Who’s on our Team! Not Ideal Scenarios • Developer != Change Approver • Developer != Quality Assurance • Business Analyst != Change Approver • Change Approver != Quality Assurance • Project Manager != Developer Ideal Scenarios • Admin = BA, QA, RM • Admin = Dev, != QA
    12. 12. Unfortunately the “Norm” #NotAllowed
    13. 13. The Ideal Recipe for Success! +
    14. 14. Who Talks to Who? 1. Product Manager, “I want something!” 2. Project Manager, “New Project!” 3. Business Analyst , “What & Why (-How)” 4. Developer = “Dev Complete” 5. Administrator, “I understand the Solution” 6. Quality Assurance, “Testing Complete” 7. Release Manager, “Deployment Tested!” 8. Change Approver, “Deploy!” 9. Release Manager, “Deployed!” 10. Administrator, “Unit Testing Complete” 11. Product Manager, “It’s working!” 12. Project Manager, “Project Closed, Next!”
    15. 15. Define BEFORE Design - Who (Actor) - What (Context) - Why (Value) - Acceptance Criteria
    16. 16. Design BEFORE Developing - Native vs Custom - User Experience - System Impact - Boundary Systems - Level of Effort
    17. 17. Develop BEFORE User Review #CommonSense ... duh!
    18. 18. Review BEFORE Deployment - Unit Testing - User Review - Additional Iterations - More Testing - User Acceptance
    19. 19. Smaller Team? No Problem! • Builders cannot be testers! • Clear Boundaries, Keep Integrity
    20. 20. Deploy !?!?
    21. 21. Purpose To give admins insight to why they have challenges and provide the tools and processes to improve
    22. 22. #DF13
    23. 23. All about Appirio Appirio is a global services provider that helps enterprises reimagine their business and become more agile using crowdsourcing and cloud, social and mobile technology.  More than 600 enterprise customers successfully moved to the cloud  Strategic partner of Salesforce since 2006  On-demand access to 600,000 of the world’s top developers, designers and data analysts through Appirio’s community
    24. 24. All about Arrowpointe Arrowpointe builds apps powered by the force.com platform. We deliver some of the most popular and highest rated applications on the AppExchange. Our core focus is Geopointe, the #1 geo-mapping application available on the AppExchange, and a top 10 app overall.  Answer the ‘Where’ questions in your Salesforce data  2012 AppExchange Customer Choice Award winner  acrrowpointe.com/getmaps
    25. 25. Geoff Escandon Technical Consultant, Appirio @gjescandon Brandy Colmer Joshua Hoskins Customer Success, Arrowpointe @forcedotmom Solution Architect, Appirio @jhoskins

    ×