Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

DevOps Burndown chart

Last post 12:32 am November 1, 2022 by Ian Mitchell
2 replies
07:17 am October 30, 2022

Hello ,

How can I add ad hoc user stories for urgent work in DevOps Team without impacting the burndown chart? Is there any way that can be used where we donot get the scope creep type of Burndown chart? My team has to take ad hoc work almost every other day which always impacts our sprint. 


09:16 pm October 31, 2022

What you're asking for is a lack of transparency.

A burndown chart shows the amount of remaining work on the y-axis and time on the x-axis. When you take on this ad-hoc work in the middle of your Sprint, the amount of remaining work will increase. If you're using a burndown chart, not reflecting the newly added work means that you are not being honest and transparent with the people reading the burndown chart.

It may be better to understand where this urgent ad-hoc work is coming from. There may be opportunities to identify the need to do the work earlier so it can be refined and planned. There may also be opportunities to understand its true urgency and importance and defer some to a future Sprint. In some cases, though, if a sufficient amount of ad-hoc work is a part of the nature of the team's work, perhaps it doesn't make sense to use a framework that is built around planning and executing timeboxed iterations.


12:32 am November 1, 2022

How can I add ad hoc user stories for urgent work in DevOps Team without impacting the burndown chart? Is there any way that can be used where we donot get the scope creep type of Burndown chart? My team has to take ad hoc work almost every other day which always impacts our sprint. 

If work is being pushed on to the team, it's bound to impact their ability to meet the Sprint Goal. They've already made their commitment and now some other commitment is being thrust on them. Why are you trying to cover the matter up?


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.