Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (16)
Similar to Pivotal tracker presentation 10-13-2010
Similar to Pivotal tracker presentation 10-13-2010 (20)
Recently uploaded
Recently uploaded (20)
Pivotal tracker presentation 10-13-2010
- 1. Pivotal Tracker #protips ATLRUG 201010131830 Joe Moore (@joem) joe@pivotallabs.com
- 2. About Pivotal Labs • Software development consultancy for over 20 years • Agile (XP) since mid ‘90s • Rails since 2005
- 3. 100 Pivots HQ in San Francisco, offices in NYC, Boulder, and Singapore
- 4. 100 Pivots HQ in San Francisco, offices in NYC, Boulder, and Singapore Me
- 6. Clients
- 7. Clients
- 9. 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)
- 10. Oh yeah...
- 11. Oh yeah... We call it “Tracker”, not “Pivotal”
- 12. Oh yeah... We call it “Tracker”, not “Pivotal” ... cuz we work for Pivotal
- 16. Perhaps another time? $$$ ???
- 17. Perhaps another time? $$$ ???
- 18. We built Tracker to support the typical agile Pivotal project
- 19. 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
- 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.
- 22. 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”)
- 23. 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!
- 24. Story Lifecycle
- 26. Velocity
- 27. Charts
- 28. Integrations
- 29. Developer API • RESTful XML HTTP API • Read/Write access to projects and stories • Activity web hook (push HTTP)
- 30. 3rd Party Tools
- 31. 3rd Party Tools
- 32. 3rd Party Tools
- 33. 3rd Party Tools
- 34. 3rd Party Tools
- 35. 3rd Party Tools
- 36. 3rd Party Tools
- 37. #protips from @pivotallabs It’s not the technology, it’s the process
- 38. Tracker is not a replacement for conversations.
- 39. Tracker is not a replacement for conversations.
- 40. Stories are fine-grained and user-centric
- 41. Customers and developers should write stories together.
- 42. Customers and developers should write stories together. ... because a story is customer business value + developer deliverable
- 44. Weekly Iteration Planning ... where customers and developers review and estimate upcoming stories
- 45. Weekly Iteration Planning Dev Team estimates as a group Play an estimation game
- 46. The Customer prioritizes stories -- physically!
- 47. The Customer prioritizes stories -- physically! ... even if it makes them cry.
- 48. The Customer prioritizes stories -- physically! ... even if it makes them cry. informed by the development team
- 49. Developers can create stories and put them in the Icebox
- 50. Developers can create stories and put them in the Icebox ... but only the Customer can prioritize them.
- 51. You must have a Tracker Czar
- 52. 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???”
- 53. You must have a Tracker Czar
- 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
- 55. 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
- 56. 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.
- 59. There’s always Monday ...if your iterations start on Tuesday.
- 61. Don’t start max-point stories
- 62. Don’t start max-point stories Reserved for “OMG” stories.
- 63. Never restart an Accepted story. X Make a new story or bug.
- 64. Turn Chores into Stories if you can
- 65. Back-date stories finished last iteration, but accepted later.
- 66. Back-date stories finished last iteration, but accepted later. ... maintains Velocity calculation.
- 67. Assign the customer/verifier the “requested” ... they will get email updates for comments and delivered stories.
- 68. Must-have Labels • blocked • needs-prioritization • needs-discussion • suggestion • needs-design • needs-assets
- 69. One Big List
- 70. Joe’s Personal Point Scale (based on Fibonacci)
- 71. Questions?
- 72. Thank You!
- 74. Linkage Joe Moore Pivotal Labs Pivotal Tracker @joem pivotallabs.com pivotaltracker.com joe@pivotallabs.com @pivotallabs @pivotaltracker 40withegg.com