- 1. INTRO TO TRACKER A simple, story-based project planning tool
that allows teams to collaborate and react instantly to real-world
changes. JOANNE WEBB Manager, QA + Customer Support
[email protected]
2. IN A NUTSHELL AFTER SIGN UP HOW TRACKER WORKS WHATS NEXT FOR
MORE WELCOME TO TRACKER 3. IN A NUTSHELL 4. Is a shared to-do list
for software development teams Was originally built to support and
encourage the Pivotal Labs software development process Small teams
with collective ownership Highly involved product owner and
continuous feedback loop Pair programming, test driven development
TRACKER 5. Software development consultancy, across US and in UK
Hundreds of clients/projects, from startups to enterprise Focus on
transformation via delivery and co-development Technology and
vertical agnostic, its about the how (The Pivotal Way) PIVOTAL LABS
6. AFTER SIGN UP 7. Accounts in Tracker are separate things from
personal user logins Your login is always associated with you -
your email address, username and private password Your login can
own one or more accounts, or just be a member of projects in
someone elses account An account is eectively a container for
projects ACCOUNT VS. LOGIN 8. When you rst sign in to Tracker you
land here: DASHBOARD 9. TRACKER: ORIGINAL + NEW ORIGINAL BETA 10.
HOW TRACKER WORKS 11. 1. Provides a birds-eye view of project 2. Is
a prioritized list of work (stories) 3. Groups list of work
(backlog) into segments of calendar time (iterations) 4. Predicts
progress based on historical performance (velocity) 5. Fosters a
simple process, continuous feedback loop AT ITS CORE, TRACKER
VELOCITY ITERATIONS PRIORITIZED STORIES 12. PLANNING WITH STORIES
In eective planning you Take a large project and break it down into
manageable steps to complete it Allow focus on completing the next
priority in the list See progress and the big picture 13. FEATURES
A feature story describes work that results in direct value to the
teams customer For example: As a shopper, I can add an item to my
shopping cart, so I can purchase it later Search for products
should take 400ms or less Stories should be as small as possible,
while still veriable 14. ESTIMATING Features are estimated via a
xed point scale: Powers of 2 1, 2, 4, 8 Linear 1, 2, 3 Fibonacci 1,
2, 3, 5, 8 Custom A point is a team-specic metric representing the
eort it will take to implement a feature (considering risk) 15.
CHORES A chore is a story that is necessary but its value to the
customer is indirect For example: Setup new domain and wildcard SSL
certicate for test environments Evaluate tools for system
troubleshooting Chores can represent technical debt, and/ or points
of dependency on other teams Chores are not estimated, as they do
not contribute business value directly 16. BUGS A bug is a story
representing a defect, that may be related to a feature story Bugs
can be entered for feature stories that have already been accepted
Bugs are also not estimated 17. STORY WORKFLOW 1. Customer / PM /
PO prioritizes stories in backlog 2. Team discusses and
collectively estimates each story 3. Developers start next
available story in current or backlog 4. Developers check in code
to nish story 5. Team pushes code for new feature to demo/test
environment, and delivers stories 6. Customer/PM accepts or rejects
story (the feedback loop) ESTIM ATE TEST FINISH DELIVER PRIORITIZE
RELEASE DEPLOY START DEFINE DESIGN TEST ACCEPT ACCEPT REJECT 18.
Pro tips: Tracker is not a replacement for conversations Customers
and developers should write stories together ... because a story is
customer business value + developer deliverable Do design
walkthroughs with support and testers they can help with customer
viewpoint, gotchas and missing pieces Stories are ne-grained and
user-centric Dont start max-point stories they should be reserved
for OMG stories & broken down Never restart an Accepted story
make a new story or bug. Turn Chores into Feature stories if you
can MORE ON STORIES 19. PRIORITY 20 PRIORITY 1PRIORITY 1 PRIORITY
12 PRIORITIZATION Position in backlog is priority Stories are
ordered by business value weighed against development risk Consider
dependencies when prioritizing It's obvious which item the team
will work on next Pro tip: One big list (combine current and
backlog) 20. Pro tips: Weekly iteration planning ... where
customers + developers review + estimate upcoming stories
Development team estimates as a group Play an estimation game The
customer prioritizes stories -- physically! (informed by the dev
team) Anyone can create stories and put them in the Icebox but only
the customer can prioritize them MORE ON PLANNING + PRIORITIZATION
21. Pro tip: You must have a Tracker Czar We just delivered some
stories to accept/reject The backlog is getting low, can you
prioritize some stories? Were confused about that story you added
Were blocked on XYZ because the design isnt nished Can you please
accept/reject those stories??? Its a good idea to have a formal
role: Anchor, Scrum Master, Coach, Engagement-Lead, Customer
Liaison The Czar shouldnt also be coding in the project they own
Owning a project is a lot of work, but makes a huge dierence THERE
CAN ONLY BE ONE OWNER 22. VELOCITY + ITERATIONS Accepted stories in
current automatically move into Done at end of each iteration
Velocity calculated based on average # of points accepted in recent
iterations Future iterations are projected based on current
velocity Velocity can be overridden locally for what if scenarios
Iteration length & team strength can be adjusted for unusual
situations - goal is steady velocity (low volatility) Pro tip:
Back-date stories that were accepted late... maintains Velocity
calculation VELOCITYVELOCITY ITERATION NUMBER TEAM STRENGTH
ITERATION LENGTH OVERRIDE 23. RELEASE MARKERS Represent milestones
in the backlog, such as planned releases Optional target dates,
release marker turns red if they wont he hit (too much scope) Helps
avoid scope creep because impact on milestones is immediate
Progress toward release can be visualized with burndown chart 24.
LABELS Highlight key information Click on a label to see all
stories with that label, or use search Labels can be applied in
bulk Can be used to group related stories or for workow Pro tip:
Must-have Labels: blocked needs discussion needs design needs
assets needs prioritization 25. EPICS Represent coarse-grained
features or feature themes Order independent of stories in backlog,
convey overall big picture priorities Linked to stories via label
Progress bars show story progress and relative size Sharing and
collaboration around requirements and design assets that span
multiple stories 26. WORKSPACES Work with panels from dierent
projects in one view Can set color for each Add any number of
projects Drag stories between projects Search across projects in
workspace My Work across projects Shows stories you are working on
(as story owner) or delivered stories youve requested (as the
customer) Order is based on priority of stories in backlog 27.
WORKSPACES CONTINUED ADD/REMOVE PROJECTS IN WORKSPACE SEARCH ACROSS
PROJECTS SELECTABLE PROJECT COLOR SORT 28. SEARCH Full text search
with support for wildcards/regex, negatives, boolean expressions
Search by specic elds (state, owner/requester, dates) Relative
dates (today, -2weeks), with date ranges (-1w..today) Searches can
be pinned and saved Cross-project search 29. SEARCH CONTINUED
PINNED SEARCH 30. USING PANELS Panels / UI Drag drop to rearrange
panels Choose panel width (xed vs auto) Pro tip: In xed mode double
click panel header to t panels to browser Clone panels
Split/combine current and backlog Layouts Favorite Searches &
Epics 31. PANELS CONTINUED FAVORITE EPICS FIXED OR AUTO PANELS
WIDTH SAVE OR PIN SEARCH DRAG / DROP TO CHANGE PANEL ORDER SPLIT /
COMBINE CURRENT BACKLOG PANEL OPTIONS E.G. CLONE 32. STORY VIEWS +
OPTIONS Hide accepted stories in current Add stories directly to
current, backlog and icebox panels View history Story density modes
VELOCITYADD STORY VELOCITYHISTORY 33. STORY DENSITY Dense: !
Normal: ! Minimal: ! Projector 34. MARKDOWN Use Markdown to add
richer content such as: bold/italic numbered and bulleted lists
code blocks headers images CLICK HERE FOR HOW TO USE
TRACKER-FLAVORED MARKDOWN 35. Email and in-app notications keep you
up to date You can be @mentioned, @mention others and follow
stories You can mute notications from certain projects Notication
options can be found in your Proles Notications Settings: "State
changes relevant to me" provides notications when: A story you
requested is delivered A story you own is accepted or rejected Pro
tip: Make the customer/verier the Requester ... they will get email
updates for comments and delivered stories NOTIFICATIONS 36. IN-APP
NOTIFICATIONS Mark each notication as read Mark all read Reveal the
related story Open your notications into a panel that persists in
your project to have a real-time feed of notications to easily
respond to 37. MULTIPLE STORY OWNERS Keep track of who's pairing or
working on stories by adding multiple story owners. Makes My Work
more accurate For now, it's limited to three, for your dev pair and
perhaps a tester or designer 38. INVITING YOUR TEAM TO TRACKER Add
people to projects by: entering their name and email address
selecting from a list of existing account members via Google Apps
integration Users will receive an email inviting them to the
project 39. Account: Owner - receives emailed receipts, can change
plan, can see/manage all projects Admin - can take over ownership,
can see/manage all projects Project Creator - Can create new
projects, can only see those & any they are invited to Member -
Can only see projects they have been invited to Project: Owner: Can
collaborate, change Project Settings & manage membership
Member: Can collaborate Viewer: Read only Pro tips: The account
owner or an Admin can choose to only allow existing account members
to be added to projects, under Account Settings. A project owner,
account owner or admin can move a project to another account if
they are the destination accounts owner, an admin or Project
Creator, via Project Settings. PERMISSIONS 40. PERMISSIONS
CONTINUED 41. WHATS NEXT Out of beta iOS app updates Android app
Private, on-premises install on Cloud Foundry Charts &
Reporting New & improved integrations 42. FOR MORE Help &
Updates: Beta Overview Recent Updates:
www.pivotaltracker.com/help/recentupdates Help Center:
www.help.pivotaltracker.com Markdown Doc App Bazaar Integrations
API Doc System Status: status.pivotaltracker.com Support:
[email protected] Tracker Blog:
www.pivotaltracker.com/community/tracker-blog/ Follow us on Twitter
@pivotaltracker
