Course Category: Fundamentals
Course Duration: 1 day
Course Credit: 7 PDU
You need information and stakeholder buy-in prior to writing requirements. We call the collection and documentation of this information “Scope”. Whether you begin writing requirements with a clean slate or respond to a customer’s set of requirements, understanding the Scope of the product is essential prior to writing, reviewing, or implementing requirements.
Failure to address Scope prior to writing requirements is one of the major reasons for continuous requirement rework and failure to obtain a good set of requirements in a timely manner. No one can write requirements without a vision. Without a documented Scope, each author will have a different vision and the resulting requirements will be woefully defective. Efforts to identify defective requirements are not only time consuming, but fraught with arguments between team members who have different visions. Due to time constraints, you will find yourself in verification before you uncover all the requirement defects.
Learning how to gather and document Scope is one of the most productive steps you can take to improve your requirements. Information documented in the Scope definition phase will support the design and verification efforts and can reduce your schedule by 30% or more from start to finish.
To build a firm foundation for defining, interpreting, and verifying requirements.
Develop skills to enable you to:
* Includes examples and student exercises
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.
You may not need this course if:
If your organization is looking for additional training, also consider our 2- and 3-day seminars where we cover “Scope Definition” in the first day.
View our public course schedule and register.