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 will behave and interact. The contract can differ from project to project.
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 also valuable project managers when you start a new project.
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.
In this article, Johanna Rothman explains why the size of a project team matters. Teams larger than 9 seems to have problems to communicate and teams smaller than 3 could lack the creative power to solve issues.
Meetings that encourage participation and building consensus are valuable, but true project team collaboration assumes shared responsibility and ownership to boost creativity and learning.
This video presents some surprisingly deep research resulting from a simple team-building exercise that involves dry spaghetti, one yard of tape and a marshmallow. Who can build the tallest tower with these ingredients? And why does a surprising group always beat the average?