Skip to main content

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.


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 time and with quality to depend on your product. If the team can’t meet deadlines your customers don't know how to make their plans and will probably make plans that exclude you.  Highly effective software teams have the technical knowledge, dependency management and self awareness to come up with a good project plan.  Bright Hub Project Management has a great article on Top 10 Characteristics of an Effective Project Team:
The members of an effective project team are reliable, responsible and accountable to one another as well as to themselves. They create a plausible schedule that incorporates timeliness with accuracy and detail, leaving some room for unexpected snags. They adhere to that schedule because they don't want to let down their teammates - or themselves.
Highly effective software teams communicate and solve issues proactively.  When you working with them you are rarely blindsided.  A great piece on proactive communication is written by Alina Vrabie on LifeHacker:
Communication is obviously important, but what really matters is proactive communication. Proactive communication can be materialized in four ways:
  1. Team members provide information before being asked.
  2. They provide support and assistance before being asked.
  3. They take team initiative by providing guidance and making suggestions to other team members.
  4. They provide updates, creating situational awareness for other team members.

Committed to Shared Goals

I am yet to see a successful technology company that is comprised of part time people.  While you can create an early prototype and test the market slicing your attention between various projects, you will never have a highly effective team whose passion and attention is split between various companies and projects.  There are some rare exceptions such as Elon Musk and Jack Dorsey, but I doubt you can find enough of those types of people to create a full team.  In my 20 years of experience in software: a person who works for you 50% of the time gives you 40% of the output, a person who is working for you 100% of the time gives you 120% of the output.  Here Bright Hub Project Management again hit the nail on the head: 
Team members who are committed to the company or organization as well as the project in general are highly effective, as they are much more likely to give 100 percent at every step of the project and go above and beyond when necessary. Committed team members believe in what they are doing and therefore take great satisfaction in a job well done.

Passionate about Technology

The best software teams are comprised of technology enthusiasts that love learning new things and improving themselves.  There is no way to fake it: people who are in tech just for the paycheck rarely drive you to adopt new frameworks, tools and techniques.  The world of technology evolves too fast and changes too much for someone who wants a regular office job.  Highly effective software teams continuously look to grow.  Amit Kaura has a great article on Agile Delivery Teams: 
"Whether it is using development and deployment checklists, automated testing, test or behaviour driven development, pair programming, extreme programming or continuous integration; teams that succeed are on the constant pursuit of excellence. Being "Good Enough" does not cut it for them."
Highly effective teams will strive to do lunch and learn sessions, do root cause analysis, adopt and try new tools.  In the world of technology if you are standing still, you are falling behind.

Respectful and Compassionate

The best idea can’t win if people do not feel safe expressing their opinions or being themselves.  One of the most powerful articles on this subject is about Google’s project Aristotle:
What Project Aristotle has taught people within Google is that no one wants to put on a ‘‘work face’’ when they get to the office. No one wants to leave part of their personality and inner life at home. But to be fully present at work, to feel ‘‘psychologically safe,’’ we must know that we can be free enough, sometimes, to share the things that scare us without fear of recriminations.
Highly effective software teams create a safe space where their team mates, colleagues and customers can be themselves.  Safe space also means that team members can voice their criticism and dissatisfaction.  Fostering a diverse and respectful environment is a responsibility of the leadership and every team member and highly effective teams nail it.


There are many characteristics of highly effective software teams and it might not be possible to attribute it to just a few factors, but in my research these four things came up over and over.  I haven’t found a successful company whose software teams were not: dependable, committed, passionate and compassionate.  


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 …