Final answer:
The number of story points per person per sprint varies and is based on a team's historical velocity, which is the average of story points completed in previous sprints. Story points are relative and unique to each team, and sprint planning involves committing to a realistic amount of work based on past performance.
Step-by-step explanation:
The number of story points that can be handled per person per sprint is not a fixed value and varies depending on various factors such as the team's experience, the complexity of the tasks, and the length of the sprint. In Agile methodologies, like Scrum, teams usually determine their capacity for story points through a process called velocity tracking. Over several sprints, the team will average the number of story points they have completed, which gives them a velocity figure that can be used to forecast future sprint capacities.
It is important to note that story points are a relative measure of effort required to implement a feature, and as such, they are unique to each team. What equates to a certain number of story points for one team may be very different for another. Teams should avoid comparing their story point capacities with other teams for this reason.
During sprint planning, the team commits to a set of user stories they believe they can achieve within the sprint timeframe, taking into account their past velocity and the estimated effort required. The goal is to have a sustainable pace that ensures high-quality work without overloading the team members.