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!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …