The article “Moneyball for software engineering” explains how metrics-driven decisions can build better software teams. The basic idea is that organizations can use statistical data to build more competitive teams. Most of us work in...
In this blog post, Gary Reynolds explains why the traditional appraisal systems (performance reviews, 360 feedback, evaluations) are in conflict with Agile values because they focus on the individual and not on the teamwork. The...
This video presents the social contract. It contains a set of rules a team agrees to, that are above and beyond what their basic project roles and responsibilities mandate. It consolidates everyone’s understanding of how...
The Team Software Process (TSP) provides a framework to predictably and effectively build software-intensive products. It relies on data collected by team members to provide insight into how a software project is operating.
In this blog post, Tomek Kaczanowski share a checklist of things to do when you take over a software project as a technical team lead. The list contains more than 60 items that could be...
Mistaken beliefs about teamwork that can sidetrack productive collaboration. This blog post from J. Richard Hackman presents six common teamwork misperceptions.
In this video, Cisco CEO John Chambers explains how abandoning command-and-control leadership has enabled the company to innovate more quickly, using collaboration and teamwork.
Meetings that encourage participation and building consensus are valuable, but true project team collaboration assumes shared responsibility and ownership to boost creativity and learning.
Last Comments