Team Member's Survival Guide by Jill A. George and Jeanne M. Wilson Lack of training is nearly always identified as a major barrier to successfully establishing a team-based structure. This self-study handbook is aimed squarely at overcoming that barrier by educating employees about their new roles and the team implementation process. The oversized paperback divides team implementations into a three-part framework: preteam, new team and mature team activities. Preteam activities describe the larger organizational rationale for teams and establish the vision, mission and strategy. New team activities are divided into two sections, based on the initial formative issues and team-maintenance issues. Mature team activities address the team's continued vitality and the shift of focus from developing the team itself to the organization's greater needs. The three phases (four, really, since the new team phase is divided into two sections) are discussed in a monthly progression. The authors use a two-year format that assigns six months for preteam activities, 13 months for new team development and five months for mature team activities. Each new month introduces new concepts to the reader. The concepts are described at a level most employees should be able to understand and are reinforced with one or more exercises and assessments. The presentation utilizes plenty of illustrations and well-planned white space to maintain the reader's interest. Team Member's Survival Guide (DDI Press, $29.95) is a creative look at the role and responsibilities of employees participating in work teams of all kinds. It is integrated for use with DDI's previously published Team Leader's Survival Guide.
Software Excellence Edited by Shigeichi Moriguchi The popular perception of software creation usually includes eccentric, disheveled programmers banging away at their keyboards while chugging cola and wolfing pizza. Software Excellence, a massive look at the application of total quality management to software development, goes a long way toward eliminating that perception by describing a rational, high-quality development process. Although quality in software, according to the Japanese author team, depends on many of the same factors as other products, it is also unlike other products in that the design process is the essence of software production, and this process is usually conducted by small teams of programmers. As you might expect from a Japanese book on quality, these small teams are a primary force in software quality control activities. The book is organized into a series of long chapters devoted to important issues in software quality. These include reliability, modularization, documentation, software engineering techniques, the application of quality function deployment in software development, measurement, and test and audit. As in many team-written books, these issues are not well-connected, so reading the book in a linear fashion is difficult. It is also difficult to evaluate the overall value of Software Excellence (Productivity Press, $90). The information on TQM is certainly pertinent, but two primary concerns remain. First, are the primary development issues of 1990 still relevant in the fast-changing world of software? Second, given this country's leadership position in software development skills, are the Japanese even the best source for information regarding software quality? |
|
|