You are welcome! :)

Thanks Jessica! We certainly plan to produce content more often, especially with positive feedback such as yours :)

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: kzfaq.info/get/bejne/h7ufaM9l3N3Rqp8.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: kzfaq.info/get/bejne/b5qjpL2SybGzdn0.html) Hope it helps! If you have any other questions or if those above need more clarification let me know :) Many thanks! Richard

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

@@AxisAgileApps Thanks 🫡

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 Elektro, do you mean examples of what a small User Story would look like compared to a large User Story?

@@AxisAgileApps exactly. Examples for different fibonacci numbers.

@@elektrotigerRM Cool, that's a great idea. We've added it to our Video Backlog :)

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: kzfaq.info/get/bejne/b5qjpL2SybGzdn0.html Hope that makes sense, but if not let me know and I can clarify. Thanks! Richard

@@AxisAgileApps thank you for your video will do and if i need help or any questions regarding this will ask you. Have a wonderful day.