Learning Objectives

• insight in the consequences of working without a requirements document;
• understand the importance of a succinct, signed-off requirements document (RD) for project success;
• minimize misunderstandings by using SMART to write requirement; and
• learn a “light” requirements document process.

Project success is more likely to happen when a project begins well. Effective requirements discovery, analysis and documentation practices are key factors to achieve this. It's a dirty secret that requirements are often not documented in detail at the start of projects or at all. For some reason the thought is that a “Requirements Document” will just slow things down.

As a result there is an abundance of misunderstandings concerning expectations, project scope, deliverables and many more things. Missed schedules, cost over-runs, restarts, are some of the results of not establishing requirements clearly upfront. Determining requirements that satisfy the actual customer needs at the start of the project greatly enhances the chances for project success. Requirements are the foundation to both the product and project life cycles.

Writing good requirements takes time and practice, and, even with all the new tools designed to help you, it will not happen overnight. You need a clear and organized mind, excellent communication skills and good people skills. This presentation will provide you with tools to minimize misunderstandings around requirements and with a “light” requirements document template so you can start your project right.