Who wants to get up at 3 a.m. for a status meeting? This article shares valuable lessons about organizing and managing virtual teams with members around the globe, who have various skills, motivations, commitments, project affiliations and restrictions.
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 challenge is that individuals within an organization expect and deserve feedback on their performance, thus...
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.