Skip to main content

Software Development Pods

One of the key responsibilities of Director of Engineering or any sort of software manager is ensuring the continuity of business.   It just so happens that no matter what you do your engineers will need to move around inside and outside the company. When people leave you are stuck with a piece of software that is not supported for bug fixes and escalated configuration questions.

As a manager your internal and external customers generally come to you for answers, but with a sizable portfolio of say 10-12 products even a reasonably technical manager can’t possibly maintain the products that lose the engineering ownership.  More importantly when you are pulled into bug fixing you lose your ability to unblock and facilitate the team’s workflow.

Recently I decided to try forming “software pods”. Pods consist of two developers and a tester.  This ensures that I have three people who know how the product works and two people who can fix bugs or deal with hot escalations.

There has been another good side effect of a pod.  It seems like folks have also started forming friendships and joint ownership of code. While these guys don’t have to do pair programming, they constantly have to merge code and talk about their respective design.

There is also a question on what kind of skill set you have in a pod.  Is it two mid-level engineers?  Is it senior and a junior?  It seems like two junior folks don’t really work.

What do you do to ensure continuity? What kind of effects have those methods have? Feel free to share via comments or over twitter @mikebz.
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…

Ego in Your Decision Making

Oxford dictionary defines Ego as: “a person's sense of self-esteem or self-importance”. It says that it is “responsible for reality testing and a sense of personal identity.” For a lot of us techies those were really important functions that probably served us very well early in our career.  We had to be assertive, we had to choose a coding style guide, pick our frameworks and “be decisive”.  However when it comes to engineering management the same things that used to help might be turning into a liability.

When my job changed from writing code to creating an environment where the best code is written - it took me a while to understand how my ego was holding me back.  I kept applying the old tricks - defining the architecture, the final design and task priority.  What ended up happening is those things led me to turn off a lot of the best and brightest people on my early teams.

I remember the feelings of being aggravated when I had to go over an explain my decisions and get buy …