In a perfect world, we do our development, tests past the first time and the work shoots from environment to environment, going live same day and leaving us all looking like hero’s

Reality check, having been in delivery for 15 years, in many different companies, the only place that I have actually seen this happen is linkedin posts.

Most of us have to work through change boards or governance of some sort, especially if we work in the secure, finance or insurance or insurance sectors.

Nobody likes doing the governance tasks, we would all rather focus on development and building new features BUT, these tasks are real, they have to happen and they usually include supporting documents that take time to put together.

So don’t feel bad creating stories/tasks in your sprint to cover the time needed to complete them, else they will end up at the side of your desk, which is never good.

What’s the worst that could happen?

• You have the time to accounted for in the sprint.
• You could highlight improvements to reduce the time lost doing these tasks.
• You can highlight dependencies getting in the way.

All these things sound sensible to me.

Just a thought.