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 [...]
How to optimize Planning Poker as a part of Scrum and some benefits of the Planning Poker process – Part 1
Filed Under Estimation, Features, Scrum, Sprint Backlog | Posted on February 28, 2010
In previous posts (Details about Planning Poker process), I have explained the process of Planning Poker as a part of how to do estimation of tasks during the Sprint Planning process. In this post, I will go further and post some points about how to optimize the Planning Poker process / make it a success, [...]
Planning Poker and Scrum – a brief introduction
Filed Under Estimation, Features, Scrum | Posted on February 4, 2010
First a question. How many of you have heard of something called Planning Poker ? Not too many of you ? Well, that’s okay; in this and the next couple of posts, you will learn a lot more about what Planning Poker is, what it is used for, and so on.
One of the most difficult [...]
Some tweaks in the Scrum process so as to generate an overall schedule
Filed Under Estimation, Features, Product Backlog, Product Management, Product Owner, Scrum | Posted on January 20, 2010
The Scrum process can seem pretty radical for somebody who has not done this before. If you consider my case, I was used to normal waterfall or modified waterfall, where we would start work on a set of features, move onto more features as succeeding features got done, and so on. However, this resulted in [...]
