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?