Good Developer, Bad Teammate
I will start upfront and propose an idea: software development with a team is very similar to a competitive online computer game. As an experienced software developer and gamer, I can assure you that 80% of people will struggle with both activities, not because they are bad gamers or developers (in most cases, they are really good on their own), but often because they lack the experience of being a team player. Here is a list of activities on how to become a better team player.
Play the objectives
The most common reason why your team loses? It doesn't play the objective. In the dev world, each team has its own objectives. These could be short-term goals like sprint goals, delivering a milestone or a feature, and long-term goals that usually align with company goals. So, if you don't know the goal, you won't be able to reach it and win the game. Discuss your goals for the sprint, quarter, or next year during each planning session. Better yet, visualize them in the form of a roadmap with important milestones and share it with the team
Group up
In competitive games like The Finals, Apex Legends (which are typically 3-person teams), or Overwatch (usually 5-person teams), teams fight head-to-head. When skill levels are roughly equal and the fight drags on, the team with fewer players is at a disadvantage. Don't pick fights alone! Wait for your teammates, group up, and plan your next move together. Daily stand-ups can be the perfect time to discuss which tasks or user stories need extra support or resource allocation. Remember, the goal is to win, not how you do it.
Communicate well
Sure, communication is crucial in competitive games, but it's not about mindless chatter. Effective communication takes different forms: voice chat, text chat, and quick action pings ("Target spotted!", "Moving right!", "Need ammo!"). Remember, good communication is precise, informative, and concise. During daily stand-ups:
- Struggling? Speak up about it, clearly stating the issue.
- Blocked? Mention it and seek help.
- Smooth sailing? Describe your next action steps.
Stay visible and be aware what is going on around you. See and be seen
Don't be an asshole
Even if you are the skillfullest sharpshooter in CS:GO or the smartest Linux core developer, it doesn't mean you can be an asshole. Toxicity always drives people away and makes those around you weaker. Even in times of great pressure and tight timelines, be polite and calm, which will eventually lead you to greater social capital and a more pleasant workplace. Success is the result of the hard work of people who care –care about the product, championship, and the people they work with.
Win, praise the team. Lose, blame yourself
My basketball coach used to say, "If your pass fails, you're the reason." In a team loss, apply that principle during analysis. Think: "What could I have done differently to help us win?" Did you miss a crucial call? Was your aim off? Could you have improved other skills?
For missed deadlines, did you focus on the wrong tasks? (Remember: Play the objectives.) Did you lack communication or mislead teammates? There's always room for improvement. Don't brush it off and do your homework!
Conclusion
These ideas might seem like common knowledge, and I admit, I initially thought the same. However, during recent matches in The Finals, I was surprised by how many players simply ignore them. So, if you want to level up your team player skills – play more computer games.
Written by Igor