1. 1<br />Pivotal Tracker <br />Getting Started Guide<br />
2. DEFINITIONS<br />Pivotal Tracker <br />Story-based project planning tool from Pivotal Labs.Based on agile software methods<br />Aims to maximize team velocity rather than points scored by individuals<br />Projects<br />Engage, Distro, Business, Operations, Backend (based on teams)<br />Iteration<br />Time span of 1 working week is called an iteration.<br />2<br />
3. 3<br />DEFINITIONS<br />Story is a basic unit in pivotal<br /><ul><li>Represents small, concrete deliverable for a project.
4. Easily comprehensible and verifiable.
5. Placeholder for ongoing conversations.
6. Maybe estimated in points.</li></ul>Tasks: <br /><ul><li> To-do list while someone works on a story
7. Task status does not affect overall story status.</li></li></ul><li>LABELS, RELEASES AND CHARTS <br />Labelsare tags, associated with stories. They are used to organize stories. All labels in the project can be seen in the Labels & Searches panel.<br />A Release is a special type of story that represents a milestone in the backlog. Releases may be tied to production code pushes or they may simply represent a group of related features.<br />Charts available in Pivotal Tracker : https://www.pivotaltracker.com/help#whatchartsareavailableintracker<br />4<br />
8. TYPES OF STORIES<br />
9. 6<br />STATES OF A STORY<br />Estimate the story <br />Start Working on the Story<br />Finish the Story<br />3<br />4<br /> Commit SVN & Deploy to Live<br />Verify<br />5<br />
10. ESTIMATION OF POINTS<br />7<br />
11. DEFINITIONS<br />Velocity<br /><ul><li>Average number of points accepted per iteration, based on recently completed iterations.</li></ul>How is velocity calculated?<br /><ul><li>Accepted stories in the current iteration move to the Done panel.
12. Team velocity is a running average of the velocity of the past 3 iterations.
13. Remaining stories are grouped into future iterations based on velocity.</li></ul>8<br />
14. DEFINITIONS : COLLECTIONS<br />9<br />
15. CASE: MULTIPLE PEOPLE WORKING ON SAME STORY? e.g. designer & developer working on a feature (1 story)<br />Designer gets the story first & estimates in consultation with dev<br />After finishing design tasks, designer assigns the story to dev<br />Developer finishes dev work, deploys feature and updates story<br />Story can be accepted once the feature is deployed to live.<br />10<br />
16. ROLE OF PRODUCT MANAGERS / PRODUCT OWNERS / TECH LEADS<br />Put all ongoing work into Pivotal <br />Current should contain stories being worked on this week.<br />Accept/Reject stories ASAP <br />Before weekly meeting, get everyone to update current status of stories<br />Delete out-dated stories from backlog or icebox.<br />Next week of backlog is the highest-priority stuff. <br />Estimate stories yourselfto prioritize it in backlog<br />Make sure next 2 weeks of backlog are estimated. Get estimates from engineers if possible, otherwise fill in with your own estimate.<br />11<br />
17. HOW TO REPORT PIVOTAL STORIES IN EOD?<br />TODAY<br />1) Fixed & Deployed http://www.pivotaltracker.com/story/show/3480662 <br /> Reconcile the different channel typesChangeset: http://jboutelle.trac.cvsdude.com/slideshare/changeset/18670<br />Fixed and Committed http://www.pivotaltracker.com/story/show/3735705 <br />Refactor the channels code <br />Changeset: http://jboutelle.trac.cvsdude.com/slideshare/changeset/18670<br />Worked on http://www.pivotaltracker.com/story/show/3735705 <br /> Analytics front-end refactor , 40% complete<br />TOMORROW<br />Work on http://www.pivotaltracker.com/story/show/3735705 <br /> Profile redesign for PRO<br />12<br />