Customer-Centered Products: Creating Successful Products Through Smart Requirements Management »

"Ivy F. Hooks (Fair Oaks Ranch, TX) is president and CEO of Compliance Automation, Inc. She has provided training and consulting in requirements for a variety of corporations and government organizations, including Kodak and NASA.

Kristin A. Farry (Friendswood, TX) is an engineer with over two decades' experience in aerospace, robotics, and biomedical engineering."

When your product development process fails, do you blame scarce resources or unforeseen technical challenges? Those may be factors, of course, but most product failures and development rework can be traced to a poor understanding of customer-centered needs and requirements. This book will show you, as a manager, how to prevent failure by guiding and empowering your people to define and understand the right requirements early in the product development cycle.

Drawing on their 50 combined years of real-world product development experience in many industries-including aerospace, medical, transportation, insurance, and military applications-the authors spell out exactly what's involved in "doing it right the first time." They provide tested methods for defining hardware and service products as well as software, a true rarity in handbooks on requirements.

Whether you manage product development, procurement, or service, it's possible, and even likely, that you lack formal training in requirements definition and management. This book fills that educational gap by offering the necessary fundamentals and framework. Uniquely, it helps you examine your organization's culture and work environment with an eye toward how it helps or hinders product development. It also positions you to take advantage of automated tools for managing requirements, with proven techniques for increasing efficiency

Through step-by-step analysis and enlightening reallife examples, you'll learn how to:

Assess weaknesses in your current requirements process.

Create a big picture roadmap for your project.

Capture critical data on customer needs, budget and scheduleconstraints, and management responsibilities.

Apply operational concepts and interfacesi.e., detailed scenarios of how people will use your products in the real world-to build quality in from the start.

Bridge communication breakdowns that lead to ambiguous, inconsistent, or missing requirements.

Manage layers as well as levels of requirements on complex projects.

Design with product testing and verification in mind.

Document your requirements uniformly and prioritize them to control risk.

Measure requirements quality throughout the development cycle.

Integrate the inevitable changes that arise.

By improving the fit between your products and your customers' needs, and by streamlining your development process, you'll achieve the Holy Grail of product development. Let Customer-Centered Products show you how to make your products "faster" and "cheaper"without sacrificing "better."

Booknews

Shows how to define and understand the right requirements early in the product development cycle, providing tested methods for defining hardware and service products as well as software. Explains fundamentals of requirements definition and management, and shows how to analyze an organization's culture and work environment with an eye toward how it helps or hinders product development. Hooks is president and CEO of a training and consulting firm. Farry is an engineer and pilot, and cofounder and president of a bionics company. Annotation c. Book News, Inc., Portland, OR (booknews.com)

1. Requirements: Structure for Success
2. Why Johnny Can't Write Requirements: Cultural, Educational, and Management Influences of Requirements Definition
3. The View from the Top: Steps to Creating and Managing Good Requirements
4. Creating a Shared Vision: Scoping the Project Up Front
5. One Day in the Life of a Product: Using Operational Concepts to Improve Requirement Quality
6. Collision Course: Identifying and Managing Interfaces
7. Be Careful What You Ask For: Writing Good Requirements
8. Theirs But to Reason Why: The Value of Recording Rationale
9. Everything in Its Place: Levels, Allocating, and Tracing Requirements
10. But Will It Work? Thinking Ahead to Verification
11. A Needle in a Haystack: Formatting Requirements
12. Drawing a Line in the Sand: Preparing to Baseline Requirements
13. Not All Requirements Are Created Equal: The Case for Prioritizing Requirements
14. Keeping Sane: Automating Requirement Management
15. Death, Taxes, and Requirement Change: Managing Change
16. Cap'n, Are We There Yet? Measuring Requirement Quality
17. It Can Happen On Your Watch: Making Changes in an Organization's Requirement Definition Process