This single page describes the full Scrum Framework. It gives a quick overview related to Scrum Master, Sprint Planning, Burndown
Agilo for Scrum - Details
Agilo extends Trac adding the following capabilities:
Real Ticket typing: Trac supports the creation of different types of ticket, but in the end it shows the same fields for every type and makes no more differences. We love the simplicity of Trac, including its great capabilities to be extended ;-) Thanks to the agilo-types plugin Agilo allows you to define which attributes belongs to which defined type of ticket, allowing much more consistent customization

Ticket References and Linking:
Trac allows to hyperlink any kind of ticket, with some markup work and some automation. We wanted to enforce a bit of rules and structure linking between different types of Ticket so that they can better support the defined process. Linking is important, but more important is to define the semantic behind the linking of two different items. Consider the following example: You have a User Story (ticket) and you want to create a set of Tasks (ticket) to work on this User Story, and having the possibility to keep a relation between the User Story and the Tasks, to monitor changes, keep traceability and having a top-down view as well. What about having the possibility to define into the trac.ini that the User Story type of ticket, can be linked to the Task type of ticket, and having automatically the possibility to create a linked Task to a User Story, from the user interface?. To allow this we implemented the agilo-links plugin, which has the following capabilities:
-
Define which links are allowed and which are not. For more detail read the agilo-links plugin description below, as an example consider to allow links from
storytotaskor fromrequirementtostory -
Define which fields of the
sourceof the link have to becopiedto thedestinationof the link when a new linked item is created. For example when creating a Task connected to a User Story, we would like to copy the fieldmilestoneinto the newly created task -
Define which virtual field of the
sourceof the link have to becalculatedusing some operation from thedestinationof the link. For example when looking at a User Story, would be of great help to know how muchtotal remaining timeis left to complete the Story, based on thesumof the remaining time of all the linked tasks
The [agilo-links] plugin integrates also a new Ticket form, that allows to visualize the tickets in a more clear way, and:
- Adds a tabbed view for each type of Ticket, separating the Editing pane from the Viewing pane, allowing users interested in "reading" information to do it very fast, as well as allowing users without TICKET_WRITE permission to view the tickets
- Adds the possibility to hide and collapse the history of tickets, that after a while is becoming a very long list, and force you to scroll the browser page up and down, to make every little change
- Adds the possibility to navigate back and forward between all the linked tickets, adding in the Editing pane the necessary fields to create, delete and search for tickets to be linked

Sprint Data and Burndown Chart: What would be Scrum without it? We implemented a couple of plugins (agilo-scrumdashboard, agilo-sprint-backlog and agilo-charts) that allows an easy an simple implementation of the Scrum process, and particularly supports you in:
- Maintaining the Product Backlog updated, and sorted according Business Value
- Having a quick glimpse on the Selected Product Backlog for a specific Sprint
- Accessing the Sprint Backlog and the Burndown Chart for a specific Sprint
- Viewing some statistics on the current team workload and number of tickets planned and closed

