Meetings, meetings, meetings ... you've got to have at least some to keep the team communicating, but which ones, why, and with whom in attendance? Check out one team's approach in their meeting-phobic environment; describing their critical "types" meetings in a way that portrays their practicality and value(!).
What this is
An example of the types of meetings one cross-functional product development team decided it needed during its project, and how they chose to document the purpose of each type of meeting to convey its practicality and value.
Why it's useful
Meetings are often an under-appreciated if not downright reviled part of project life. Done poorly, they can seem like a waste of time and energy and actually be counterproductive to the team's effectiveness together. Done well, though, they can enable thorough, timely, rich collaboration on the project. The key is to be clear about why any given type of meeting is needed.
The company that created these descriptions was new to project management and product development processes. The introduction of "process" was a jolt, and any meeting was not assumed to have value "just because." The project manager was a well-respected technical person; his clear articulation of why the various meetings were important went a long way toward gaining acceptance. His practical style matched the company's "just get it done" culture-no fancy words about why project management or meetings in particular are a good thing in general, just some plain-spoken words about what and why.
How to use it
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail email@example.com