Relative Sizing/Story Points

Correct Answer: Facilitate a detailed discussion about the complexities of the story and why the member thinks it's a 21 and then guide the team towards a consensus.

In agile practice, every team member's estimation is essential since it's a team-based approach. The first answer reflects the adoption of 'collaborative decision making,' which is an integral part of Agile. It suggests facilitating a detailed discussion about the complexities of the story and why the member thinks it's a 21, then guiding the team towards a consensus. That's the most appropriate approach- it's not about denying or accepting suggestions upfront, but about discussing, understanding the complexities, and then coming to a team consensus. The other two answers - 'Immediately discard the suggestion as it's way beyond what the team usually estimates' or 'Tell the member that they are wrong and their story can't be a 21' contradict the Agile values as they do not promote a collaborative approach, rather these responses are dictatorial. The last answer 'Ask other members to give their points without considering the 21 point suggestion', although sounds democratic, it's also not ideal because it makes the member's suggestion feel ignored which is against Agile spirit.

Correct Answer: Comparing each story to other stories and assigning points based on complexity and effort.

The most accurate approach for assigning story points in Agile Methodologies is by comparing each story to other stories and assigning points based on complexity and effort. This is the method recommended by Scrum and other Agile frameworks, recognized as relative estimation. Here, team members analyze each story by itself, its complexity, risks involved and efforts to complete. It's relative because it's based on the comparison of one story to another, not on precise measure like time. Assigning points based on the time it will take to complete misrepresents the complexity and risks involved in the story, making it an inaccurate estimation. Giving each story the same number of points regardless of complexity or size doesn't consider the variability and differences among user stories. Assigning points merely based on the priority of each story in the product backlog does not consider the actual effort needed to realize each story, thus not a reliable approach for determining the story points.

Correct Answer: Review the way the team is calculating story points and adjust it as necessary to ensure consistency and accuracy.

The best approach if a team is facing a problem with their current story point calculation affecting their velocity calculation is to 'Review the way the team is calculating story points and adjust it as necessary to ensure consistency and accuracy.' Story points are an estimation of the effort required to complete a task, and if calculated inconsistently, will lead to inaccurate velocity. Adjusting the method of calculation to ensure better accuracy and consistency will result in a more accurate measure of velocity, thereby improving project planning and execution. The other answers suggest to ignore the story point completely, artificially increase velocity or decrease story point for all future stories. These approaches can cause serious project planning issues and not address the root cause of the problem. Consequently, they are not recommended.