You are here

Blog: April 2012

Why use avatars for scrum team members? (Part 2)

In my prevous post on this, I mentioned a few reasons why using avatars is important, both in Scrum terms as well as in helping build and meld the team.
One of the many problems a Scrum team has, especially new teams, is irregular burnup across the iteration. It is also not uncommon to see a very slow burnup (almost flatlined) across the iteration and then a steep burnup curve during the lsat few days. This is exactly not what we want, burnup like this puts undue pressure on everbody.
What you then find is:

Iteration Zero (Before you start your engines)

There is some controversy about this.
One view is that it is a misused phrase used to describe the planning that occurs prior to the first sprint, another is that it is that work that is needed prior to initiating development work, still others claim that this pre-work part of the project charter.

For a team new to agile, and a lot that aren’t, you need some space between the project charter, all the budget work and goals and vision nonsense to do some work before the start of development and all hands on deck. This is what most people refer to as iteration 0.

Iteration Zero (Before you start your engines)

There is some controversy about this.
One view is that it is a misused phrase used to describe the planning that occurs prior to the first sprint, another is that it is that work that is needed prior to initiating development work, still others claim that this pre-work part of the project charter.

For a team new to agile, and a lot that aren’t, you need some space between the project charter, all the budget work and goals and vision nonsense to do some work before the start of development and all hands on deck. This is what most people refer to as iteration 0.

Subscribe to Blog: April 2012