3
Story points are a relative measure of effort rather than an absolute one. However, each member of the team should have the same understanding of the size of a points estimate. A common understanding is achieved when the team estimates repeatedly together and when they agree common baseline stories against which to measure. This is really no different to ...
2
I know of at least two
"Empirical assessment of machine learning models for agile software development effort estimation using story points". Available online at https://link.springer.com/article/10.1007/s11334-017-0288-z
"Empirical Validation of Neural Network Models for Agile Software Effort Estimation based on Story Points". Available online at https://...
2
Let's be serious, people don't usually care about estimates. What they care about is how much it takes and/or how much it costs. Time and money. That's what they want. The estimates is just something that helps you answer those questions. It doesn't matter what you use for estimations as long as people can get back a time or money value. It can be estimating ...
2
Each person in a team may have his personal understanding of the correlation between an effort and Story Points.
Initially, in a new team, that may be true. That is why an estimation based on Story Points is more than each team member just giving a number and then taking the lowest/highest/average/whatever as the final estimate.
When doing a Story Point ...
1
Mike Cohn has a great article on Story Points. Some of the highlights are
Story points are a unit of measure for expressing an estimate of the
overall effort that will be required to fully implement a product
backlog item or any other piece of work.
...
Because story points represent the effort to develop a story, a team’s
estimate must ...
Only top voted, non community-wiki answers of a minimum length are eligible
