How To Pause A Software Project To Fix A Problem
It’s bad enough when you’re working on a software project and you run into a problem.
But it’s even worse when you know that problem might block other people from getting work done!
It’s always blown my mind how some managers try to keep everyone working as if nothing’s wrong when this happens.
Software projects are getting more complicated every day and so it’s easy to get to a point where you’re blocked.
And I’ve been in the situation many times where I’ve had to explain a problem I’m having to my boss or managers.
But when the problem blocks other people, I’ve had bosses at times pretend there is no problem!
Especially if there’s pressure, blocking multiple people to fix a problem can feel horrible for management – if they’re focused on how much people are getting done.
I talked with you in another episode about how focusing on how much work a team gets done actually hurts how much money a product makes for your company.
So in this episode I want to help you get your manager or boss to support you when you need to make a change that will disrupt other people.
Skip To Points In The Video
- Communicate The Impact (1:47)
- Document Who Will Be Blocked (2:24)
- Explain The Dangers Of Not Stopping (3:06)
- Offer Next Steps (4:44)
- Offer Alternative Work For Others (6:01)
- Take Ownership For The Problem (6:52)
- Should You Really Measure Progress On A Software Project?
- Daily Scrum Meeting: A Status Meeting In Disguise?