Socialtext Distributed Agile


Published on

Adina Levin and Tracy Ruggles from Socialtext share their experience with Agile Product Management Methodologies with Social Software. A video of this presentation is available here

Sorry the font is messed up.

Published in: Business, Travel

Socialtext Distributed Agile

  1. 1. Socialtext Distributed Agile Ross Mayfield Adina Levin Tracy Ruggles
  2. 2. Socialtext Distributed Agile <ul><li>Distributed agile is a trend </li></ul><ul><ul><li>At BarCamp and D-Camp a few years ago </li></ul></ul><ul><ul><li>Last year at PCamp </li></ul></ul>
  3. 3. Socialtext Distributed Agile
  4. 4. Socialtext Distributed Agile <ul><li>Why agile? </li></ul><ul><ul><li>Personal experience with waterfall </li></ul></ul><ul><ul><li>300 page prds </li></ul></ul><ul><ul><li>24 month product cycles </li></ul></ul><ul><ul><li>product obsolete when released </li></ul></ul><ul><ul><li>dev and pm mutual incomprehension </li></ul></ul><ul><li>Agile sounds like better way </li></ul><ul><ul><li>Small-a agile, not big-A agile </li></ul></ul><ul><ul><li>Lots of war stories requiring beer </li></ul></ul>
  5. 5. Socialtext Distributed Agile <ul><li>The basics </li></ul><ul><ul><li>2 week iterations </li></ul></ul><ul><ul><li>Hosted service and SAAS appliance </li></ul></ul><ul><ul><li>Hosted every 2 weeks, appliance every month </li></ul></ul>
  6. 6. Anatomy of a story <ul><li>Anatomy of a story </li></ul>
  7. 7. Anatomy of a Story
  8. 8. Anatomy of a Story
  9. 9. Anatomy of a Story
  10. 10. Anatomy of a Story <ul><li>Cross-functional discussion </li></ul><ul><li>Real time teamwork </li></ul>
  11. 11. Anatomy of a story family <ul><li>How to do planning with agile </li></ul><ul><ul><li>Leadership team direction for year and quarter </li></ul></ul><ul><ul><li>Stories fit into projects. </li></ul></ul><ul><ul><li>Occasional focused planning a project level </li></ul></ul><ul><ul><li>Occasional f2f and focus </li></ul></ul>
  12. 12. Real Live Customers <ul><li>” Customer feedback blog&quot; </li></ul>
  13. 13. Information radiators
  14. 14. Challenges - Teamwork <ul><li>“ The swarm&quot; </li></ul><ul><ul><li>Started with multiple processes </li></ul></ul><ul><ul><li>Changed to one process, one dev group </li></ul></ul><ul><li>Emotional challenges </li></ul><ul><ul><li>Can't fight and then play foosball, get beer </li></ul></ul><ul><li>Logistics </li></ul><ul><ul><li>Need to be sensitive to timezone differences or we'll miss people </li></ul></ul>
  15. 15. Socialtext Agile Culture <ul><li>Learning... retrospect every iteration, what went well, what didn't, what can be improved </li></ul><ul><li>JFDI.. if you have an idea for improvement, take the ball </li></ul><ul><li>Transparency - code, design, planning, customer feedback, better in the open </li></ul>
  16. 16. Outakes
  17. 17. Challenges - Design <ul><li>Harder to &quot;whiteboard&quot; ideas together </li></ul><ul><ul><li>voip and screen or vnc </li></ul></ul><ul><ul><li>communicate that it's a brainstorming meeting and not tactical story definition </li></ul></ul><ul><li>Design patterns </li></ul><ul><ul><li>could do more to make it easier to add additional stories with design variants </li></ul></ul><ul><li>Usability testing </li></ul><ul><li>Architecture </li></ul><ul><ul><li>Review stories in families </li></ul></ul><ul><ul><li>Appoint architecture steward </li></ul></ul>
  18. 18. Socialtext Agile Development <ul><li>No code ownership (but some expertise) </li></ul><ul><li>Source code control - cvs > subversion > git </li></ul><ul><li>Iteration capacity based on on &quot;yesterday's weather&quot; </li></ul><ul><li>Pair programming with voip and screen </li></ul><ul><li>Standup 3x per week - what are you working on, where do you need help </li></ul>
  19. 19. Socialtext Agile QA <ul><li>Release testing is a considered combination of automated and human testing with the goal of preventing unhappy experiences for our users. </li></ul><ul><li>Story test cover expected behavior & corner cases </li></ul><ul><ul><li>As stories are finished, QA validates and raises concerns during the iteration. </li></ul></ul><ul><li>Browser based testing with selenium </li></ul><ul><ul><li>UI tests run 24/7 just like unit tests. </li></ul></ul><ul><ul><li>Automated tests are maintained and always exercise a majority of the functions exposed to the user. </li></ul></ul><ul><li>Exploratory testing </li></ul><ul><li>Lightweight performance analysis </li></ul>