Requirement Definition is more than writing requirements. Requirement Definition encompasses two critical activities…defining the scope of the project and defining the requirements that align to that scope. In this two day class, you will learn how to:
To define project scope so that your projected is bounded, you have buy-in and agreement from your stakeholders and you have the information you need to write requirements and deliver a requirements specification.
Write requirements to best practices and avoid writing defective requirements that are ambiguous, state design, are at the wrong level, are incorrect, incomplete…any number of problems that lead to rework and potential overruns.
Understand how to bound the scope of your project/product and manage to that scope.
Learn what information needs to be collected to produce a Scope Definition Document.
Learn how to conduct a Scope Review and Scope Risk Assessment to get buy-in from all stakeholders and confirm you are ready to being writing requirements.
Discuss the cause and impact of requirement defects on project and product success.
Learn how to write good requirements and avoid writing defective requirements.*
Discuss rationale and understand how it can be used to ensure requirements are understood only one way.*
Learn how defining the verification method for each requirement can be used to validate the requirement as written is testable.*
Understand levels of requirements and the basics of allocation and traceability between levels.
Learn the importance of using templates for preparing and organizing your requirements specification.
Understand the sources and categories of requirements – functional and performance, interface, operational, “-ilities” (such as reliability and supportability), physical, environmental, and design and construction categories.*
* Includes examples and student exercises
Day 1: Scope Definition
How to bound your project (product) by defining its scope
How to clearly define the need, goals, and objectives for your product
How to define stakeholders and to involve them in early scope activities
How to develop operational concepts to ensure complete life-cycle coverage
How to determine your interfaces
How to determine if you have a reasonable risk to proceed to writing requirements
Day 2: Writing Good Requirements
Understand why we have bad requirements
How to recognize and write good requirements
Understand common mistakes when writing requirements
The value of recording rationale
Thinking ahead to verification
Levels, allocation, and tracing requirements
Documenting requirements – templates
Writing different types of requirements (Functional and Performance, Operational, Interface, Physical, -ilities, etc.)
This training is critical for those responsible for capturing and documenting requirements. Representatives of all the product’s stakeholders will be involved in developing, reviewing, and approving requirements, and this training will benefit them and your requirement effort.
System Engineers (SE)
Requirement Engineers (RE)
Business Analysts (BA)
Subject Matter Experts (SME)
Program and Project Managers (PM)
Independent Verification and Validation (IVV) Team
Build On This Training
If your organization is looking for additional training, also consider 3-day seminar where we also cover “Managing Requirements” in the third day.