Skip to main content
Software Engineering

Return to Question

Question Protected by Thomas Owens♦
Post Made Community Wiki by Scott Barnes
Fixed some grammar.
Source Link
edit approved Dec 7, 2013 at 1:43
SunSparc
edit approved Dec 7, 2013 at 1:43
SunSparc
  • 185
  • 8

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story. Story points are used to calculate how many user storystories a team can take in an iteration.

What is the advantage of introducing an abstract concept story(story points), where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story pointpoints are harder to use (because itthe concept is abstract), and also harder to explain to stakeholderstakeholders. What advantage does it offer?

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story points are used to calculate how many user story a team can take in an iteration.

What is the advantage of introducing an abstract concept story points, where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story point are harder to use (because it is abstract), and also harder to explain to stakeholder. What advantage does it offer?

In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories are measured in Story points. Story points are used to calculate how many user stories a team can take in an iteration.

What is the advantage of introducing an abstract concept (story points), where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story points are harder to use (because the concept is abstract), and also harder to explain to stakeholders. What advantage does it offer?

fixed a semantic error
Source Link
edit approved Jan 10, 2013 at 0:24
PhD
edit approved Jan 10, 2013 at 0:24
PhD
  • 2.5k
  • 2
  • 19
  • 32

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story points are used to calculate how many user story a team can take in an iteration.

What is the advantage of introducing an abstract concept like user storiesstory points, where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story point are harder to use (because it is abstract), and also harder to explain to stakeholder. What advantage does it offer?

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story points are used to calculate how many user story a team can take in an iteration.

What is the advantage of introducing an abstract concept like user stories, where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story point are harder to use (because it is abstract), and also harder to explain to stakeholder. What advantage does it offer?

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story points are used to calculate how many user story a team can take in an iteration.

What is the advantage of introducing an abstract concept story points, where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story point are harder to use (because it is abstract), and also harder to explain to stakeholder. What advantage does it offer?

Tweeted twitter.com/#!/StackProgrammer/status/289130213667909632
Source Link
Louis Rhys
Louis Rhys
  • 6.2k
  • 11
  • 45
  • 60

Why do we use story points instead of man days when estimating user stories?

In agile methodologies (e.g. SCRUM), the complexity/effort needed for a user stories are measured in Story points, and story points are used to calculate how many user story a team can take in an iteration.

What is the advantage of introducing an abstract concept like user stories, where we can just use a concrete measurement, like estimated man-days? We can also calculate velocity, estimate coverage of an iteration, etc. using estimated man-days.

In contrast, story point are harder to use (because it is abstract), and also harder to explain to stakeholder. What advantage does it offer?