My Velocity chart is showing weird data, it shows more completed then committed.

[Charu Nisheeth]

I added couple of stories after sprint started but I think that is acceptable. I want to know where I am doing wrong and by my chart is not showing the right graph. 

[Scott Theus]

Hi @Charu Nisheeth , 

Could you share an image of the graph? That will help us understand what might be happening.

Also, take a look at the sprint report for that sprint. I suspect that you've completed several story points outside of the sprint.

-Scott

[Charu Nisheeth]

uploaded

[Charu Nisheeth]

[Charu Nisheeth]

[Scott Theus]

Thanks @Charu Nisheeth .

The velocity chart shows what was committed at the start of the sprint; it does not take into account the stories that were added mid-sprint. The red line of the burndown, however, shows the total story points that are not done on each day of the sprint. The grey line shows the "expected" burndown based on the committed points at the start of the sprint.

So, as stories were added to the sprint your burndown went up because you were increasing the sprint's scope, but your original commitment does not change. 

If the increase in scope was a one-time thing, then I suggest using the velocity from the start of this sprint for the next sprint.  However, if the team's capacity has improved that much or your sprint was not planned out thoroughly before you started it then use the average velocity for this sprint and the previous two sprints to estimate the number of story points to include in the next sprint. Over time the velocity will balance out until you no longer need to add scope in the sprint to show the work that is actually being completed.

Hope this helps, 

Scott

[Charu Nisheeth]

Thanks @Scott Theus