Agile Estimating and Planning

This is a pretty good video about Agile estimation and planning. I recommend it is worth a watch. Its very interesting at the start where lots of people in the web conference put in there comments about planning.

And there is a great point made at the start of the video. That goes something like this – ‘At the start of a project when we know least about it, why do we plan so much!’ This is why Agile emphasises managing change over planning.

The video is presented by Sally Elatta, president of Agile Transformation Inc

Agile and Story Points

Below is a good video on Story point Poker Planning:


If you are not sure what a ‘story point’ is in Agile, the video above will give a great overview and also the links below give a good explanation. Basically it is a way to estimate how difficult or easy a task / story will be in the project that is being worked on.

The article where the link above goes to is written by Vibhu Srinivasan

The article where the link above goes to is written byVikas Hazrati

Agile Planning Board (Scrum)

Below is a simple way to understand the differences between the planning terms in an Agile Scrum planning board. It’s also worth noting that these titles are not set in stone and can be altered to what works best with you and/or the team. For example ‘working’ could be defined as ‘in progress’ and some teams may not see the point of having a done section in the planning board.

Product Backlog > A prioritized list of work for the entire product. E.g., feature 1, feature 2, etc… (This may not appear on the board as it will be the initial wishlist of the product that is being made / developed).

Release Backlog > A subset of the product backlog that you are targeting for completion for the next or first release. E.g. feature 1, feature 2.

Sprint Backlog > A subset of Release backlog through a set of detailed tasks/user stories. E.g., feature 1 – (task 1, t 2, t 3)

Working On > When team members take a task/story, they add it to this column, to show everyone what they are working on.

Done > Work that is completed.

Below is a link to a photo of an Agile Scrum planning board that has its own set up.

Post written by me (Chris Mitchell) 🙂