How to deal with recurring tasks in a sprint?



  • We are working on a software product which by now requires about 40% of our capacity maintenance work like e.g. manually checking data per day. What would be the recommended way on dealing with those tasks within a Scrum framework?

    At the moment I do see 3 solutions:

    Move them out of the sprint/backlog as Scrum Backlog Items (SBIs) should be one time problems and reduce capacity of the team accordingly. Which would result in intransparency of tasks that need to be done (in order to keep our product alive)

    Treat them as regular SBIs and keep them in the sprints. One per day, resulting in a cluttered backlog and during sprint change the PBIs need to be done as well but are not reflected in the stats/planing. Try to automate those tasks and reduce the amount in the future.

    Create one SBI with a checklist and one line/checkbox per day to be checked. This would result in being permanently in progress and belonging story points will reduce the burn down chart only at the very end of the sprint.

    What do you think and is there a solution you know from experience that would work?



  • A common theme in agile methods is about communication, visibility, and transparency in the work that is being done and what the status of that work is, ensuring that the right stakeholders have access to this information.

    Without knowing all of the details about this work, it seems like the Product Backlog is not the right place for these. The Scrum Guide defines the Product Backlog as "an ordered list of everything that is known to be needed in the product." Unless this work represents something that the product needs, I would simply ensure that the work is placed into the Sprint Backlog during Sprint Planning. This can help the team to ensure that they consider it when crafting the Sprint Goal and selecting Product Backlog Items for the Sprint. I would put each task as a separate item in the Sprint Backlog and even estimate them like you would other work in order to be able to show the impact of this necessary work on the ability to deliver other work for the product.

    Long-term, though, it seems like regular work that involves 40% of the capacity is something that should be addressed. I'd question if a development team represents the people who should be doing this work. Alternatively, I'd want to know if there are ways to automate the process to some degree so that way the burden can be reduced, especially if it's an ongoing process.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2