You are on page 1of 19

Development

Pivotal Tracker Workflow


Screenshots

© 2010 Peter Saddington


Pivotal Tracker Project Home Screen

© 2010 Peter Saddington


Adding a New Feature / Bug

© 2010 Peter Saddington


Selecting Feature / Bug

© 2010 Peter Saddington


Selecting a Story Label

© 2010 Peter Saddington


Completing a Feature Story

© 2010 Peter Saddington


Example Story

© 2010 Peter Saddington


Adding Tasks

© 2010 Peter Saddington


Adding Comments

© 2010 Peter Saddington


Completing a Bug/Issue

© 2010 Peter Saddington


Example of a Bug/Issue

© 2010 Peter Saddington


Attachments and Screenshots!

© 2010 Peter Saddington


View After Saving Story

© 2010 Peter Saddington


Stories to Backlog

© 2010 Peter Saddington


Backlog to Current

© 2010 Peter Saddington


Current “States” of Development

© 2010 Peter Saddington


Tracking In-Progress Stories

When a developer begins work on a story people will


be notified of the changes and progress via email.
If you would like to see all changes to all stories
within the Customer Service Project
 Go to My Profile >
 > Receive Comment Emails “For All Stories” [Dropdown box]
 You can also change other options in My Profile

© 2010 Peter Saddington


Meetings for Development with PT

WE GET REQUIREMENTS (DETAILED) FROM BIZ


Story Carding (1-4hrs)
 As a team, build out the stories and tasks
 All stories and tasks will be completed from requirements
document
IPM (Iteration Planning Meeting)30-1hr
 As a team, break out stories into iterations (sprints) with
release markers
 Estimate release schedule and goals

© 2010 Peter Saddington


Questions?

© 2010 Peter Saddington

You might also like