How is team progress measured?

The progress of a Scrum team is measured not by time, but by value and finished results. The main idea is to see what is actually done and delivers value, not how many hours were spent.

---

#Main ways to measure it

1. Velocity Shows how many Story Points the team completes per sprint. A stable velocity indicates predictability and good planning.
2. Burndown Chart A chart showing how the amount of remaining work decreases by day of the sprint. If the line goes steadily down, the team is on track; if it stays flat, there are delays.
3. Number of completed tasks Only tasks that fully meet the Definition of Done are counted. This reflects the actual readiness of the product, not "in progress".
4. Achieving the Sprint Goal The main measure of success is whether the sprint goal was reached. Even if not all tasks were completed, the sprint is considered successful if the goal was reached.
5. Feedback at the Sprint Review The customer's and users' assessment of the value of the finished increment, a measure of usefulness, not just the amount of work done.

---

#Conclusion

Progress in Scrum is results that deliver value, not the number of hours or lines of code. It is measured through velocity, burndown, task completion, and achieving the sprint goal.