Pivotal Tracker   #protips  ATLRUG 201010131830    Joe Moore (@joem)   joe@pivotallabs.com
About Pivotal Labs• Software development  consultancy for over 20 years• Agile (XP) since mid ‘90s• Rails since 2005
100PivotsHQ in SanFrancisco,offices in NYC,Boulder, andSingapore
100PivotsHQ in SanFrancisco,offices in NYC,Boulder, andSingapore  Me
6TrackerPivots
Clients
Clients
What is Tracker?• Shared, predictive, collaborative to-do list  for software development teams• Free, open to public: pivo...
Oh yeah...
Oh yeah...We call it “Tracker”, not “Pivotal”
Oh yeah...We call it “Tracker”, not “Pivotal”   ... cuz we work for Pivotal
Perhaps another time?
Perhaps another time?
Perhaps another time?
Perhaps another time? $$$ ???
We built Tracker tosupport the typicalagile Pivotal project
We built Tracker to   support the typical   agile Pivotal project• Small team of 2-8 developers with a  highly involved cu...
What’s a Story?Feature with verifiable business value to the team’s customer. Has estimated effort and        risk to compl...
What’s a Story?Feature with verifiable business value to the team’s customer. Has estimated effort and        risk to compl...
What’s a Story?Feature with verifiable business value to the team’s customer. Has estimated effort and        risk to compl...
Story Lifecycle
Position is Priority
Velocity
Charts
Integrations
Developer API• RESTful XML HTTP API• Read/Write access to projects and stories• Activity web hook (push HTTP)
3rd Party Tools
3rd Party Tools
3rd Party Tools
3rd Party Tools
3rd Party Tools
3rd Party Tools
#protips from@pivotallabsIt’s not the technology, it’s        the process
Tracker is not a replacement for     conversations.
Tracker is not a replacement for     conversations.
Stories arefine-grained    anduser-centric
Customers and developers should     write stories together.
Customers and developers should     write stories together.      ... because a story is    customer business value        ...
Weekly Iteration Planning
Weekly Iteration Planning ... where customers and developersreview and estimate upcoming stories
Weekly Iteration Planning Dev Team estimates as a group    Play an estimation game
The Customer prioritizes stories --          physically!
The Customer prioritizes stories --          physically!   ... even if it makes them cry.
The Customer prioritizes stories --          physically!   ... even if it makes them cry.informed by the development team
Developers can create stories and put        them in the Icebox
Developers can create stories and put        them in the Icebox... but only the Customer can prioritize                  t...
You must have a Tracker Czar
You must have a Tracker Czar “We just delivered some stories to accept/reject”“The backlog is getting low, can you priorit...
You must have a Tracker Czar
You must have a Tracker Czar    It’s a good idea to have a formal role:Anchor, Scrum Master, Coach, Engagement-Lead,      ...
You must have a Tracker Czar    It’s a good idea to have a formal role:Anchor, Scrum Master, Coach, Engagement-Lead,      ...
You must have a Tracker Czar    It’s a good idea to have a formal role:Anchor, Scrum Master, Coach, Engagement-Lead,      ...
Random Tracker Tips
There’s always Monday
There’s always Monday...if your iterations start on Tuesday.
Don’t start max-point stories
Don’t start max-point storiesReserved for “OMG” stories.
Never restart an Accepted story.              X   Make a new story or bug.
Turn Chores into Stories if you can
Back-date stories finished last iteration, but accepted later.
Back-date stories finished last iteration, but accepted later.... maintains Velocity calculation.
Assign the customer/verifier the           “requested”... they will get email updates for   comments and delivered stories.
Must-have Labels• blocked            • needs-prioritization• needs-discussion   • suggestion• needs-design• needs-assets
One Big List
Joe’s Personal Point Scale     (based on Fibonacci)
Questions?
Thank You!
Linkage     Joe Moore          Pivotal Labs      Pivotal Tracker       @joem          pivotallabs.com   pivotaltracker.com...
Pivotal Tracker Protips
Pivotal Tracker Protips
Upcoming SlideShare
Loading in...5
×

Pivotal Tracker Protips

2,707

Published on

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,707
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
36
Comments
0
Likes
5
Embeds 0
No embeds

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 of "Pivotal Tracker Protips"

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

      Clipping is a handy way to collect important slides you want to go back to later.

    ×