We Just Cancelled a Sprint Retrospective. It???s a Disaster

I feel tense in my shoulders today. This is because I failed to speak up in the stand-up. I didn’t say what I know to be true and let myself and my whole team down.

As a result of my actions, the team won’t improve and we will be unable to deliver as many features as we should be able to.

So what is the crime of The Secret Developer this time?

I didn’t speak up when we cancelled the Sprint Retro.

The Working Environment

I’ve been working at my current position for something like a year. To say I’m not enjoying it is something of an understatement and I’m just starting to come to the truthful conclusion that it isn’t me it’s them.

Today I feel that I’ve got just a little more evidence that the correct conclusion has been reached.

Our feature team has just started four-week sprints because we failed time and time again to deliver work in two-week sprints.

The Situation

At the end of today’s standup at the end of the sprint, we had the following questions from the tech lead and product management.

Is there anything you want to raise today for the retro or we can cancel.
I don’t, but it’s really a question for the team.
I’ll ask the Scrum Master later.
[to the team] Anyone want to raise anything?

We were met with a stunning wall of silence to this last question. Now I’m of the opinion that retrospectives should (near) never be canceled.

Website