Burn the heretic! You can't assign a fixed relationship between hours and points just because that's a logical consequence of having a stable velocity! :-)
hey Nick, thanks for your comment, please read the disclaimer , which i shared in the beginning of the video, absolute agree with you there is no fixed relationship between hours and story point but what is story point = Efforts * complexity * Risk( dependencies) . happy to connect with you on virtual beer someday , drop me email sunand.sharrma@gmail.com or connect via linkedin
Hi Sunland - in Team capacity chart the best case total shown is 120 hours for month but it seems the calculation is for one week as we assume full strength of each resource that will account is 8hrs * 5days working = 40hrs max and max total capacity for one week will be 40*4 resource = 160hrs. Then for 2 weeks sprint it will be 160*2 sprint = 320hrs maximum hours... Kindly confirm above understanding.
Is there anything like this if we are going to take velocity The number of weeks 2 * 4 is a constant measure * number of team members 8 So the total velocity is 2*4*8=64 When we don't know velocity is this also a method, please let me know sir.
Other way around when we are estimating the whole PB then looking at the capacity and considering 2 weeks sprint we can ask members of team how many story points they can complete in a 2 week sprint . for 200 point story suppose they pick up 40 SP. which means that they can deliver whole product backlog in 5 sprints. Does that make any sense sunand?
Hi Sunand Sir, As You mention(Video play 3.16) that we need to estimate entire Product backlog so We need to give one pointer reference user story and compare that with other stories. So My query is that to give one pointer that needs to be given on fibonacci format like 1,2,3 5,8 and so on? Also my another query in hr to point mapping, for task level do we need to use Fibonaaci format for that also?
1- Yes (Fibonacci) 2- yes (Fibonacci) buts also ok if you do normal effort allocation. Also let me remind you this is just for the beginning for projects manager or clients , it will change with actuals once project start
Sir , The number of weeks 2 * 4 is a constant measure * number of team members 8 So the total velocity is 2*4*8=64 When we don't know velocity is this also a method, please let me know sir
One of the agile coach told me and I was surprised that please let me know or if I want to connect with you is there any way please let me know. Because in social media phone number exchange is not the good idea
Next step is Hour to Point Mapping. ? Is this the right apporach. as Points are relative estimation and mapping them to hour doesnt it kills the estimation motive . Is it then like taking a relative estimation and considering them as deadline??Please suggest
Please understand the context/purpose first here and disclosure/warning I gave in this video. SP is = effort x complexity x risk and not only equal to effort
Please understand the context/purpose first here and disclosure/warning I gave in this video. SP is = effort x complexity x risk and not only equal to effort
You have no idea, how much you are helping many scrum masters who are looking for great content like me... Is there any email where I can reachout to you.. I live in France.
