Software Development Staffing and the Sixth Man Principle
With college basketball season heating up and March Madness right around the corner, I’m reminded of the sixth man concept that Rural Sourcing has used since its early days. As in basketball, the sixth man concept is all about having a ”non-starter” prepped, practiced, ready to enter the game and immediately start contributing to the team. This concept is core to Rural Sourcing’s sixth man principle. For many of our strategic accounts we deploy an extra colleague to participate in the upfront strategy and design sessions, kickoff meetings and daily stand ups so that when their time comes they’ll be prepared to hit the court at full speed. Their time may come due to an injury, an illness, paternity or maternity leave, or maybe just a packed sprint that needs the extra help. Whatever the cause, we know that this sixth man will be able to step in, run the offense and execute the game plan because they’ve been to all the practices.
But wait, why would an enterprising, software development firm place a non-billable colleague onto a team? Our rationale is that it’s good for the client, good for the colleague, and in the long run, it’s good for us. For the client, it’s the assurance that they know there’s a backup waiting to get in the game in case something happens. For the colleague, it’s a better use of “bench time,” and it keeps them fully engaged in the project at hand.
That’s why, as the season progresses and March Madness arrives, pay special attention to the sixth man players. I bet you’ll find that even though they have less time on the court, they still make a big impact on the final score.