Arpoh

Generating burn down chart using Arpoh !

arpoh — Tue, 29 Sep 2009 13:03:20 +0000

Burn down chart is the most powerful aspect of SCRUM. It gives us the complete information about the sprint;

On day 1, When the sprint starts, the total effort required to complete the sprint is shown on the ‘Y’ axis.
As on the last day of the sprint, the effort required to complete the balance activities will be ideally Zero.
These two points are connected by a straight line, which is the ideal curve on the sprint burn down chart.
On the activity “post it’ there are three columns; “EP – Effort planned, ER – Effort required, EA – Actual effort”
EP- effort planned is updated during the sprint planning meeting
ER – effort required to complete the balance work is updated on a day to day basis. If you can decide on a cut of time for this with the team, you can be sure of the completeness of the data. When the ‘ER=0″, the activity is done. In another words, for the completed (done) activities “ER” will be equal to Zero.
The burn down chart takes the values of ‘EP’ and ‘ER’ and plots the sprint burn down chart.
It will be useful, if you capture the ‘EA – Actual effort’, when an activity is done. This will help to develop a correlation between the story points and the effort over a period, resulting in better estimation.

Arpoh effect -1

arpoh — Fri, 18 Sep 2009 00:36:14 +0000

This video shows how easy it is to create and maintain the sprint board and the sprint burn down chart using Arpoh. The video explains the following steps;

1) The user logs into Arpoh.com using his user id and password.

2) Clicks on the ‘new sprints’ button, and enters the sprint name, start date and end date.

3) Creates the features of the sprint. Using Arpoh, the features can be either created or you can just drag and drop from the product backlog.

4) Once the features are created, then it is time to create the associated tasks required to build those features. This is done by clicking on the create task button on the feature.

5) Team members can volunteer for the tasks, just by clicking on the ‘volunteer’ link on the tasks. When the real work starts on the task, it is dragged into the ‘Being done’ column, and once it is done – it is dragged into the ‘Done’ column.

6) Every day, the ‘required effort RE’ is updated by the team members, and from this the burn down is generated.

7) One can change the colours of the post its as well. So within the team, you have the flexibility of using some special colours to indicate some special tasks.

Enjoy Arpoh, You will not need anything else.

Before Arpoh!

arpoh — Thu, 17 Sep 2009 22:17:13 +0000

What is arpoh?

arpoh — Wed, 16 Sep 2009 09:24:20 +0000

We use SCRUM for managing our internal projects, and we do help our clients to implement scrum among their teams. Our working locations are decided by our clients. So we needed a scrum board which can be shared across locations. That is where everything got started. Since most of our clients have multi location operations, very often the product owner sits away from the team, and arpoh fitted in well there as well.

During scrum implementation assignments, sometimes SCRUM initiatives takes off well, and looses it’s steam half way through. By adopting arpoh in those environments, it was a kind of re assurance on the right scrum process implementation. So it all started and happened as internal requirements of ours and our clients.

Now we are opening it up for the entire scrum community, so that they get the best out of their work. We do get feature requests from the arpoh user community, and most of them find a place in our product backlog!.