Why are some teams successful while others are less than stellar? Can teams use processes to do their work? How can managers help teams to become better? And do we need incentives to improve the quality of software? InfoQ did an interview with Simon Brown about sustainable competence for continuous improvement, balancing people and processes, and software quality and architecture.
Why go an entire year before receiving feedback? Nothing else in the Agile world waits a year, why would feedback? Struggling to make feedback objective? Perhaps objectivity is the wrong goal perhaps reviews should be subjective. Ryan Hagan offers his approach to doing performance reviews with an Agile Team.
In his book, iTeams – Putting the “I” Back Into Team, author William E. Perry demolishes the cliché - "There is no ‘I’ in team." As Perry explains, the phrase is nonsense because it is the individual differences in team members that make teams great. In this interview, Ben Linders explores with the author the motivations for writing the book as well as some of the key thoughts.
The new brain science (social neuroscience, positive psychology, and imaging techniques) give us tools for understanding and enhancing the ability of men and women to work together. 27
This article describes the components of a successful team and how we built such a team. 10