Assembling a group of people and declaring them a team doesn’t make them one. Do you have the conditions necessary for the team to form? What activities have they completed to help them find an identity, their purpose, and how they’ll interact with each other?
The age-old expression "you never get a second chance to make a first impression" is still true to this day. So often the way we greet people, or fail to greet them, sets an irreversible path of leaving others feel completely unwelcome, even if that wasn't the intention.
Many developers and testers are familiar with test-driven design (TDD), but how can managers use it to drive project implementation? In this article, John Goodpasture offers a guide to TDD design from the project manager’s perspective.
We put a lot of emphasis on being Renaissance workers, able to step comfortably from one job role to the next. But, as Mitch Lacey describes here, not all roles play nicely with each other, and trying to combine them may lead to disaster.
In this excerpt from Leadership, Teamwork, and Trust: Building a Competitive Software Capability, Watts Humphrey and James Over explain why these changes must be a high priority for software companies and other organizations for whom knowledge is a valuable asset.
In most workplaces, there’s an institutional hierarchy that may influence how we react in situations that require us to step up. Navigating effective communication means knowing when we should listen quietly to leaders and when we should challenge or question.
Inspired by the success of India’s Weekend Testing movement, Michael Larsen saw a need for a group closer to home. The Weekend Testing Americas chapter invites testers from across the Western Hemisphere to join an informal, distributed group of their tester peers to learn and perfect their craft.
The portions of projects that are not yet complete occur in the future. Since the future is an uncertain place, there will always be surprises. Some surprises are so obvious that they should hardly be called surprises at all. This is the kind of surprise that project management helps to avoid.
Having similar motivations and processes may help to establish a team, but you and your coworkers won’t be the best teammates you can be until you also have each other’s back. Here, Johanna Rothman and Gil Broza describe valuable approaches to whole-team support, including banking trust and building shared responsibility.
The Blue Ocean Strategy gives important insights regarding how to create new market space in uncontested markets thereby making the competition irrelevant. This strategy can be adopted to explain the significance of agile methodologies as compared to the Waterfall method of software development.