I'm dealing with a similar problem, except on 4 week sprints. It's not management, who doesn't care, it's the team itself which continues to be FIXATED on a burn down chart, to the extent that they massage story points, avoid doing work late in sprints, and are way too concerned with burndown in general.
Shipping valuable features without regressions is my metric of success. Not y=mx+b applied to story points.
Burn down charts are misused far too much to be considered generally valuable.
This all sounds exactly like Solzhenitsyn's descriptions of Soviet factory production, where the work near the end of the month was always rushed out the door to meet quotas.
The way he tells it, no one ever got in trouble for subpar products. But if production numbers were down, someone was going to the gulag.
Apparently, consumers were aware of this and would try to obtain goods that were produced near the start of each month.
this is exactly the CON of the burndown chart. it's a guide, nothing more. I wouldn't say its bad to learn from what the chart gives you, except if its trying to get a linear burn. In fact.... one may argue there is value in underfilling sprints (from a capacity standpoint) and then overdelivering, every time. otherwise known as... momentum or GTD
Shipping valuable features without regressions is my metric of success. Not y=mx+b applied to story points.
Burn down charts are misused far too much to be considered generally valuable.