Agile Development Introduction - Outputs

Scrum - Outputs

If you are familiar with other parts, you can read the introduction, roles, and ceremonies

User Story

The document describing the requirements and expected delivery is the most important document in Scrum. It is a bridge between product requirements and product implementation. A clearer description can reduce the possibility of the gap between the final product and the expectation.

Task

The task is the specific thing to be executed. A User Story may be split into multiple Tasks, including tasks required by the front end and tasks required by the back end. Usually, a Task is the smallest indivisible unit.

Story Points

The goal of Story Points is to measure the development capacity of the team within a certain period through quantitative indicators. Story Points can be defined in several different ways:

1. Associated with the development time, 1 point is one hour, so if a Task is estimated to take 3 hours to complete, it is 3 points.
2. Take a composite score of a Fibonacci sequence (1,2,3,5,8,13) from three aspects of Effort, Complexity, and Uncertainty. The purpose of using the Fibonacci sequence is to make the points have unequal distances. So higher points represent more difficult or complex tasks.

By everyone voting on the same Task, how many Story Points it should be, and obtaining quantitative standards determined by consensus, the purpose is to have a stable and measurable development volume. The purpose of judging by multiple members is to prevent senior members from evaluating the task with relatively low points, but in the end, the task may not be completed by senior members, which will increase uncertainty during delivery. Therefore it is very important for the relevant developers to decide on Story points.