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

  • 4h 26m
  • Ivy F. Hooks, Kristin A. Farry
  • AMACOM
  • 2001

"Never time enough to do it right, but always time enough to do it over." In today’s "faster-better-cheaper-at-any-cost" world, this is not just a joke, but an all-too-frequent reality. And, most often, a poor understanding of the requirements for a product is the reason it must be done over.

Customer-Centered Products is a highly practical new book that helps readers gain a clear understanding of how to elicit the right requirements early on in a project--and make the right product the first time. Packed with useful information, enlightening real-life examples, and money-saving solutions, this book shows readers how to:

  • Identify where their current requirements process is weak
  • Bridge communication breakdowns that lead to muddy requirements
  • Eliminate costly mistakes and rework
  • Improve product quality without increasing cost
  • Use operational concepts to improve requirements quality
  • Improve the fit between the product and the customers' needs
  • Prove that faster, better, cheaper is possible, and more.

About the Authors

Ivy F. Hooks is a nationally renowned expert in requirements development and management. She is the president and CEO of Compliance Automation, Inc., in Boerne, Texas, a firm that provides training and consulting in requirements for organizations such as the U.S. Navy, Rockwell-Collins, and Kodak. For 20 years, Ms. Hooks was a manager at NASA. She holds B.S. and M.S degrees in mathematics.

Kristin A. Farry is an engineer and pilot with more than 20 years of experience in aerospace, robotics, and biomedical engineering. She is the cofounder and president of Intelligenta, Inc., a bionics company. Dr. Farry has also been a U.S. Air Force captain and a space shuttle flight controller at Rockwell. She holds B.S., M.S.E., and Ph.D. degrees in aerospace and electrical engineering.

In this Book

  • Requirements—Structure for Success
  • Why Johnny Can't Write Requirements—Cultural, Educational, and Management Influences of Requirement Definition
  • The View From the Top—Steps to Creating and Managing Good Requirements
  • Creating a Shared Vision—Scoping the Project up Front
  • One Day in the Life of a Product—Using Operational Concepts to Improve Requirement Quality
  • Collision Course—Identifying and Managing Interfaces
  • Be Careful What You Ask For—Writing Good Requirements
  • Theirs but to Reason Why—The Value of Recording Rationale
  • Everything in Its Place—Levels, Allocating, and Tracing Requirements
  • But Will It Work?—Thinking Ahead to Verification
  • A Needle in a Haystack—Formatting Requirements
  • Drawing a Line in the Sand—Preparing to Baseline Requirements
  • Not all Requirements are Created Equal—The Case for Prioritizing Requirements
  • Keeping Sane—Automating Requirement Management
  • Death, Taxes, and Requirement Change—Managing Change
  • Cap'n, are We There Yet?—Measuring Requirement Quality
  • It Can Happen on Your Watch—Making Changes in an Organization's Requirement Definition Process
  • Endnotes
SHOW MORE
FREE ACCESS