Pivotal Tracker Protips
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,813
On Slideshare
2,750
From Embeds
63
Number of Embeds
2

Actions

Shares
Downloads
31
Comments
0
Likes
5

Embeds 63

http://www.hashdog.com 61
http://wootify.com 2

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 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. 100PivotsHQ in SanFrancisco,offices in NYC,Boulder, andSingapore
  • 4. 100PivotsHQ in SanFrancisco,offices in NYC,Boulder, andSingapore Me
  • 5. 6TrackerPivots
  • 6. Clients
  • 7. Clients
  • 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. Oh yeah...
  • 10. Oh yeah...We call it “Tracker”, not “Pivotal”
  • 11. Oh yeah...We call it “Tracker”, not “Pivotal” ... cuz we work for Pivotal
  • 12. Perhaps another time?
  • 13. Perhaps another time?
  • 14. Perhaps another time?
  • 15. Perhaps another time? $$$ ???
  • 16. We built Tracker tosupport the typicalagile Pivotal project
  • 17. 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
  • 18. 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.
  • 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. Chores No verifiable business value, but need to get done (e.g. “tech tasks”)
  • 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”) Bugs ... it’s a Bug!
  • 21. Story Lifecycle
  • 22. Position is Priority
  • 23. Velocity
  • 24. Charts
  • 25. Integrations
  • 26. Developer API• RESTful XML HTTP API• Read/Write access to projects and stories• Activity web hook (push HTTP)
  • 27. 3rd Party Tools
  • 28. 3rd Party Tools
  • 29. 3rd Party Tools
  • 30. 3rd Party Tools
  • 31. 3rd Party Tools
  • 32. 3rd Party Tools
  • 33. #protips from@pivotallabsIt’s not the technology, it’s the process
  • 34. Tracker is not a replacement for conversations.
  • 35. Tracker is not a replacement for conversations.
  • 36. Stories arefine-grained anduser-centric
  • 37. Customers and developers should write stories together.
  • 38. Customers and developers should write stories together. ... because a story is customer business value + developer deliverable
  • 39. Weekly Iteration Planning
  • 40. Weekly Iteration Planning ... where customers and developersreview and estimate upcoming stories
  • 41. Weekly Iteration Planning Dev Team estimates as a group Play an estimation game
  • 42. The Customer prioritizes stories -- physically!
  • 43. The Customer prioritizes stories -- physically! ... even if it makes them cry.
  • 44. The Customer prioritizes stories -- physically! ... even if it makes them cry.informed by the development team
  • 45. Developers can create stories and put them in the Icebox
  • 46. Developers can create stories and put them in the Icebox... but only the Customer can prioritize them.
  • 47. You must have a Tracker Czar
  • 48. 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???”
  • 49. You must have a Tracker Czar
  • 50. You must have a Tracker Czar It’s a good idea to have a formal role:Anchor, Scrum Master, Coach, Engagement-Lead, Customer Liaison
  • 51. 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
  • 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 Customer like consistencyIt’s a lot of work. Coding time will be impacted.
  • 53. Random Tracker Tips
  • 54. There’s always Monday
  • 55. There’s always Monday...if your iterations start on Tuesday.
  • 56. Don’t start max-point stories
  • 57. Don’t start max-point storiesReserved for “OMG” stories.
  • 58. Never restart an Accepted story. X Make a new story or bug.
  • 59. Turn Chores into Stories if you can
  • 60. Back-date stories finished last iteration, but accepted later.
  • 61. Back-date stories finished last iteration, but accepted later.... maintains Velocity calculation.
  • 62. Assign the customer/verifier the “requested”... they will get email updates for comments and delivered stories.
  • 63. Must-have Labels• blocked • needs-prioritization• needs-discussion • suggestion• needs-design• needs-assets
  • 64. One Big List
  • 65. Joe’s Personal Point Scale (based on Fibonacci)
  • 66. Questions?
  • 67. Thank You!
  • 68. Linkage Joe Moore Pivotal Labs Pivotal Tracker @joem pivotallabs.com pivotaltracker.comjoe@pivotallabs.com @pivotallabs @pivotaltracker 40withegg.com