Master documenting requirements and increase project success.

Successful projects are built on the foundation of well-written requirements. In fact, many problems of challenged and failed projects can be traced back to requirements issues. In this course, you'll learn to document requirements clearly, effectively, and appropriately to create a solid foundation for project success.

In this course, you will learn the difference between validation and verification, and you will survey the various verification and validation techniques. You will learn to select the appropriate technique for each situation and apply it to ensure your requirements effectiveness.

This course covers the "Requirements Documentation" knowledge area of the Business Analysis Body of Knowledge (BABOK).

What You Will Learn

• Identify the various types of requirements
• Define each project member's role in requirements activities
• Distinguish between good and bad requirements
• Understand the requirements needs of each project member, including:

• Information needed and level of detail

• Business vs. technical point of view

• Need for formality

• Document functional requirements, Quality of Service requirements, and assumptions and constraints
• Apply good technical writing principles to writing requirements, including:

• The five Cs of technical writing

• Structuring techniques such as lists, tables, models, and graphics

• Formatting techniques such as white space, fonts, and headings

• Distinguish between validation and verification
• Ensure that the requirements are valid
• Verify that the requirements are effective

Hands-On Exercises

• Identify requirements phases in a generic product life cycle
• Identify requirements stakeholders
• Evaluate the effectiveness of requirements statements
• Identify the needs of requirements stakeholders
• Classify customer requirements
• Identify missing requirements
• Find violations of the five Cs in the customer requirements
• Identify where to use lists and graphics
• Identify where to use formatting techniques
• Hold a formal requirements review meeting

Who Needs to Attend

Business analysts, requirements analysts, technical writers, systems analysts, developers, software engineers, IT project managers, project managers, project analysts, project leaders, senior project managers, team leaders, program managers, testers, and QA specialists.

Suggested Prerequisites

Introduction to Business Analysis

Requirements Development and Management