Hard deadlines
“This Date Must Do It, No Exceptions.” Sound Familiar?
Who hasn’t heard that ultimatum before? If I had a dollar for every time I did over my 25 years in tech, I’d have a nice little nest egg, maybe not enough to retire, but certainly enough for something special.
Deadlines are a fact of life in technology, and sometimes they’re set in stone for good reason. I was reminded of this recently after finishing Jeff Sutherland’s “Scrum: The Art of Doing Twice the Work in Half the Time.” The book is filled with stories about how public deadlines can put teams in a corner, especially when decisions are made without all the facts. However, sometimes those immovable dates originate from outside forces, such as regulatory requirements in healthcare. When compliance codes have to be implemented by a specific date, there’s simply no way around it.
Navigating Non-Negotiable Deadlines
Let’s start with those externally imposed deadlines. In these cases, your team should be prepared. If you know your velocity and have a history of similar projects, you can usually plan and execute without too many surprises. But as we all know, “s*** happens.” Unexpected issues can pop up and threaten your timeline. When that happens, the best course of action is to stay calm, assess the situation, and quickly replan. Agile methods shine here, getting everyone together to tackle the challenge head-on can make all the difference.
The Pitfalls of Self-Imposed Deadlines
The real trouble often comes from self-imposed, company-driven deadlines. In theory, if you plan well, estimate accurately, and understand your team’s capacity, you can set realistic timelines. But when any of those factors are off, things get dicey, especially for testing teams, who usually feel the squeeze the most.
So, what are your options?
- Working Overtime: While you can log extra hours, this often leads to burnout and doesn’t guarantee quality.
- Adding More People: The Mythical Man-Month warns us: more people don’t always mean faster delivery. In fact, it can slow things down due to increased coordination and the risk of duplicated effort.
- Replanning and Scoping: This is where Agile shines. Revisit the backlog, clarify what’s truly essential, and push “nice-to-haves” to the next release. It’s not always painless, but it’s effective.
- Risk-Based Testing: Focus on What Matters Most. Prioritize test cases by business impact—think financial transactions over UI tweaks. Provide stakeholders with transparency on what has been validated and what has not, so everyone is prepared for potential issues.
Sometimes, despite your best efforts, you have to deliver tough news: “It just can’t be done.” When that happens, be honest and data-driven. Explain what’s been done, what’s left, and why the timeline isn’t feasible. Most leaders will be frustrated in the moment, but clear communication builds trust and helps everyone move forward.
Tracking Progress and Staying Ahead of Trouble
The best way to avoid deadline disasters is to track and measure continuously. Forget about rigid Gantt charts; instead, focus on metrics like throughput, remaining work, and burn-down rates. These provide a real-time pulse on your progress, allowing you to identify issues before they become crises. If a train wreck is coming, don’t hide it. Raise the flag early so everyone can make informed decisions and adjust as needed.
Ready to make your deadlines more predictable—and your teams more resilient?
Let’s talk about how to implement more thoughtful planning, risk-based testing, and transparent communication in your organization. Reach out at jberriault@berriaultandassociates.com, and let’s turn deadline pressure into a driver for better results.
"I help create ecosystems that become legacies.”
- Jeremy Berriault
Quick Links
Hours of Operation
Monday - Friday
9 am to 5 pm
Saturday - Sunday
Closed