Currently my team's burndown charts includes weekends and nights, I feel like this harms the velocity by misrepresenting it, however, I cannot explain this very well.
This is what is going on in my head...
In my team
Velocity = Number of Story Points Completed / Sprint and
Sprint = 2 Weeks
So as an example, in the above image, the commit is 50 story points, while the team was only able to deliver
50 - 10 = 40 story points this sprint, so the team's velocity is 40 story points.
Currently the target burndown chart generate by JIRA (grey) at the start of the sprint includes the weekends, I feel like it should not include the weekends (blue). What are the benefits of including the weekends? What are the downsides of removing the weekends? Does including the weekends harm velocity?
Because we track nights, everyday we go above the target line (grey) and it looks like we are under-delivering. What are the benefits of including the nights? What are the downsides of removing the nights? Does including the weekends harm nights?
What also came to me while writing this, is that during planning we say that each developer will do 8 hours of work per day, however, we track 24 hours of work per day.