HeroOps is a planned team-wide event used by the some teams to improve long term issues.

Often we must focus on immediately urgent tickets, or on incidents. This causes improvement tickets in our backlog to be neglected, and sometimes never being completed. With HeroOps we ensure that we can work on those often forgotten improvement tickets regularly.


The goal of HeroOps is to complete 2 improvement tasks per VSHNeer which aren’t necessary right now, but will save us time in the medium and long term.

In short, HeroOps is our way to reduce technical debt by refactoring modules that are difficult to maintain.



F.e. the Polaris team will do a HeroOps day on the second Wednesday of every month. Other teams are welcome to come up with their own schedule.


Everyone from the team will do HeroOps on our HeroOps day. If a major incident comes up, we will of course handle it. We also will still do first-level standard operations on this day.


Pick tickets from the backlog which you feel like would be nice improvements and complete them (within the HeroOps day). Focus on tickets that save us time in the long term. Set the "HeroOps" label before working on a tasks, so we can easily review the tickets and make some statistics.

Be careful with tickets not having a realistic estimated time!


  • Start working on tasks which you feel you can complete within the HeroOps day.

  • Once a tasks is picked (selected and assigned) it’s your responsibility to make sure it will be completed.

    • This means, should you not be able to complete it on the HeroOps day, it will be a normal task in your Kanban you’re responsible for.

  • Don’t work on tasks not finished on a prior HeroOps day or any other started tasks.

  • Request someone’s opinion if you’re not sure on how big / complicated a task will be before picking it.