The Latest

It's a pretty good bet that at some point in your career you and your work will be managed by someone who doesn't really understand what you do. Here are some ways to close the communication gap when you have a nontechnical manager.

Few people know intuitively how to manage process, projects, and people. Like anyone else learning a new skill, new managers need training, guidance, and mentoring. And just like technical staff, experienced managers need to keep their skills current and evolve with an evolving workplace. Technical Editor Esther Derby gives advice on how to develop your management abilities.

The Software Project Manager's Handbook is an excellent reference for the experienced or moderately experienced project managers who are looking to expand their "bag of tricks." Use this book as a reference to bone up on a specific topic, or use the case studies and questions to help you design and implement a feasible project plan.

Job interviews are stressful. Often, people are so eager to impress the interviewer that they don't find out critical information about the company and the position. But it's just as important for you to be convinced of the position's suitability for you as it is for the company to be convinced of your suitability for the position. If you ask the right questions, interviews can be much more productive at helping you avoid poorly managed, unhappy projects and zero in on well-run, professional projects.

Luisa Consolini tells us why the managerial side of quality is as important as the technical side. The precepts she imparts are: 1) there is something as bad as not doing testing—not managing it; 2) if you don't manage quality, you won't improve it just by applying some fancy quality techniques; and 3) people are not second to quality.

On June 4, 1996, the maiden flight of the Ariane 5 satellite launcher ended spectacularly after only forty seconds, with bits of the $67 billion vehicle and its payload spread over a fairly large part of French Guiana. The report issued July 19 by the International Inquiry Board noted that the fiery crash was due to a "chain of technical events." The details of that particular chain of events are reviewed here.