I’ve borrowed both the title of this post and the following picture from Don Carew, Eunice Parisi-Carew and Ken Blanchard to illustrate what your team will go through for each event of the Winter Scripting Games.
Note: I’ll use italics whenever I quote the above authors or someone else.
(TDS = Team Development Stage)
There are two key variables. Productivity is the team’s ability to work together and achieve results. Morale is the team’s motivation, confidence and cohesion.
After each team member read the whole event description (including the criteria used by the judges for scoring), you and your team should immediately go through the first stage (TDS1) called orientation where productivity is low (you didn’t write any code yet) and morale is moderately high. Team members are moderately eager and have high expectations. They need direction and have some anxiety about their roles and their connections with the team.
To go through phase 1, you and your team will need to adopt a structuring approach. I think that you’ll need to:
- Identify the main goal of the event
- Identify skills among your team
- Divide to conquer
- Clarify roles
For the practice event, the main goal could be: inventory servers by scanning an IPv4 subnet, gather data like the CPU, RAM,…installed components and save data to files in a reusable format.
You should split each problem into tasks and create one function to achieve one task. Each function should do one single thing and do it well.
Make sure that each member in your team has had a role assigned, i.e. is responsible for writing the function that does this…
Now each team member starts his journey and writes some code 😀 …
… and your team is actually slowly moving toward phase 2 (TDS2) called dissatisfaction.
Productivity is low to some. Skills and knowledge are slowly developping. Some results are occuring. Morale is low. There is a discrepency between expectations and reality. Team members have feelings of anger, frustration, confusion and discouragement.
This is in my opinion the most difficult phase to overcome.
As soon as you feel that morale is at its lowest point, it means that you matured enough to share your code on the scripting games site and get the help of coaches.
Coaches will do their best to provide high quality support and direction to your team. Resolving is the keyword for this phase. But don’t get me wrong. Some conflicts may arise among your team. You’re on your own to solve these conflicts. My last advice about this situation is that you’ve to listen and you can also use a tool like the “ladder of inference to avoid jumping to conclusions”. The following article provides some tips that may help you.