Your SlideShare is downloading. ×
Successfully Scaling an Agile Innovation Culture with Perforce - 2011 Perforce Users Conference
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Successfully Scaling an Agile Innovation Culture with Perforce - 2011 Perforce Users Conference

1,981
views

Published on

2011 Perforce User Conference presentation by Mike Saha and Steve Greene of salesforce.com.

2011 Perforce User Conference presentation by Mike Saha and Steve Greene of salesforce.com.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,981
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
49
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Lock the codeline; what we learned that led us to do codeline locking and why we came up with lock-by-team: teams that were good citizens would get punishedBy a few bad citizens and they didn’t like that.Lead into next slide by talking about how we no longer have broken builds.
  • Creates a cleaner codeline -> more productive staff -> this is part of the automation story
  • Invest in infrastructureAutobuilds support fast feedback
  • Radical TransparencyInvest in InfrastructureInvest in Automation
  • Radical TransparencyInvest in InfrastructureInvest in Automation
  • Transcript

    • 1. Successfully Scaling an Agile Innovation Culture with Perforce
      Steve GreeneVP, Technology Program Management
      Salesforce.com
      Mike SahaSr. Manager, Release Engineering
      Salesforce.com
    • 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 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.
    • 3. Why Agile?
    • 4. Predictability
      Productivity
      Innovation
    • 5. R&D
      IT
      Operations
      Marketing
      Services
    • 6. 125+
      Scrum Teams @ Salesforce
    • 7. 10B+
      Transactions per month
    • 8. 100K+
      Customers
    • 9. The Salesforce Transformation
    • 10. Major enterprise-wide Agile Transformation to ADM
      In just 3 months+ another 5 years of continuous improvement
    • 11. ADM (Adaptive Delivery Methodology)
      Salesforce.com flavor of agile
      Scrum project management framework
      XP practices
      Based on Lean principles
    • 12. What is ADM?
      Self-organizing
      Continuous integration
      Lean
      Agile
      Self-correcting
      Time-boxed
      Ftest - Selenium
      Re-factoring
      Collective Code Ownership
      Transparent
      Early Feedback
      Iterative
      Code Reviews
      Just-in-time
      Predictable releases
      Debt free
      Continuous Improvement
      Always Potentially Releasable
    • 13. Rhythm & Flow
      Release
      Release
      Release
      Release
      Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan
      Monthly Rhythm
    • 14. One Codeline
    • 15. Maintain Technical Health
      Debt is the Enemy
    • 16. Create a Single Definition of Done
    • 17. Investment in Automation
    • 18. Successfully Supporting an Agile Innovation Culture
    • 19. The Change Pipeline
      Velocity and logistics
    • 20. Own Your Pipeline
      Dev
      You
      Production
      QA
    • 21. Communication: Integrated Systems
    • 22. Change Propagation: Autointegrate
      Rel-B Production
      Rel-B Freeze
      Rel-A
      Rel-B Patch
      Mainline
    • 23. Directing Flow: Triggers
      • Ensure right changes in the right branch
      • 24. Enforce code reviews
      • 25. Propagate change info
      • 26. Lock a codeline
    • Stop the line when automated tests aren’t passing at >99%
    • 27. Invest in Automation: Pre-Checkin
      • No more broken builds
      • 28. Cleaner codeline
      • 29. Productivity boost
    • Invest In Infrastructure
      Invest In Infrastructure
      Invest in Infrastructure, build it to scale
    • 30. Invest In Infrastructure: Perforce
    • 31. Invest in Automation
    • 32. Radical Transparency with Metrics
    • 33. Radical Transparency
    • 34. Radical Transparency
    • 35.
    • 36. Q&A
      http://www.slideshare.net/sgreene