This guide will walk you through step‐by‐step on how to use Agilebuddy.
For more help please visit
or email email@example.com
Logging in to Agilebuddy.com
Every company receives its own url for logging into Agilebuddy. Enter your url into any of the supported browsers (Firefox
and Safari recommended) and click enter.
In the example below, the url is “yourcompanyname”.agilebuddy.com. Enter your company’s url and click enter.
The Login screen appears
Once logged in, you will be presented with your home page, the default landing page. The
ﬁrst Pme you login, this page will be empty.
The home page is designed to show you all items across all projects including, User stories
(requirements), Tasks, Bugs and Blockers assigned to you.
Note: The ﬁrst person to signup will be the default administrator of the site.
Note: It is recommended that once you have products
deﬁned in Agilebuddy that you choose the product you
want to work with in the product chooser. (top right)
Here’s an example of a fully populated home page, once there is data entered into the
InformaPon is stored in Agilebuddy according to the following hierarchy:
Feature User story Tasks
A feature is deﬁned by one or more User Stories and a User Story is deﬁned by one or more Tasks. Features
are the headers in the rows by default. User Stories are all numbered and appear beneath each feature.
Tasks are indented under each User Story.
Step 1: First you’ll need to deﬁne a new product (or project), Release and Sprint.
NavigaPng to your company’s product plan page with your mouse, click on Track
menu item and then select All Products.
This takes you to the Product plan page.
Product plan page
The product plan list all acPve products (or projects) in your company.
This is designed to show high level project status informaPon to management.
Step 2: Deﬁne your company’s ﬁrst product.
With your mouse click on Create Product
Note: Any Pme that you create an item, a pop‐up message box appears at
the top of the page to let you know that the item was properly created, and
gives you opPons to navigate to its page by clicking on one of the links
provided in the message box.
Click the “x” to close the
Link to go to the items
Click on the new product in the
Clicking on the new product in the Products table takes you to the
Product page, which is iniPally empty.
The Product page also displays the Product calendar along with all Product
milestones, the Product backlog, list of Releases, Product bugs, Shared
documents uploaded and applicable at the Product level, a list of Product
features, and the AcPvity log for all product interacPons.
Step 3: Deﬁne the ﬁrst release
1: Click Create Release and enter
appropriate informaPon and Click Save
Or, navigate with the Track
menu to the Release page as
The release page displays the Release backlog, the Sprint table which displays a
list of IteraPons (Sprints) which is iniPally empty. Here is an example of a fully
populated Release page:
Step 4: Next, Deﬁne the ﬁrst iteraPon or sprint
1: Click Create IteraPon and enter
appropriate informaPon and Click Save and
Clicking Save & Close will display the following on
the Release 1 page:
Click on Sprint 1 in the
Sprint table to take you to
the Sprint page
The Sprint page contains all the informaPon necessary to track the Sprint.
The Sprint page and Home page will be the pages that most people will
be working on day to day.
Note: Agilebuddy does not limit the number of Sprints you can have
The Sprint page, contains the Sprint Calendar, the Burndown chart, the
team chart, the Sprint backlog, the Sprint bugs list, the Sprint Blocker board,
Shared documents for the Sprint, the AcPvity log for all Sprint acPvity and
the Team member list (for assigning team members to the Sprint).
IniPally the Backlog, Bugs list, Burndown, Team chart etc. will all be empty.
Here is an example of a fully populated Sprint page:
Step 5: Adding Team members 1: Click on
Click on AdministraPon to open the AdministraPon
2: Click “Create User” to add new users to
Clicking create user opens the Create New User dialog box
Enter appropriate user information.
Then click Save & Close.
Step 6: Assigning Team
members to Sprints 1: Click on Team tab
2: Click Show all Users
Users already assigned to a sprint
appear in bold font.
3: Click on the “+” sign alongside
the user you want to add to the
Once you have added users to the team by clicking “+”, Team members will
appear in the Sprint Team chart as follows:
Team member hours
Note: Hours remaining for each team member is shown in the Team chart.
Managers can quickly see which team members are over‐burdened.
Product and Release Backlog
Scrum deﬁnes two types of backlogs:
• Product Backlog: for tracking all user stories (requirements)
• Sprint Backlog: for tracking all user stories and tasks
The Product Backlog is the Product owner’s responsibility and the Sprint
backlog is really the team’s responsibility.
Agilebuddy implements the Product backlog at both the Product level, and
Release level. These are really the same thing, except that the Release
Backlog only show items in it that are planned for the speciﬁc release you’re
Step 7: Navigate to
the Product backlog
by clicking on Track,
then “My First
Clicking on the product link in the track menu takes you to the
Product page. The product backlog is displayed by default on the
Product page. Here is an example of a fully populated Product
Click on headers
Backlog tab selected grouping
The Product backlog is paginated. Items on the page can be grouped by Feature,
Size, Release, IteraPon, Business Value, Business ObjecPve, Risk, Status and
Date. Clicking on the headers will change the grouping. providing you with a
variety of sort opPons.
The Product backlog tracks features and user stories for a parPcular product (or
project). The blue lines represent features and the uniquely numbered items
below represent user stories in the system.
Product Backlog AcCons
Show details Delete
Users can perform mulPple acPons on each item in the backlog. E.g.
Show details, Edit, Delete, Add a=achments, Add comments or
Complete/Close User Stories
User Story Details
To see the Details of a User Story (And similarly for bugs, tasks etc, click on the
AcPon: Show user story details
User story Activity
Step 8: Adding features and user stories
Step 9: Adding tasks
There are two ways to create tasks in Agilebuddy. Direct
via the Create menu, or using the Create task acPon in the
1. Via Create menu
Choose a Story for
which this task is
Enter hours required
to complete the task
2. Via the AcPons on the Sprint backlog
Click “Add tasks to this
Note: You can only add tasks to the Sprint Backlog. Not
the Product or Release Backlog.
Step 9: UpdaPng the daily esPmates
OpPon 1: In the Sprint Backlog, click on edit link in the “Hours Lec” column.
Click on edit and
enter hours left for
your tasks daily
Step 9: UpdaPng the daily esPmates
OpPon 2: Or, from the Home page, Click edit link in the “Hours Lec” column.
Click “edit” and
enter hours left
Start, stop and update tasks using the AcPons provided
Start a task. This
sets the status to
Stop a task. Tasks
can be paused or
Edit or update
tasks by clicking
the edit action
Note: Task management can be done on both the Sprint Backlog page
or the Home page.
When a task is stopped, a popup appears giving you the opPon to
pause, re‐open the task, or close it and enter in your actual hours, if you
Stop work re‐opens
(pauses) the task
Assign tasks by
clicking on the
assign action from
tasks by clicking
the home page
on the assign
Assign tasks on
the create task
Or assign Enter
tasks on Task in
Step 10: View status on the Sprint burndown chart.
There are 3 charts presented on the burndown. The green line shows the Actual team
burndown in hours. The Grey line represents the target velocity in order to complete
all tasks within the designated sprint Pme. The blue line represents the average
velocity for the team over the course of the sprint and is a “best ﬁt” curve of the
Comments appear as a label in
blue next to the text.
Mouse over the comment label to see all team
Step 11: Keep everyone informed by commenPng on items in the backlogs.
Enter your status and
post for all to see
Step 12: Casually inform team members of
what you’re doing and keep everyone in sync.
appear in the
status feed on
the home page.
Agilebuddy provides single click story point esPmaPng!
Agilebuddy supports esPmaPng in story points or ideal hours or days. It is
important to note that you are consistent, so once you start with Story
Points, stay with story points.
In the ﬁrst version, Agilebuddy only supports one esPmaPng scale –
modiﬁed fabernaci (in accordance with most Agile gurus).
i.e. 1, 2, 3, 5, 8, 13, 20, 40, 100
Agilebuddy provides a unique interface for relaPve esPmaPng – which is
the Agile way of esPmaPng. The interface therefore provides a means for
easily comparing stories to be esPmated with stories that have already
been esPmated. According to researchers, relaPve esPmaPng is a=ributed
to far more accurate esPmaPon.
Step 13: Click on Estimate and
select either the product or
release backlog to estimate.
List of recently completed
user stories that have already
Click edit box to
select the story
points to assign
Step 15: Plan releases and sprints. Agilebuddy supports both release and
sprint planning. To get to planning click on Plan then select a release, or
sprint to plan
Select the Sprint
Plan user Add stories until
stories or bugs you reach the
into sprints teams target
velocity Remove user
stories by clicking
on the unscheduled
Add user stories to the current
sprint by clicking the schedule