Skip to main content

The biggest issue for software schedules

Every time you create a program you are creating something new with new challenges, tools and
requirements.  At the same time business requires schedules and costs to figure out how to bring a product to the customers.

Scheduling and estimates is a never-ending topic in software. Different estimation techniques have been employed over time.  From a simple one like “take whatever engineer tells you and multiply it by two” to Scrum points and velocity calculations.

My team spends about an hour after every sprint doing a “Sprint Review” meeting where we discuss things that accelerated progress or derailed our plans.  The finding of what has screwed up the schedules the most has been quite surprising to me.

I was expecting that it would be one of the usual suspects such as “engineers are naturally optimistic” or  “no one anticipates the level of detail”, however the most common source of delays have been… waiting on dependencies!  Engineers might have been absolutely correct about anticipating the level of effort and might have taken into account the complexity of requirements and even time to do bug fixing, but still missed their anticipated delivery date.

What are some of those dependencies?
1) waiting on a bug fix from another team
2) working with an external vendor to do localizations
3) waiting on access to legacy source code
4) waiting on a customer to give additional data for a bug repro

This all made me think about how valuable program managers can be.  I remember working at Microsoft a decade ago where some engineers said: “developers develop, testers test and program managers – stay out of the way”, but it turns out that these busy bees of tracking dependencies, facilitating conversations and documenting schedules are really quite impactful.  Of course when everything goes well and all dependencies are there just in time no one notices that, so to compensate for it find a Program Manager near you and give them a hug! ☺



Post a Comment

Popular posts from this blog

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…