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

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!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…