Incorporating Part-time Team Members

[article]
Summary:

"Part-timers just don't seem to fit in with the team," a manager complained to Esther Derby recently. "I do everything I can to impress on them the importance of teamwork and team spirit, but they just don't gel with the team. What can I do to motivate these people to fit in?" In this column, Esther Derby reveals the truth of the part-timers' mindset and what you can do to motivate this group.

Here's the news nobody wants to hear: The problem is not with the part-time people, rather it's with the part-time assignment.

Priority
When a person is assigned to more than one team, she'll gage priority by the proportion of her time that's allocated to each project. One tester I know was assigned 90 percent to developing manual test cases and 10 percent of her time to creating a "critically important" automated test harness. No matter what words her manager said about the importance the test harness, the fact that she was directed to spend only 10 percent of her time on it communicated a different message. Furthermore, when she attended meetings or working session with the automation team, she spent most of the time catching up on what had transpired since her last sliver of time with the team. The arrangement wasn't satisfying for her, and frustrated the automation team. Soon, she stopped working on test automation at all.

Ambiguity
Many people will opt to spend their time on work that has clear-cut outcomes over work that's ambiguous. The more clarity around the part-timer's contribution, the more productive the situation will be for everyone.

Team Cohesiveness
If the full-time team is cohesive, the part-timer may not be able to fit in. Gelled teams develop their own subcultures. They may have unspoken rules of engagement, communication patterns, and established relationships that make it difficult for someone who isn't full time to fit. Over time a part-timer may acculturate, though the process will be slower than it would be for a full-time team member.

Missing Context
When someone works on a team part time, he is by definition missing part of the context of the team. While the part-timer is off doing something else, the full-time team makes decisions, solves problems, and exchanges information. While the full-time team may document and transmit major events, there are numerous small decisions and communication events that may not seem important enough to pass along but still affect the way the work is done. The adage "You never step in the same river twice" fits this situation. Each time the part-timer re-enters the team, the team has inevitably moved on from the last time the part-timer participated.

So, what can managers and team members do to improve the situation? First look at the work and how the part-timer needs to contribute. Here are some of the questions you may ask about the work:

Is his contribution time-limited, meaning that his skills are needed for several days, but not for the duration of the project? Maybe the person only needs to contribute at some critical point. Perhaps he is only needed for one or two iterations, when the team is working on a particular feature. Consider contracting for the person to focus full attention for those periods of time.

Can the contribution be batched so the part-timer interacts with the team for a day or two a week? Blocking out a day or two a week to work with the team is more effective than having the part-timer spend an hour here and an hour there with the team. This may require more clarity and coordination from the full-time team, but it will make better use of everyone's time in the long run.

Is the part-timer needed for hands-on work, or can he act as a reviewer, consultant, or coach to members of the full-time team? Sometimes the full-time team needs to use a certain skill a little bit each day or week, but needs the skill over all long period of time. In this situation, it could make sense to develop the skill on the team and have the part-timer act as an expert coach or reviewer until the full-time team members are self-sufficient. Teams who have all the skills needed for the work are often most productive.

About the author

Esther Derby's picture Esther Derby

A regular StickyMinds.com and Better Software magazine contributor, Esther Derby is one of the rare breed of consultants who blends the technical issues and managerial issues with the people-side issues. She is well known for helping teams grow to new levels of productivity. Project retrospectives and project assessments are two of Esther's key practices that serve as effective tools to start a team's transformation. Recognized as one of the world's leaders in retrospective facilitation, she often receives requests asking her to work with struggling teams. Esther is one of the founders of the AYE Conference. She co-author of Agile Retrospectives: Making Good Teams Great. She has presented at STAREAST, STARWEST and the Better Software Conference & EXPO. You can read more of Esther's musings on the wonderful world of software at www.estherderby.com and on her weblog at www.estherderby.com/weblog/blogger.html. Her email is derby@estherderby.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09