How to correct burndown chart?

Question

Hi,

We are expecting burndown chart to be correct. Our statuses are Dev in progress, Dev completed, Ready for QA, QA in progress, QA completed, Ready for UAT, Moved to UAT, Moved to Pre-Prod and Moved to Prod(last status). On sprint last day we are moving all code to production, so status become Moved to Prod for stories planned in the sprint. Burndown chart become deep down from 60 story points to 0 on last day. Is there any way to 'correct' burndown chart without changing statuses?

Jeevabharathi · Answer

Thanks all for your answers!

Let me check from my side and come back if I have any further queries.

Scott Theus · Answer

I like having a visual way to move stuff around the board too.  But in this case it sounds like Jeevabharathi has a "done" status and a "done done" status, which supports dysfunction within the team. Stories are either done when they are delivered to the release team/process to package up and put into Prod or they are done when they go into Prod.

Charlie Misonne · Answer

Definitely something to consider. There are pros and cons to have them as separate statuses. The donwside of the statuses is your workflow gets more complex.
In my experience people like moving things around on a board, it is very easy and visual compared to editing a field.

Following this idea you could have 1 field named "deployed in" or "current environment" or anything similar and have the 3 values: UAT, Pre-Prod, Prod.