Over the last five years, Salesforce.com has been an industry leader in enterprise-wide Agile transformation and innovation with more than 100 Agile teams across their technology and products organization. In this session, hear how Salesforce has successfully implemented Agile at scale, and how Perforce has been key to enabling agility.

1. Successfully Scaling an
Agile Innovation Culture
with Perforce
Steve Greene Mike Saha
VP, Technology Program Sr. Manager, Release Engineering
Management Salesforce.com
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?
Lean Self-organizing Continuous integration
Agile
Time-boxed Self-correcting
Ftest - Selenium
Re-factoring
Transparent Collective Code Ownership
Early Feedback
Code Reviews Iterative
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
• Enforce code reviews
• Propagate change info
• Lock a codeline

24. Stop the line when automated tests
aren’t passing at >99%

25. Invest in Automation: Pre-Checkin
ü No more broken builds
ü Cleaner codeline
ü Productivity boost

26. Invest In Infrastructure
Invest In
Infrastructure
Invest in Infrastructure, build
it to scale

27. Invest In Infrastructure: Perforce

28. Invest in Automation

29. Radical Transparency with Metrics

30. Radical Transparency

31. Radical Transparency

33. Q&A
http://www.slideshare.net/sgreene