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.  



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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi