Clik here to view.
Agile Estimation:8 Steps to Successful Story Point Estimation
In Story sizing, team does a comparative analysis between all of the stories for the project. Let’s look at the typical story sizing steps. For each story to be sized, do the following as a...
View ArticleClik here to view.
Agile Estimation: 9 Reasons Why You Should Use Story Points
A common question about estimating with points is, “Why Points? Why not in Days? Finally I need to do planning so I need to convert points to Days. Why this additional level of indirection? In-fact I...
View ArticleClik here to view.
Story Points and Man Hours – When To Use Them and Why?
The debate about why story points why not time goes on wherever I go for conducting coaching workshops. Hence I thought of sharing few more thoughts today. Previously we had sizing techniques like...
View ArticleClik here to view.
Planning Poker is NOT about Agile Estimation!
One of the popular mechanisms to estimate story points as a team is planning poker exercise. It’s an awesome technique but it may become a challenge for some teams. For instance, a team estimates...
View ArticleClik here to view.
Our Sprint Velocity Never Seems to Change. We don’t Know Why!
Story point is about size, not about time. At best it can be about a range of time but not about absolute time. In many teams people map story point directly to time and may get into vicious cycle...
View ArticleClik here to view.
All About Story Points and Agile Estimation Series
Lots of Scrum teams have been using story points and planning poker for relative sizing. However, this is one of the concepts like pointers in C, which troubles most of the teams and they all have...
View ArticleClik here to view.
What is a Story Point?
Story point is a unit of measure of estimation for the overall size of the work that will be required to fully implement a user story. Story point has no direct relation with time even though people...
View ArticleClik here to view.
Who all should Participate in Story Point Sizing Activity?
There are folks who may be moving from waterfall to agile approach. They in general divide the estimates in terms of development estimates and testing estimates. These estimates are separately done by...
View ArticleClik here to view.
How to do Story Point Sizing with Planning Poker?
Story point estimation is all about relative sizing. In order to compare the amount of work of one story to another, we need to identify a base story in order to define the base story point size. It...
View ArticleClik here to view.
How to Forecast the Number of Story Points in a Sprint?
Question – Estimation in the form of anything else other than time may be helpful, but we can’t use it to answer questions about when a project shall be delivered. In our previous post, we saw that...
View ArticleClik here to view.
Never Map Story Points with Hours
As long as a customer trusts the team, whatever way you size or estimate or don’t estimate, doesn’t really matter. But that doesn’t happen very often. Whenever a customer questions about team...
View ArticleClik here to view.
Should We Count Story Points for Unfinished Stories?
Unfinished stories is a smell and the root cause in general may lie somewhere else. Why don’t we try to fix the root cause first as much as possible? This generally happens when a team practices...
View ArticleClik here to view.
Story Points for Bugs or Defects
Generally, a sprint backlog contains bugs as well apart from user stories. In these situations, a common question is should we assign story points to the bugs. If the team does not assign a story...
View Article