mustERkennung … stuff about patterns and their recognition

it’s the new board

with 3 comments

On friday I finished the preparations for our next sprint. Not enough to mention, but …

Let me sketch the circumstances: In our BI environment based on SAP BW we are currently bound to a 2 month release cycle, which shall be expanded to 3 months. I started agile program management with pieces of scrum nearly 8 month ago, so we finished the so called fourth sprint on friday. All things finished and tested and delivered are put into a big envelope and saved for generations to come.

In a retrospective meeting the team decided to plan acitivities in more detail (move from days to hours) and with a focus on the high priority tasks / stories. Additional we split the formal release into different sprints of 3 weeks duration.

So, in combination with the ideas regarding the Scrum Board at Olli’s blog I set up the new board, which now contains:

  • Some rows containing the top stories of the varoius business lines we are serving; the first row is reserved for Incidents, which must be treated with highest priority
  • First column with the story and the identified activities
  • Second column with the activities the team is working on
  • Third column with things done
  • The final fourth column now contains some information like burndown chart and a legend of activite card colors

The old board was different: First column reserved for the name of the business line, no content at all, second one for the plan, 3rd one for the current activities and 4th one for things testable. The final 5th column contained the activities / tasks released by the business department.

Then we introduced colors. The first idea was to have a color per team member to group and assign tasks. I argued that with such a logic we loose the abillity to re-priorize the tasks and help each other. Now we have colors for different aspects:

  • Yellow for technical stories
  • Green for business stories
  • Blue for activities
  • Orange for 3rd party activities we triggered
  • Pink for Incidents

It may be bad manner to be off at sprint start, but I’m sure they will do well without me. I’m really looking forward coming back in one week and see the progress on the new detailed level.

Add on: WordPress automatically sugested comments / related sites, so I found or better were forced to:Task Boards: Telling a Compelling Agile Story on a page about agile tools. I think I add the site to my blogroll.


Written by Rayk Fenske

March 14, 2009 at 9:10 pm

Posted in Uncategorized

Tagged with ,

3 Responses

Subscribe to comments with RSS.

  1. Looking forward to your results and experiences.


    March 15, 2009 at 8:31 am

  2. Do you have before and after pics?

    Kevin E. Schlabach

    March 16, 2009 at 4:32 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: