Process to manage changing priorities mid-quarter
I am trying to come up with a proposal for a process that will show the progress of our features. Showing progress will give transparency and enable management to see what work will be impacted if they decide to increase scope or add another feature. I was thinking to create a Gantt chart, with the list of features, by team, and show the progress. The data would be generated based on the number of stories completed and the number of stories left. I would show this to management after every system demo. Would this be effective or can someone suggest a better idea?
You may want to explore a Release Burn Up Chart, and reflect a cone of uncertainty (using best Sprint, Avg Sprint, Worst Sprint velocity or throughput). The nice thing about the burn up is that it shows completed work by Sprint, and remaining forecast. I even added a line to that graph to show Product Backlog size (to show increase in scope). It is a great visual for conversation with stakeholders (our forecast keeps moving because of scope add).
I am trying to come up with a proposal for a process that will show the progress of our features. Showing progress will give transparency and enable management to see what work will be impacted if they decide to increase scope or add another feature. I was thinking to create a Gantt chart,
Why doesn’t the Product Backlog offer adequate transparency over progress?
Why do you want to do this?
Is there a reason you're trying to solve this with a process?
Why is it that you're specifically making this transparent to management, rather than to all stakeholders?
Who is accountable for value delivered, and is that recognized as a separate concept to feature creation?
Why do you want to do this by team, rather than by product?
What is a system demo? How is it different to a Sprint Review? Are you using Scrum?