SCRUM POKER - Estimación y Planeación del Sprint en Scrum

Introduction to Scrum Poker and Estimation

In this section, Cris Rúa introduces Scrum Poker as a method for comparing the difficulty of user stories in Agile development. The focus is on estimating difficulty rather than time.

Scrum Poker Cards

• Scrum Poker uses physical cards or an application.

• The numbers on the cards represent the relative difficulty of user stories.

• Smaller numbers indicate closer difficulty, while larger numbers indicate greater separation.

Example Comparison

• Comparing combing hair of a hamster (2 points) to combing hair of a cat (8 points).

• It is easier to compare when the difference is double or triple, but harder when it's 20 or 21 times more difficult.

• Beyond a certain point, the difference loses relevance.

Using Scrum Poker for Estimation

This section explains how to use Scrum Poker for estimation in Agile development.

Starting with a Baseline Story

• Begin with a baseline story that everyone knows how to do and has clear acceptance criteria.

• Use this story as a reference point for comparing other user stories.

Individual Estimation

• Each team member selects their own card without showing others.

• The chosen card represents their estimation of the story's difficulty.

Revealing Estimates

• Team members simultaneously reveal their chosen cards.

• This reflects each individual's understanding of the story's difficulty.

Importance of Individual Expression in Scrum Poker

This section emphasizes the importance of individual expression during Scrum Poker estimation.

Avoid Biasing Others' Estimates

• One team member expressing an extreme opinion can bias others' estimates.

• It is important not to influence others based on personal understanding or assumptions.

Encouraging Open Expression

• Each team member should express their estimation without being influenced by others.

• Different perspectives and understandings contribute to a more accurate estimation.

Discussion and Consensus Building

This section explains the process of discussion and consensus building after individual estimations.

Discussing Lowest and Highest Estimates

• Team members discuss the reasoning behind the lowest and highest estimates.

• Only the team members with the lowest and highest estimates participate in this discussion.

Second Round of Voting

• After the discussion, team members vote again based on their revised understanding.

• The numbers tend to converge towards a consensus after the discussion.

Importance of Reflecting Individual Understanding

This section highlights the significance of reflecting individual understanding during Scrum Poker estimation.

Avoiding Biased Estimates

• Biased estimates can occur when one person's understanding dominates the discussion.

• It is important to consider different perspectives for a more accurate estimation.

Allowing Individual Expression

• Each team member should have an opportunity to express their understanding without bias.

• Both easy and difficult aspects of a user story should be considered for a balanced estimation.

Estimating Story Points and Hours

In this section, the speaker discusses the difficulty of estimating tasks and the importance of not relying on hours as a measure. They also mention additional factors that can affect estimations.

Estimating by Story Points

• Estimating tasks solely based on hours is not effective.

• It is better to estimate using story points, which take into account complexity and effort required.

• Story points are relative and can be compared across different tasks.

Relationship Between Story Points and Hours

• There is no direct correlation between story points and hours.

• Each team member may have a different understanding of how many hours a certain number of story points represents.

• It is important to let go of thinking in terms of hours when estimating.

Additional Factors in Estimations

• Sometimes teams may find a user story too large for a sprint, leading to the need for splitting it into smaller stories.

• Occasionally, estimations may be affected by fatigue or lack of focus during estimation sessions.

Conclusion and Further Resources

The speaker concludes by encouraging viewers to practice poker estimation with their teams and explore various resources on the topic.

Final Thoughts

• Poker estimation can be a useful technique for estimating tasks accurately.

• It is recommended to read from multiple sources to gain different perspectives on estimation.

Further Resources

• The speaker suggests watching more videos on their YouTube channel for additional information on estimation techniques.