re: Explaining Scrum story points VIEW POST


Thank you! This is the blog post I've been meaning to write for quite some time. Story points are a measure of complexity, not time. Eventually, people learn to judge complexity: is this code we're going to change something we've worked on lately? Does it have good test coverage? Was it written by someone who is no longer on the team, or worse, a founder? Does the story depend on external vendors and APIs? New and unknown technologies or frameworks? Add more points for each bad answer.

Code of Conduct Report abuse