Welcome to Agilo for Trac Pro 1.3
This is a Demo project, prepared for the sole reason of giving you and idea on how the software handles specific Scrum related practices. The project is in rapid evolution and is used already in many production environments. Any feedback is highly appreciated, so please send any sensible comment to agilo+feedback@… or participate directly in our Google Group http://groups.google.com/group/agilo/ :-)
If you are looking for help, please consult our Agilo documentation first.
Before you start clicking everywhere :-)
In order to login, you need to have an account. You can obtain this by registering here! After the registration is complete, you will have an account created with both the rights of Scrum Master and Product Owner. After logging in, you will see all the actions you can perform on the left side pane, as well as a quick access to the most common links. The toolbar will also change showing all the features :-)
Agilo is an extension to Trac that adds some important functionality, for details please have a look at the HowTo page.
Get Started... What's next?
After having successfully registered, and logged into the system, you should see a menu named Dashboard. This is a quick access to the Scrum functionality. It contains an overview of the sprint and milestone that are currently active.
You were granted the Scrum Master rights, which will enable you to edit the Sprint Backlog and change the Burndown Chart in real time, for example when you are at the Daily Scrum.
In the Sprint Backlog view. you will have the chance to see the Tasks in progress as well as who is doing what. Once the team members will commit themselves to complete a specific activity, you can assign them (also as multiple resources) to a that Task. If you will not assign an owner to that task, Agilo will promote the first resource in the list of resources to owner.
The Sprint Backlog is grouping tasks by User Story so that it will be easier to get the dependencies right and see which user stories have been completed, and can be set to complete. Now the backlog allow you to easily sort items by multiple keys as well as via Drag & Drop.
From the dashboard you'll find the possibility to create tasks for the next Sprint, as well as the possibility to add new Product Backlog items.
In the Dashboard you'll also find the access to many Backlogs created specifically for Scrum, one is the Sprint Backlog for a specific Sprint and the other is the Product Backlog (that you will find also in the left sidebar for quicker access).
Quick Start Guide
To start using Agilo you normally need to build a Product Backlog, which is one of the most important artefact in Scrum, a Product Backlog in Agilo is build using Requirements and User Stories. You can also use only User Stories and customize the whole tool to handle your own type of tickets. The Product Backlog is the list of Requirements and related User Stories prioritized by Business Value that have not yet been assigned to any Sprint (a Milestone in the Roadmap). You can also configure the Product Backlog include planned items. We suggest for the purpose of a release plan to use a Release Backlog which will contain all the items planned for every Sprint in that release, also when closed.
To create Requirements, as a product_owner go to the Scrum Dashboard and click on New Requirement or click on the left side bar, do not set the Milestone property, you normally do not need to set the Milestone on a Requirement, because the Team will commit to User Stories. You can set a Milestone if you want to plan a Requirement for a specific product release, normally the Product Owner does that once the teams are good enough in self organizing and have reached a constant velocity, so that based on estimation the Product Owner can guess what will enter into a Release... but this is a very long story...
Once Requirements are in, you can click on the Edit tab of each Requirement and use the link "Create a Referenced User Story" to associate User Stories to each Requirement -- or use the plus icon on the Requirement in the backlog. User Stories represent a way to describe the interaction between a type of user of your system and the system itself, they are a kind of functional specification if you wish. User Stories are great for their simplicity, in order order to make them effective for the development team remember to write Acceptance Criteria too.
Now you can look at your Product Backlog and use this at the Sprint Planning Meeting to present to the Team each and every User Story. Normally we use a projector or a big screen, introduce the team to the bigger picture explaining the whole Requirement (the need that have to be fulfilled, you can click on it from the Backlog Report) and dig down into each User Story, so that the team has an overview of the whole Requirement.
Once the Team has chosen a Baseline, using the Planning Poker technique they estimate one after the next as many User Stories as will fit into the first half of the meeting (time-boxed to 4h, first half is 2h normally). The product_owner can update estimations on every User Story, switching to the Edit pane and entering the Story Points estimations in the appropriate field, or directly in the Product Backlog. When the Team completed the initial estimations, it will give an initial commitment in term of which Stories they think they would be able to successfully implement and release in the next Sprint. At this point the product_owner may set the Sprint property to the next Sprint for those chosen Stories (this can also be done directly in the Product Backlog, keep in mind that once the stories are planned they will disappear from the Backlog).
Before starting the detailed planning make sure the sprint is well defined and the capacity for that sprint set and updated.
1) Go to Roadmap and chose the Milestone related to the next Release, and than the right Sprint, or create a new one
2) Set Start and End or duration for a new sprint, keep in mind that agilo will normalized the start and end date to fall into a working day (we know you also work on weekends but it is not a good practice ;-) )
3) Go to the Scrum Dashboard, the Sprint shown in the "Sprint Backlog for Sprint" should be the one you just set, and so the charts that will eventually display on the Dashboard will be related to the next due Sprint
4) At this point in the Sprint Backlog you should see all the Stories, with the related Requirements, that have been committed for this Sprint by the team
5) Now the Scrum Master can help the Team in breaking down every Story into Tasks, from the Sprint Backlog view he can click on a specific Story, go to the Edit pane, and use the "Create Referenced Task" to create all the needed Tasks for that Story. We normally do not estimate at this point, but we do set estimation directly in the Sprint Backlog view, once all the Tasks for a Story have been defined, this helps the team in having an overall view when estimating. The Scrum Master can enter the estimated time in Ideal hours (you can also do in ideal days, but this demo server is configured with hours) for each of the task, save the Backlog by pushing the button "Save" on top of the Sprint Backlog.
6) There is also a button "Confirm" that normally appears only the first day of the Sprint, which is meant to be used to "Confirm" the team commitment once a bit more of detailed plan as been made. Agilo also offer the possibility to automatically estimate the 'User Story Point/Ideal? Time' ratio and calculate the actual team estimated commitment using the remaining story points. This can be achieved selecting one or more stories that the team consider well defined and estimated and pressing the button "Calculate", this will store in the team metrics for the current sprint the 'User Story Points/Ideal? Time' ratio, that will be used to calculate the estimated remaining time. Clicking on "Confirm" will store in metrics the Estimated team velocity, in terms of 'Story Points', the team commitment in terms of committed time, and the capacity for the current sprint. All this information are than shown in the team statistics page, accessible from the menu Team than dig down to sprints.
On a daily basis at the Daily Scrum the Scrum Master while asking the three questions:
- What did you do yesterday?
- What are you going to do today?
- What are your impediments
May ask also how much time each team_member has left to complete its task, and update the Sprint Backlog directly. Each team_member can pick out a Task or more than one (even if you should focus!) form the Sprint Backlog, by declaring it at the Daily Scrum the Scrum Master can assign the Task to that team_member that will have to accept it by going to the Sprint Backlog, as team_member and clicking on the Edit pane of the Task, choose Accept and saving the Task.
All the Accepted Tasks will appear highlighted in orange in the Sprint Backlog view, to help the Team and the Scrum Master in focusing on the most important things, avoiding the Team Members to start too many parallels tasks at the same time. (We will implement a better workflow for agilo types as soon as possible... don't worry)
If you need more advanced tips and tricks, do not hesitate to subscribe and participate to our online User Group: http://groups.google.com/group/agilo
What is Trac?
Trac is a minimalistic approach to web-based management of software projects. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.
All aspects of Trac have been designed with the single goal to help developers write great software while staying out of the way and imposing as little as possible on a team's established process and culture.
As all Wiki pages, this page is editable, this means that you can modify the contents of this page simply by using your web-browser. Simply click on the "Edit this page" link at the bottom of the page. WikiFormatting will give you a detailed description of available Wiki formatting commands.
"trac-admin yourenvdir initenv" created a new Trac environment, containing a default set of wiki pages and some sample data. This newly created environment also contains documentation to help you get started with your project.
TracGuide is a good place to start.
The Trac Team
- TracGuide -- Built-in Documentation
- The Trac project -- Trac Open Source Project
- Trac FAQ -- Frequently Asked Questions
- TracSupport -- Trac Support
For a complete list of local wiki pages, see TitleIndex.