Skip to main content

Cross Functional Teams

Example of Small Cross Functional Teams - Jazz Bands
In the early days of a startup, everyone is on one team; they’re all part of the same tight-knit family.
Until the headcount reaches 15-25 – especially if they all share an office – it’s hard for any employees to be misaligned for too long.

Fast forward to when the organization grows to hundreds of people, or even thousands. Then the execs start making choices about how to organize; considerations like efficiency, career paths, dependencies all come into play.

To maintain agility in the company, it’s best to have everyone working together on the same team, reporting to the same manager who is responsible for delivering on the goals.

During my years of delivering software projects, I have noticed that the #1 issue plaguing product delivery is dependencies. When the Program Managers, Designers, Developers and Quality Assurance (QA) Engineers are all on a different team, it requires coordination, scheduling and other things that slow the progress down.

It’s impossible to avoid dependencies, but it’s always a good strategy to minimize them. 

Being physically located together is a big advantage as well. I have seen many instances in which a QA engineer finds a bug and the developer fixes it instantly. Stepping in to help someone out happens a lot more frequently when that someone is a real person; a real person who reports to the same manager and sometimes grabs lunch with you in the cafeteria. On my cross-functional teams, developers continuously help out QA with automation and testing.

The endless back and forth -- the triage and figuring out how to set up the repro environment -- goes away when you can take three steps to look at your neighbor’s screen.


The benefit of a big Developer team having sister QA and Program Management teams is that the company gains efficiencies from these disciplines being together. The Director of QA, for example, can establish the common tools and guidelines. For a company that’s in a more stable phase, that could be the right configuration. This organizational structure also helps employees who aim to move up the management ranks and need a career trajectory for graduating from individual contributor, to lead, to manager to director and so forth.

For most of my life, I’ve been focused on hyper-growth products that needed to move fast with as few dependencies as possible. As a result, I’m a big fan of the cross-functional team model.

-mb

PS: If you liked this post you might also like Three Pillars of Engineering Management and The biggest issue for software schedules.

Labels:
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!
Read more

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…
Read more

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 …
Read more