The problems with having a large Scrum team – say more than 10-11 people (especially when more people are added to the team)
Filed Under Scrum, Team | Posted on March 17, 2010
In the past, when our teams have been experimenting with how to breakup the overall size of the team into Scrum teams, and we were trying to break the teams up into sizes of 7-9 people (excluding the Product Owner and the ScrumMaster). However, since there were times when there was an effort to accommodate [...]
Burndown charts and Scrum – Some issues and problems that people encounter
Filed Under Agile, Problems, Product Backlog, Scrum | Posted on March 15, 2010
Burndown charts are a key part of Srum; after all, what could be better than a chart that shows a well defined path to reaching the end of the Sprint with all the tasks done in the allotted time. The Burndown chart at any point in the Sprint shows a status of where the team [...]
Burn Down chart and a change in scope that impacts the burn down chart
Filed Under Agile, Change, Features, Scope, Scrum | Posted on March 11, 2010
In the previous post (Burn Down Chart), we talked about what a Burn Down Chart is, and how you can use it to get the current status of the project, while not using it as a way of judging the performance of the team. This is because there are many variable that can impact the [...]
Burndown charts – a easy and powerful way to depict progress in the Scrum environment
Filed Under Agile, Scrum, Status | Posted on March 10, 2010
So what is a Burndown chart ? Seems a slightly weird name as compared to other documents whose names are more descriptive. Well, you will find that this name is also fairly descriptive. The burndown chart is a way to show the progress in a Sprint cycle, and differs radically from the milestone based progress [...]
