2010/10/27

Congratulations! You just broke the team!

Infighting. Every team has it to some point. The testing team complains that the developers screwed up the application. The developers blame the business analysts for incomplete/incoherent requirements. The BA’s blame the testing/dev groups for misinterpreting the requirements or interpreting them instead of asking for clarification. The project manager blames everyone for slipping deadlines.

Some conflict is expected within any group. There are, however, lines that need to not be crossed. We are all part of this thing for a reason. Let’s give each other a bit of respect and we can get through our day-to-day much easier. Mutual respect is required for all silos/individuals on the team.

Saying to external teams that you have no confidence in one of the internal teams to deliver on what they are paid to do is incomprehensible. Questioning a team members motives on how they spent a vacation day that was scheduled weeks in advance is ludicrous. Demanding that other teams work nights and weekends when you don’t do the same is selfish. Throwing a fit when an individual says “NO!” to working over a holiday weekend because you don’t celebrate the same holiday is appalling.

Below is a brief list of what is being halted whenever I have to deal with this infighting:

  • I investigate new methodologies and technologies
  • I scrutinize every line of code
  • I monitor data page utilization
  • I remove redundancy
  • I optimize methods and queries
  • I normalize datasets
  • I take long running processes down to a tenth their initial time
  • I plan for scale
  • I visualize data sets and workflows the way most people see pictures
  • I read countless blogs, tweets, message boards
  • I teach more junior developers how to use existing frameworks
  • I collaborate with my peers
  • I document the system
  • I design new features
  • I prioritize deliverables
  • I fix bugs
  • I update data
  • I spec hardware
  • I evaluate new software
  • I verify we are licensed properly
  • I write .Net
  • I read Java
  • I understand PHP, ForTran, COBOL and more
  • I relate the data
  • I connect the networks
  • I make the impossible possible
  • I tell you when the impossible really is impossible
  • I can *DD the hell out this shit
  • I can make fat objects light and anemic domains rich
  • I’ve came in early, stayed late, worked weekends and holidays

I am Paul Montgomery. I am good at what I do. I do this shit for a living because I am good at it. I am a pretty damned big deal. I do all I can to surround myself with highly capable people. I will not tolerate treating any member of my team without respect.

Comments