How to Avoid Last Minute Missed Deadlines

Last week, a CEO asked me a great question. His tech team told him they would be missing their delivery date, which was the very next day. He was obviously frustrated. He wanted to know how this sort of last minute “oh by the way we’re going to miss tomorrow’s deadline” scenario could be avoided.

“Avoided?” I thought. “If a tech team is doing that, they should be fired! That’s not just irresponsible, it’s almost criminal!” I stopped myself from saying that out loud. Instead, I told him this:

If this is happening to you, it means the technology team is hiding problems from you. When something went wrong early on, they didn’t say anything. And now, there is no time to fix, to pivot, or to call in more troops.

Here are practical things I recommend doing on a project to prevent last minute missed deadline surprises from happening:

Start with a realistic plan

Ideate the road ahead. At Stride, we have Inception meetings. They require all stakeholders and the technology team to collaborate and clarify assumptions, state business vision, and define the initial scope of work. We break down that work into stories and tasks, estimate that work systematically, prioritize everything in a master list, and come up with an initial project plan that shows how we predict we’ll burn down our backlog.

Realize that everyone truly is on one team

Whether you partner with a software consultancy like Stride, or do all the work in-house, it’s critical to realize that everyone is on the same team, rowing in the same direction towards a shared goal. That requires a massive investment of everyone’s energy, but we think it’s worth it. The team must identify and fill roles including the domain expert, product owner, and source of the product vision. These roles can be filled by one or multiple individuals.

The team should ideally have a daily stand up detailing progress, weekly demos of the software, as well as lots of ad-hoc discussions about how the product should behave and what’s next. Everyone should be along for the entire journey. Developers and everyone on the front lines should be involved from day one. Nothing should come as a surprise to anyone.

Revisit the plan again and again

Every week, review the plan that the team defined at the start. Did any new scope get revealed? Was a technological problem bigger than expected? How good were our estimates from the start? Do they need to be updated based on new information? Any risk to our plan needs to be reflected in an update.

Focus on prioritization

Features should come as an ordered list, so that if we are cut short for any reason, we have worked on the most important thing all along. And, this enables the team to truly embrace change. If a stakeholder or external market shift demand we add additional scope, we can easily and quickly identify where the new scope fits in. Be disciplined about having weekly priority and planning meetings so that the team stays on top of deadlines.

Want to learn the other 2 tactics to help your team meet deadlines? Read the full article here.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.