User Guide
Expected ticket flow
As all ticket types in Trac have the same workflow at the moment, the below description concerns both Stories (scope elements) and Tasks (work items).
The following is the expected sequence of steps:
- Once the ticket is created, the milestone is defaulted to none. Thus, the tickets get either into Product Backlog or Sprint Backlog (depending on its type: whether it is Scope Element or Work Item)
- The backlogs need to be regularly reviewed and estimated. So, once unestimated ticket is in there, the next step would be to estimate it (set up Business Value and/or Complexity depending on ticket type). It is expected that Complexity may be estimated by any team member, while Business Value is defined by Product Owner (though it is not enforced)
- Once the ticket is estimated, either Product Owner assigns the Story to the Sprint, or Team Member accepts the Task into the certain Build.
- Steps 1-3 do not change the initial status of the ticket. After this the ticket leaves it's own lifecycle as per Trac configuration.
- Once the ticket reaches its final step, the points need to be reviewed once again. Those Stories where total Complexity of referred tickets is more then estimated beforehand Complexity of the story, the due lessons should be learned, noted as the comment to the Story and then the Complexity points adjusted.
