Scrum & Agilo for trac - A Synergy
The usage model of Agilo for trac is based on the Scrum framework for software development by Ken Schwaber, Jeff Sutherland and Mike Beedle. In order to use Agilo for trac in the way it is intended, please make sure you understand the Scrum framework and know the featured artifacts, ceremonies and roles. You might find also some aspects which are not defined or used in the theoretical Scrum approach. These are based on practical experiences and have proven to be effective and useful. These aspects are marked with our logo.
Agilo for trac & Scrum
Agilo for trac & Scrum
Product Backlog Preparation
At this point do not set the “milestone” property yet, just list the requirements and User Stories, starting from the requirements that from a Product Owner perspective are considered the most important ones.
You may want to create a vision in the wiki and link specific parts of it to requirement tickets. Using the "Edit" tab of a requirement ticket you can add linked User Stories. We write acceptance criteria as a part of the User Story description. Some Agilo’s Users create a ticket type called “Acceptance Test” and link those tickets to the adequate User Stories and Requirements. (You can add/link external documents to every item at any time).
Product Management Board
Sprint Planning: Backlog Presentation
Sprint Planning: Relative Estimation
Sprint Planning: Initial Commitment
Sprint Planning: Detail Planning
The PO can leave now, because the Team gave an initial commitment for the Sprint. The Team starts now the detailed planning with the Scrum Master. The Scrum Master can login to Agilo for trac and open the Sprint Backlog view, where he will find all the committed User Stories, and where the first day of the Sprint is highlighted as today. (Please make sure that the milestone end date has been set, as well as the duration of the Sprint. To do this as a Scrum Master, enter the Sprint Backlog view and set the Sprint duration which will be calculated back from the milestone date). Now the team, with the help of the Scrum Master, starts to dig down into each User Story and creates Tasks by going to the „Edit“ pane of the story and creating a linked Task. The Team goes on laying down as many tasks as needed for the whole User Story. Afterwards the Scrum Master switches back to the Sprint Backlog, where the Team can estimate the remaining time for each task.You can also estimate instantly while creating Tasks, but we have experienced that if the team can have the whole picture, the estimations are more balanced and less reworked. It is all about speed and time box right?! ;-)
Sprint Planning: Initial Burn Down Chart and Final Commitment
Every Day Work
Because Agilo for trac has been build as a tool to support Scrum Ceremonies, we do suggest to update the remaining time of the tasks at the daily stand-up meeting together with the rest of the team. In this way the whole team will have an idea of the progress done and can pick-up very well the Inspect & Adapt process.
Every Team Member can also create Tasks for the Sprint, which are not related to any User Story. If they want to link them to a User Story, they need the Scrum Master to link it to a User Story afterwards.If you need any help for your projects, please don't hesitate to contact us →The agile42 Team