Velocity charts indicate completed tasks along with the sprints. Typically, Y axis shows completed tasks that are measured by story points, hours or tasks and X axis shows sprints. This represents a graphical view of the amount of work that the team has completed within the past sprints.
In our project, we used these charts to identify our team performance and get the decisions to change our way of working (Mob programming to pair programming). We could identify that if we work as mob programmers, we could not complete our sprint backlogs and then we discussed and changed it to pair programming methods based on the result of velocity charts. In my opinion, if we could not meet our expected velocity in our project with the pair programming, we could identify it with velocity charts and then we can get a decision based on that.
Finally I can reflect that if we work in a scrum team, to maintain constant velocity of work along with all the sprints, we have to generate and check these charts at the end of every sprint and need to analyze them with the team members. After that we need to identify the factors that cause the velocity reductions before taking the decisions.
Top comments (0)