Team determines which backlog items have to be taken in the next sprint

Focused and productive way of working

Rule of thumb: 2 hrs per week of sprint. If we have 3 week-long sprints = 6 hrs Sprint Planning meeting

PO Agile Lead Dev team Business Analyst

Sprint Goal Sprint Backlog Items Team capacity No of backlog items the team can complete during a sprint - No of Team members * No of Hrs available - Subtract the time spent in meetings/add.tasks Velocity Rate/Speed at which the team can deliver - *Can be computed only after the team completed 3 to 5 sprints Sprint Retro Points Estimation Story Points (80% of the time in Sprint Planning meeting is spent doing estimation) - How many points each user story is - Find the simplest story, assign it 1 point and then use it to assess the rest - Assign Story points to number of hrs of effort involved Good practice: No user story should take more than half of the sprint duration