Proposal for using Pivotal Tracker:
- The REQUESTER of a story is responsible for providing criteria to evaluate DELIVERy a story. For code implementation stories, this includes provision of a test.
- The PRODUCT OWNER ACCEPTs or REJECTs a story.
- The OWNER of a story STARTs and FINISHes a story. Owners aren't assigned until the requester can evaluate delivery of a story.
- A story can be in the ICEBOX without delivery criteria, but it must have an requester.
- A story can be in the BACKLOG without an owner, but it must have delivery criteria. A story cannot be in the Backlog until the Product Owner has accepted it. A story cannot be Started until it has been assigned to a sprint.
- A story cannot be in a SPRINT without a requester, delivery criteria, and an owner.
ICEBOX
Stories in the Icebox may not have delivery criteria. They may be rejected by the product owner from the Icebox.
BACKLOG
Stories that have been accepted are moved to the Backlog.
SPRINTS
Stories that have been started must be moved to a sprint. Stories are finished and delivered in sprints.
Pivotal Tracker States
- started
- finished
- delivered
- accepted/rejected
