How to Deal with Repeating Tasks? A Question for the Audience

Most agile projects that I have worked on have had very little repetition in them. Each day brings new work, new problems. Each iteration is working on something different. So what happens if there are tasks that repeat? What if you have to do the same thing every day or every week or every iteration? How does this fit in with agile work methods?

In some agile methods, there are certain things that are already repetitive such as the iteration planning meeting, the daily status meeting and the retrospective. These things are process overhead. As overhead goes, they’re not too bad! Agile methods usually treat them as a special kind of work: they are not work that shows up in the work item backlog nor in the task backlog for an iteration.

In our lives we have to deal with many repetitive tasks: cleaning the fish tank, mowing the lawn, renewing our vehicles license plates, brushing our teeth. Many of these things are “just there”: you know you have to do them, you do them and you don’t bother tracking how much time they take, nor specifically scheduling them.

In Agile Work, with one of the disciplines being to “Eliminate Waste“, there is some tension between our normal approach to repetitive tasks and the high-visibility approach of agile.

We could put all our repetitive tasks on the backlog. For example, if we have a weekly status meeting to report on progress to management, this could be put on the backlog. The problem is, that the meeting doesn’t provide any value to the organization and the backlog is really meant for valuable items.

We could have a separate mechanism for tracking repetitive tasks. This might be a calendar, it might be a per-iteration checklist.

We could find ways to automate or eliminate the repetitive tasks. This works very well in an IT environment or in an environment where machines could do the work. But it can’t work for repetitive communication tasks where the details are constantly changing.

We could leave them essentially invisible…

I’m curious though: have any of you been on projects where you have had to explicitly deal with this? What did you do? Did you distinguish between value-added and non-value-added repetitive tasks and if so, how?

Affiliated Promotions:

Register for a Scrum, Kanban and Agile training sessions for your, your team or your organization -- All Virtual! Satisfaction Guaranteed!

Please share!

5 thoughts on “How to Deal with Repeating Tasks? A Question for the Audience”

  1. Basically, when you are writing a report that doesn’t have any value, you should eliminate it. Cleaning a fish tank obviously does have value (for the fish as well as the owner).

  2. I’m on a construction project’ s commercial team and I’ve just implemented Agile here. There are a number of repetitive tasks – daily, weekly and monthly, that we have to do.
    Struggling to determine a good way to manage these.

  3. I get that items don’t bring value shouldn’t be in backlog. Recurring tasks like cleaning fish tank should be listed in somewhere else, calendar etc.

    But the problem is, when I do daily standup or whatever you call, I want to prioritize all tasks. Then I’ll select one of top items. How can we handle that challenge?

  4. I deal with these by logic and default recurring task feature.
    Logic: if I know a task will need doing again in a while, I set it up as recurring in set intervals. If I’m not sure, I only set it up for one other occurrence and then decide if this needs to be done / reset again.
    The tool for the job:
    An approach that’s easy & successful (so far).

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.