Agile Blog Sponsored By  Agile Sponsor    Agile Sponsor   

 

 



15 Characters To Assess Teamsmanship


Written by  Ravi Vadugu | 29 December 2011
E-mail PDF

Agile TeamsOne of the first hurdle that any projects comes across is ability to gel as a team to deliver projects. Specifically when the teams are adopting agile where the key focus is around people and teams. The shift in ways of working from traditional to lean methods puts the teams at great discomfort to start with and often determines if you are able to adopt to agile or not. 

One of the projects that i am working on right now, i am into a similar situation where there is ample amount of conflicting ideas on how a task has to be done and not to mention lack of trust. While putting an attempt to find out what makes a good team, i came across Patrick Lencioni's book "The FIVE DYSFUNCTIONS of a TEAM" which highlights following few points on what makes an effective team. I have got atleast some pointers to what we as a team should work towards from this leaf in his book.

  • Team members are passionate and unguarded in their discussion of issues.
  • Team members call out one another's deficiencies or unproductive behaviors.
  • Team members know what their peers are working on and how they contribute to the collective good of the team.
  • Team members quickly and genuinely apologize to one another when they say or do something in appropriate or possibly damaging to the team.
  • Team members willingly make sacrifices (such as budget, turf, head count) in their departments of areas of expertise for the good of the team.
  • Team members openly admit their weadnesses and mistakes with each other.
  • Team members are compelling, and not boring.
  • Team members leave meetings confident that their peers are completely committed to the decisions that were agreed on, even if there was initial disagreement.
  • Morale is significantly affected by the failure to achieve team goals.
  • During team meetings, the most important and difficult issues are put on the table to be resolved.
  • Team members are deeply concerned about the propect of letting down their peers.
  • Team members end discussions with clear and specific resolutions and calls to action.
  • Team members challenge one another about their plans and approaches.
  • Team members are slow to seek credit for their own contributions, but quick to point out those of others. 


Ravi Vadugu

Ravi Vadugu

An IT professional with over 12 years of experience. Project management is what i do. Curious/Interested in upcoming technologies, trends, software methodologies(e.g. Agile) and software tools. Love sharing knowledge with rest of the community.

blog comments powered by Disqus