I’m working with Greenhopper and need advice on dealing with surprise work that pops up mid-sprint. Coming from physical scrum boards, I’m not sure about the best digital approach. When urgent tasks appear, I want to track them without messing up my sprint metrics. Is there a way to mark items as unexpected work so I can measure how much unplanned stuff happened after the sprint ends? I tried looking for some kind of flag or label to identify these items but couldn’t find an obvious option in the interface.
The component field is perfect for this. I’ve used it for about two years to separate planned sprint work from interruptions. Just create an ‘Unplanned’ or ‘Hotfix’ component and tag any surprise tasks with it. Your original sprint scope stays clean, but you’re still tracking the extra work that gets dumped on you. When the sprint’s done, filter your velocity reports by component - you’ll see exactly how much time went to unplanned stuff versus your committed stories. The burndown charts show scope creep too, which is great for explaining weird velocity numbers to stakeholders. One thing though - make sure your team agrees upfront on what counts as truly unplanned versus just bad estimation.
Labels are perfect for this. I create custom labels like ‘sprint-addition’ or ‘unplanned-work’ and slap them on anything that gets added mid-sprint. Way better than components since you can stack multiple labels on one ticket. At sprint end, I run JQL queries to see how many story points went to unplanned stuff versus our original commitments. Great data for retros and makes it easier to argue for better capacity planning. Also worth talking to your scrum master about pushing some of these to the next sprint instead. Sometimes the best move is just saying no to mid-sprint additions unless they’re truly urgent.
just toss those random tasks into a separate epic - i call mine ‘sprint interruptions.’ been doing this for months and it’s perfect. you still finish them in the current sprint, but they’re grouped away from your planned stuff. makes reporting dead simple since you can instantly see planned work vs. what got dumped on you. your original sprint commitment stays clean for velocity tracking too.