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!

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…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…