CSM Forum Banner

How to define task hours with story point

Discuss PMI-ACP® doubts, tips and lesson learned. Be agile with iZenBridge
yerdogan
Posts: 2
Joined: Fri Apr 01, 2016 8:53 am

How to define task hours with story point

Postby yerdogan Wed May 17, 2017 12:00 pm

Hi,

Following explanation is taken from Mike Griffiths PMI-ACP Prep Premier Edition, Page 220:

"Teams should own the story point definition:
Story point sizing being used on the project should be created and owned by the team. For example, the team can decide 1 story point equals the effort involved in creating a simple screen, or that 1 story point is equal to the amount of work done in an ideal day (with no interruptions for meetings, e-mail, etc.)..."

My questions
1. Can team team compare other user stories with this story?
2. If team says 1 SP for simple screen, then they decide it takes 4 hours. Can we say 2 SP equals 8 hours or 5 SP equals 40 hours?

Thanks in advance!
seema.sonkiya
Expert
Expert
Posts: 1755
Joined: Fri Jul 11, 2014 11:57 am

Re: How to define task hours with story point

Postby seema.sonkiya Thu May 18, 2017 8:05 am

1. Can team team compare other user stories with this story?


Yes, estimating in Story points is all about relative ranking of stories - Story Point estimation is about relative sizing. In story point estimation, we are taking work as one unit. Here is the process:
Take a units of work and compare them with other unit of work – does it look smaller than or look bigger than this? It is about identifying what is small and what is big?
To simplify: Consider we have taken 3 user stories initially to estimate:
1. If we talk about Login Screen, how complex it could be?
2. Now I am thinking of search functionality.
3. There is a third requirement - Report of work posted on the site.

Then team brainstorm - which one is the simplest? Which one is the complex? and which one is average - after consensus you do the ranking - lets say, the team has came up 1, 3, and 5 for the first, second, and third respectively. Now these ranks can serve as base to estimate other stories where you analyze relative size of stories from these base stories and identify their estimates in story points.
For example - I am talking about downloading of job posted - then team brainstorm about the effort involved that could either similar to first, second and third and as per the consensus size of this story is estimated.

2. If team says 1 SP for simple screen, then they decide it takes 4 hours. Can we say 2 SP equals 8 hours or 5 SP equals 40 hours?


No, it is not necessary. It is not required to be equal to the estimation (In hours) of its task. This is like two levels of estimation - For example, if you are using Scrum, at product backlog level you estimate the size (Story Point) whereas at sprint planning you estimate the effort (In hours). Task estimates are more detailed and based on work in hand. Task estimation in ideal hours may decay over time - when we actually execute the work at iteration level, many times our knowledge and experience gets increase and tasks may take less time than estimated in hours.


For more details please refer following video:

yerdogan
Posts: 2
Joined: Fri Apr 01, 2016 8:53 am

Re: How to define task hours with story point

Postby yerdogan Thu May 18, 2017 11:17 am

Hi Seema,

Thank you for your reply. Agile estimation is very difficult topic. Thanks again :)

Return to “PMI-ACP® Open Forum”

Who is online

Users browsing this forum: No registered users and 2 guests