Pivotal tracker presentation 10-13-2010

5,572 views
5,461 views

Published on

"Pivotal Tracker Protips" presentation by Joe Moore at the Atlanta Ruby Group (ATLRUG) on 10/13/2010.

Published in: Technology, Business

Pivotal tracker presentation 10-13-2010

  1. 1. Pivotal Tracker #protips ATLRUG 201010131830 Joe Moore (@joem) joe@pivotallabs.com
  2. 2. About Pivotal Labs • Software development consultancy for over 20 years • Agile (XP) since mid ‘90s • Rails since 2005
  3. 3. 100 Pivots HQ in San Francisco, offices in NYC, Boulder, and Singapore
  4. 4. 100 Pivots HQ in San Francisco, offices in NYC, Boulder, and Singapore Me
  5. 5. 6 Tracker Pivots
  6. 6. Clients
  7. 7. Clients
  8. 8. What is Tracker? • Shared, predictive, collaborative to-do list for software development teams • Free, open to public: pivotaltracker.com • User by thousands of teams and companies, over 100K users and over 100K projects • Used on all of our projects at Pivotal (and then some) • Rails app, hosted at Engine Yard (xCloud)
  9. 9. Oh yeah...
  10. 10. Oh yeah... We call it “Tracker”, not “Pivotal”
  11. 11. Oh yeah... We call it “Tracker”, not “Pivotal” ... cuz we work for Pivotal
  12. 12. Perhaps another time?
  13. 13. Perhaps another time?
  14. 14. Perhaps another time?
  15. 15. Perhaps another time? $$$ ???
  16. 16. Perhaps another time? $$$ ???
  17. 17. We built Tracker to support the typical agile Pivotal project
  18. 18. We built Tracker to support the typical agile Pivotal project • Small team of 2-8 developers with a highly involved customer • 100% pairing and TDD/BDD • Collective code ownership via constant pair rotation and even rotation between teams/projects • Weekly iterations, frequent releases
  19. 19. What’s a Story? Feature with verifiable business value to the team’s customer. Has estimated effort and risk to complete by the dev team.
  20. 20. What’s a Story? Feature with verifiable business value to the team’s customer. Has estimated effort and risk to complete by the dev team. Chores No verifiable business value, but need to get done (e.g. “tech tasks”)
  21. 21. What’s a Story? Feature with verifiable business value to the team’s customer. Has estimated effort and risk to complete by the dev team. Chores No verifiable business value, but need to get done (e.g. “tech tasks”) Bugs ... it’s a Bug!
  22. 22. Story Lifecycle
  23. 23. Position is Priority
  24. 24. Velocity
  25. 25. Charts
  26. 26. Integrations
  27. 27. Developer API • RESTful XML HTTP API • Read/Write access to projects and stories • Activity web hook (push HTTP)
  28. 28. 3rd Party Tools
  29. 29. 3rd Party Tools
  30. 30. 3rd Party Tools
  31. 31. 3rd Party Tools
  32. 32. 3rd Party Tools
  33. 33. 3rd Party Tools
  34. 34. 3rd Party Tools
  35. 35. #protips from @pivotallabs It’s not the technology, it’s the process
  36. 36. Tracker is not a replacement for conversations.
  37. 37. Tracker is not a replacement for conversations.
  38. 38. Stories are fine-grained and user-centric
  39. 39. Customers and developers should write stories together.
  40. 40. Customers and developers should write stories together. ... because a story is customer business value + developer deliverable
  41. 41. Weekly Iteration Planning
  42. 42. Weekly Iteration Planning ... where customers and developers review and estimate upcoming stories
  43. 43. Weekly Iteration Planning Dev Team estimates as a group Play an estimation game
  44. 44. The Customer prioritizes stories -- physically!
  45. 45. The Customer prioritizes stories -- physically! ... even if it makes them cry.
  46. 46. The Customer prioritizes stories -- physically! ... even if it makes them cry. informed by the development team
  47. 47. Developers can create stories and put them in the Icebox
  48. 48. Developers can create stories and put them in the Icebox ... but only the Customer can prioritize them.
  49. 49. You must have a Tracker Czar
  50. 50. You must have a Tracker Czar “We just delivered some stories to accept/reject” “The backlog is getting low, can you prioritize some stories?” “We’re confused about that story you added” “We’re blocked on XYZ because the design isn’t finished” “Can you please accept/reject those stories???”
  51. 51. You must have a Tracker Czar
  52. 52. You must have a Tracker Czar It’s a good idea to have a formal role: Anchor, Scrum Master, Coach, Engagement-Lead, Customer Liaison
  53. 53. You must have a Tracker Czar It’s a good idea to have a formal role: Anchor, Scrum Master, Coach, Engagement-Lead, Customer Liaison Customer like consistency
  54. 54. You must have a Tracker Czar It’s a good idea to have a formal role: Anchor, Scrum Master, Coach, Engagement-Lead, Customer Liaison Customer like consistency It’s a lot of work. Coding time will be impacted.
  55. 55. Random Tracker Tips
  56. 56. There’s always Monday
  57. 57. There’s always Monday ...if your iterations start on Tuesday.
  58. 58. Don’t start max-point stories
  59. 59. Don’t start max-point stories Reserved for “OMG” stories.
  60. 60. Never restart an Accepted story. X Make a new story or bug.
  61. 61. Turn Chores into Stories if you can
  62. 62. Back-date stories finished last iteration, but accepted later.
  63. 63. Back-date stories finished last iteration, but accepted later. ... maintains Velocity calculation.
  64. 64. Assign the customer/verifier the “requested” ... they will get email updates for comments and delivered stories.
  65. 65. Must-have Labels • blocked • needs-prioritization • needs-discussion • suggestion • needs-design • needs-assets
  66. 66. One Big List
  67. 67. Joe’s Personal Point Scale (based on Fibonacci)
  68. 68. Questions?
  69. 69. Thank You!
  70. 70. Linkage Joe Moore Pivotal Labs Pivotal Tracker @joem pivotallabs.com pivotaltracker.com joe@pivotallabs.com @pivotallabs @pivotaltracker 40withegg.com

×