Agile Development at Salesforce.com大沢 良樹Salesforce.com Inc.July 2012
Safe HarborSafe 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 theassumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed orimplied by the forward-looking statements we make. All statements other than statements of historical fact could bedeemed forward-looking, including any projections of subscriber growth, earnings, revenues, or other financial items andany statements regarding strategies or plans of management for future operations, statements of belief, any statementsconcerning new, planned, or upgraded services or technology developments and customer contracts or use of ourservices.The risks and uncertainties referred to above include – but are not limited to – risks associated with developing anddelivering new functionality for our service, our new business model, our past operating losses, possible fluctuations inour operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, theoutcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, theimmature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivateour employees and manage our growth, new releases of our service and successful customer deployment, our limitedhistory reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Furtherinformation on potential factors that could affect the financial results of salesforce.com, inc. is included in our annualreport on Form 10-K for the most recent fiscal year ended January 31, 2010. This documents and others are availableon 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 currentlyavailable and may not be delivered on time or at all. Customers who purchase our services should make the purchasedecisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does notintend to update these forward-looking statements.
AGENDA1. About me2. About Salesforce.com3. Adaptive Development Methodology4. 継続的インテグレーション5. 自動化テスト6. リリースマネージメント
Salesforce Release Cycle Release Release Product Development Sprints Release Planning Sprint December January February March April May June Release Release de Line Product Development Sprints Release Planning SprintOpens April May June July August September October Code Line Opens
Doneness Checklist <機能 1> <機能 2> <機能 3>Code checked in and follows department standards No open regressions. Automated tests written and reviewed for all regressionsNo open P1 & P2 bugs Code Coverage of 70% (or as agreed with team) 70% 70% 100% of test cases logged in QAForce and executed in a QA environment, and all P1/P2 cases passingAll resolved bugs verified and closed Performance/scalability impact ascertained and sys testing scheduled if requiredUE has reviewed any new features; P1 and P2 UI bugs fixedUsability testing completed when necessary, and feedback incorporated into backlogCode and UI reviewed for 508 compliance; UE team notified of any non-compliant featuresAll UI labels ready for localization vendors User documentation complete and checked in Metrics to measure customer usage have been defined and a Metric Request ticket filed for new metricsSecurity standards met and critical issues resolved
Scrum at Scale Scrum of Scrum of Technical Operations Scrums Platform Division Applications Division Infrastructure Division Scrum of Scrum of Scrum of Scrums Scrums Scrums Shared Resources Scrum Teams UI Design Doc(with dedicated Dev & QA) System Usability Test Work group Work group