How Writers Can Thrive in Agile Software DevelopmentGavin AustinLead Technical Writer

“Safe harbor” statement under the Private Securities Litigation Reform Act of 1995: This presentation and the oral remarks that accompany it contain forward-looking statements the achievement of which involves risks, uncertainties

and assumptions. If any such risks or uncertainties materialize or if any of the assumptions proves incorrect, our results 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 statements concerning new, planned or upgraded services or technology developments, 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 and statements about future customer contracts or future customer use of our services.The risks and uncertainties referred to above include - but are not limited to - interruptions or delays in our service or our Web hosting; our ability to complete and successfully release new and improved versions of our on-demand platform and development environment; our new business model; problems integrating, launching or operating services based on newly acquired businesses or technologies, breach of our security measures; possible fluctuations in our operating results and rate of growth; the emerging market in which we operate; our relatively limited operating history; our ability to hire, retain and motivate our employees and manage our growth; competition; our ability to continue to release and gain customer acceptance of new and improved versions of our CRM service; unanticipated changes in our effective tax rate; fluctuations in the number of shares outstanding; the price of such shares; foreign currency exchange rates and interest rates.Further information on these and other factors that could affect our financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings we make with the Securities and Exchange Commission from time to time, including our Form 10-K for the fiscal year ended January 31, 2009 and our Form 10-Q for the fiscal quarter ended April 30, 2009. These documents are available on the SEC Filings section of the Investor Information section of our website at www.salesforce.com/investor.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 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, except as required by law.

Safe Harbor

About me: I’m a writer who likes to talk

Agile is…

Sprint2-4 weeks

Sprint2-4 weeks

Sprint2-4 weeks

Scrum 101

Sprint2-4 weeks

Sprint Plan

Commitment Potentially shippable

Backlog

Daily Stand-up

Retrospective

2000

3 employees R&D

4 product releases

Releases on time

2005 & 2006

200+ employees R&D

1 product release a year

Releases not on time

Why we went Agile

2000 2001 2002 2003 2004 2005 2006

Features Delivered per Team

Days between Major Releases

2000 2001 2002 2003 2004 2005 2006 2007

Features Delivered per Team

ADM (Agile) results

Days between Major Releases

ADM has delivered total visibility, total transparency and unbelievable productivity… a complete win!”

Steve Fisher Executive Vice President, TechnologySalesforce.com

“

Acceptance

Originally, the methodology did not include documentation, but many organizations have figured out how to use it… ”

Alyssa Fox & Meredith Kramer Mobile and Agile: The Floating Writer’s Survival Kit

© 2008 WinWriters, Inc.

“

Challenges

Heartburn

1. Done!2. Fiction!3. Meetings!4. Estimates!5. Tracking tools!6. Multiple teams!

Indigestion

1. No time!2. No specs!3. Terminology!4. Team loyalties!5. Context switching!

66

31

80

30

78

4252

23

01020304050607080

Are yousatisfied withthe rollout of

agile?

Is agilemaking yourteam moreeffective?

Agile willmaintain orimprove the

quality of ourproducts.

Since therollout, I'm

having a goodtime.

R&DDS

Unhappy Writers

Implementation Strategies

1. Class

2. Patience

3. Templates

4. Tracking tool

5. Pad estimates

6. Clear definitions

7. Hire more writers

8. Extend doc deadlines

Daily Strategies

1. Ask

2. Email team

3. Write fiction

4. Revise fiction

5. Skip meetings

6. Doc “office hours”

Team Strategies

1. Barter

2. Doc “blitz”

3. Volunteer

4. Be wrong

5. Speak up

6. Self organizing

7. Shared service

8. Last line of defense

Benefits

1. Features less complex

2. Easier to document

3. Clearer communication

4. Know who does what

5. Know whom to ask

6. Fixed deadlines

7. Fewer surprises

Benefits

1. Doc has more impact

2. Doc is more visible

3. Learn what to expect

4. Retrospectives fix problems

5. Self determining

6. More personable

7. Team spirit

Happy Writers

0

24 23

62

30

14

46

00

10

20

30

40

50

60

70

The best time A good time Not much fun A terrible time

Mar-07Mar-08

Questions?

Whitepaper: http://www.ScrumAlliance.org