Hi Richard, your videos are very informative and the concepts are very well explained. Could you please make a series on the scrum reports (burndown , burnup etc) capacity planning report , resource utilisation etc created and used by Scrum masters in a project. In short all the charts or reports a scrum master would use in a project
I have a question here. Is the total story points in product backlog decided by the product owner? From what I understand the story points are decided by the SM & development team during spring planning while moving them to sprint backlog. Or am i wrong?
Hi Toufiq, my apologies on the delay. Typically the story points are decided by the SM and Development team, not at Sprint Planning, but at Product Backlog refinement sessions which occur during the Sprint.
Hi Mahesh, I like to use Velocity with Story Points for long term forcasting (i.e. Release Planning), but capacity using time for Sprint Planning. I.e. Story point estimation at the Product Backlog Item level, but time based estimation at the Sprint Backlog level. For more details on Time based (capacity) estimation at Sprint Planning, you can checkout this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-94sqZadKOFI.html Hope that makes sense, but if not let me know and I can clarify. Thanks! Richard
Thank you so much for this, really helpful. I know you are doing your series thing, I have some questions 1- is the estimation of story points done during backlog refinement or during sprint planning? 2- what is the difference between story point estimation and subtasks? .
Thanks Linette, and apologies for the delayed reply. 1. Estimation of Story Points at the Product Backlog level should be done during Product Backlog Refinement, at least a few days before Sprint Planning. This will give the Product Owner enough time to reprioritise based on the estimates, and also give the team some time to break down any large Product Backlog Items that was only evident after estimating. 2. Story Point points are used to estimate Product Backlog Items, and allow teams to estimate by comparing items to one another (For more details check out this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-QUo5l4wwmzk.html). Sub-tasks on the other hand, are Product Backlog Items that have been broken down into more granular tasks. These "sub-tasks" are also referred to as "Sprint Backlog items". Typically at the Sprint Backlog we would estimate using time, and *not* Story Points (For more details on this you can checkout this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-94sqZadKOFI.html) Hope it helps! If you have any other questions or if those above need more clarification let me know :) Many thanks! Richard
Really liked your videos. Can you make video on ' How to handle spill over'? Like US have 5 points and it has subtasks in which 2 subtask is still inprogress and need 6 hrs work. ( last day of sprint). What should we do ? 1.Move US with 5 points to product backlog and restimate it 2. Split the US with 3 points n mark it complete n another US with 2 points move to next sprint backlog or product backlog Please suggest
Hi, thanks for the great question. In this situation my preference is to move the User Story back to the Product Backlog, but *not* re-estimate. E.g. just leave it as 5 points. What that means is the Sprint that it was started in will probably have a lower velocity, but the Sprint in which it is finished will have a higher velocity. When you take the average velocity it will even out. The reason I like to do this is to encourage the team to complete the User Stories entirely in a Sprint. I.e. they will only be awarded the Story Points in the Sprint they actually complete the work. Hope that makes sense! If not, let me know :) Richard
I would be very happy if you could show some examples of user storys for different story point as reference. I am currently trying to use story points to estimate tasks and plan sprints for a System Development Team for system requirements analysis and system design. However, we had so far always used time estimates instead of story points, which I want to change.
