the doctor is “in” : using the office hours concept to make limited resources most effective
Post on 13-Jan-2015
2.498 Views
Preview:
DESCRIPTION
TRANSCRIPT
The Doctor is “In”
Andrea Leszek | Catherine Courage
Agile 2008 Conference, Toronto August 2008
Using the Office Hours Concept to Make Limited Resources Most Effective
Safe Harbor Statement 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 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, 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 our fiscal year ended January 31, 2008, our quarterly report on Form 10-Q for our fiscal quarter ended April 30, 2008, and in other filings with the Securities and Exchange Commission. These documents 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.
Leader in On-Demand Customer Relationship Management
First Ever Platform as a Service
3 People in R&D 4 Major Releases Per Year
9 Years Ago at the Beginning of Salesforce.com
Smart Fast Innovative
43,600+ Customers 1,000,000+ Subscribers
150 Million Transactions Per Day 300+ People in R&D
Rapid Success
At a price…
2000 2001 2002 2003 2004 2005 2006
Features Delivered per Team
Days between Major Releases
1 Major Release in 2006
How did Development Services fit in?
Technical Writers Usability Analysts
User Interaction Designers
Each person assigned to multiple product development teams based on features being
developed
1 hour weekly meeting per team
Work spread out across entire release cycle
Critical to Product’s Success
Terms of Use: Product Works as
Documented
Key Values of R&D: Usability
User-Centered Design
2000 2001 2002 2003 2004 2005 2006 2007
Features Delivered per Team
Days between Major Releases
Agile Transformation and Amazing Results
How did Development Services fit in?
All scrum teams got assigned writer, designer, and usability analyst
68 % of Development Services staff assigned to 3 or
more scrum teams
%
* Source: Spring 2007 R&D ADM Survey
Not enough time for actual work
Multiple daily 15 minute meetings Multiple monthly sprint planning meetings Multiple sprint retrospectives and reviews
Timelines tighter
Work compressed
Frequent context switching
No Change to Core Values
Results Not That Amazing for DS
* Source: Spring 2007 R&D ADM Survey
“Hire More.”
“Not enough staff to cover teams adequately.”
“Not enough resources per team (for the amount of work to
be accomplished)”
“Lack of resources”
“One word: headcount”
* Source: Spring 2007 R&D ADM Survey
2 Reduce the number of dedicated teams per DS staff member
Prioritize
Determine Complexity
Skills of PO Work with Execs
How did we fill the gap?
Team-Driven Solution
Make it simple!
Predetermined time and locations
Self-Service
OH assignees self-organizing
UE Office Hours
15 60 30 0 45
Discuss User Stories
Design Recommendations
Minutes
Review Artifacts
Technical Writing Office Hours
1 2 0 3
Determine Doc Needed
Final Fixes
Sessions
Draft Reviewed & Edited
Adoption
* Source: R&D Programs
Challenges
Successes: Viral Effect
Successes: Additional Staff Added
“Effective on small features and small
teams.”
“Worked well for the small changes
we needed to make.”
“Good solution to getting small projects done that don’t require
a full-time person.”
“OH are very useful for those smaller issues/projects.”
Successes: DS Believes Agile Works
* Source: Spring 2007 & 2008 R&D ADM Surveys
Successes: DS is Having Fun
* Source: Spring 2007 & 2008 R&D ADM Surveys
top related