What Is the Life Cycle of a User Story in Tracker?

  1. Create a new story in the Icebox: Describe the story from the user's perspective.  Supporting files (mockups, spec documents, etc.) can be attached to the story.  The client is the requester of the story, but there is no owner until work begins.

  2. Estimation: Singlebrook will give the story an estimate.

  3. Approval: The client can drag the estimated story from the Icebox to the Backlog to give us approval to work on the story. Stories in the Backlog can be prioritized by dragging the higher-priority ones to the top of the list.

  4. Work begins: Developers begin work starting at the top of the Current column and then flow into the Backlog column if the stories are finished ahead of schedule. When a developer starts a story, they automatically become the owner of the story. 

  5. Clarification: Singlebrook and the client will discuss the story as necessary to make sure we're on the same page. This can happen on the phone or by commenting on the story in Tracker, in which case an email will go out to let everyone involved know that there's a new comment. The story's description will be updated as necessary to reflect our shared understanding of the work to be done.

  6. Finished: When we're done working on the story, we'll mark it Finished. Since we do most of our development on our own workstations, the client won't see the changes until we roll them out to your staging site. We'll Deliver the story, and the requestor will get an email asking them to review the work.

  7. Acceptance: After reviewing and testing the work, the requestor will Accept or Reject the story. Rejecting a story is fine, but the client should make sure to leave comments explaining why the story was rejected. If the story's been Rejected, we'll Restart it, make adjustments as necessary, and return to the “Finished” step.