如何通过相对规模来估算用户故事？

Without proper systems or tools, estimating user stories in software development can be challenging, often leading to over- or underestimation. Traditional companies with long-term planning cycles are particularly vulnerable to deviations from initial estimates when work is interrupted. Agile teams, on the other hand, can avoid lengthy, unpredictable planning periods by employing precise iterations and monitoring work-in-progress on Kanban boards. Even with the flexibility of agile methods, the importance of user story estimation cannot be ignored as it remains the sole method for communicating delivery timelines to leadership.

Agile teams estimate the size of each user story and note it on user story cards, which are brief descriptions of customer-required features. To avoid reverting to waterfall methods due to inflexible plans, agile teams need a direct approach to assess user stories. Estimating work in hours tends to be inaccurate, hence the preference for shorter iteration cycles over marathon-like planning.

The concept of relative sizing is introduced as an alternative to hour-based estimation. The size of a story is determined by three factors: effort, complexity, and uncertainty. The 'size' of a story is gauged in relation to other stories within the team, which facilitates comparison and avoids the pitfalls of estimating in isolation.

A simple game called 'Fruit Salad' can help beginners understand the concept of relative sizing. The game involves preparing various fruits for a salad, each requiring different amounts of work, complexity, and uncertainty. By assessing tasks such as washing, coring, chopping, and peeling, team members can assign a relative size to each fruit preparation task. This exercise helps the team establish a common standard for the complexity of tasks and align their estimations accordingly.

In practice, teams can adopt the fruit salad approach to determine a baseline user story size and compare other stories against it. By understanding how to use relative sizing for estimating user stories, teams can implement this method in real-world scenarios for more accurate planning.

经济下行，企业还在“裁员至上”？

了解更多

想要了解更多内容？

查看原文：如何通过相对规模来估算用户故事？

文章来源：

敏捷开发

扫码关注公众号