Critical Skills for Writing Better Requirements and Effectively Managing Requirement Changes

3-Day Workshop

Writing good requirements  is the first step in developing and delivering a successful product on schedule. A frequent cause of project delays and poor product reliability and usability is our inability to define, analyze, and manage changes to requirements.

In addition to consuming a lot of effort from the team, the creation of flawed requirements also leads to communication failures and conflicts amongst team members with divergent perspectives.

In this 3-day workshop you will: 

  • Gain practical expertise with the newest, most effective requirements gathering methodologies. 
  • Improve the outcomes of your development projects through better requirements elicitation will be boosted by engaging lectures, insightful demonstrations, and practical practice exercises. 
  • Obtain a complete grasp of the difficulties in creating accurate functional and non-functional requirements, as well as useful techniques for gathering and maintaining requirements.  
  • Learn how to manage requirements during the course of a product development project. 

Who is this workshop for: If you are involved in requirements gathering, managing or defining project scope, then this course is for you!

Course Outcome

After completing this highly interactive training, you will have the confidence to:

  • Lower development and maintenance cost due to ever-present scope creep
  • Create useful and comprehensive requirements that truly reflect customer needs and expectations
  • Understand which requirements require validation versus verification, and why
  • Design system requirements and architecture considering functionality, physical characteristics, reliability, usability, performance, interfaces, design constraints, COTS components, standards, and more
  • Perform requirements traceability and gap analysis. 
  • Link product hazard analysis, DFMEA, and usability output  to requirements
  • Understand how to plan and manage changes in requirements over the entire span of the development and sustaining process
  • Develop requirements templates and checklists that work for your product

Course Outline

Foundations of Requirements Development

There are several reasons why projects and products fail, and problems with defining requirements as are a primary cause. This section analyzes the issues projects face that lead to missed schedules and unacceptable quality, reliability, usability. This section will also explore some fundamental definitions, a framework and procedure for requirements development, and an example system that will be used in our practice sessions.

  • Goals of a product development project

  • Types of requirements errors

  • Definitions of terms

  • Types of requirements. Understanding the difference between environment, domain properties, requirements, specification, and implementation

  • Characteristics of well-written requirements

  • Requirements and the development life cycle. Understanding which requirements require validation versus verification, and why

  • Workshop: Gain an in-depth look at a hypothetical product (or your company's product) that you’ll be eliciting and managing requirements for during the course.

Eliciting Functional and Non-functional Requirements

This section examines a number of effective analysis methodologies to elicit and build functional and non-functional requirements.

  • Identifying stakeholders and user groups

  • Techniques for eliciting user requirements

  • Identifying data requirements

  • Identifying constraints and benefits, specifying exclusions

  • Capturing requirement attributes

  • Specifying requirements from the concept phase (pre-product development)

  • Problems with requirements elicitation

  • Writing different types of requirements (functional, performance, operational, interface, usability, security, reliability, etc.)

  • Workshop: You will analyze business artifacts and documents to discover the users’ functional and non-functional requirements.

Reviewing, Refining, and Validating Requirements

A successful project and product must have well stated requirements in order to satisfy the needs of the stakeholders and users. Identifying the requirements is the first step. The next step is to analyze and validate the requirements.

  • Writing requirements

  • The benefits and basics of Use Cases

  • Building a use case model, and deriving requirements from a use case

  • Reducing ambiguity

  • Analyzing requirements for validity, consistency and effectiveness

  • Validating requirements through reviews and inspections

  • Workshop: You will create a use case model for one process of your example product. You will identify and extract requirements from this use case. You will evaluate the requirements that have been written to identify any that do not meet the defined quality characteristics. You will practice rewriting any unclear or ambiguous requirements.

Eliciting Safety, Reliability, and Usability Requirements

The section covers the creation of requirements to ensure the effective implementation of risk control measures and the reduction or elimination of product risk. Also covered is the the need for defining usability requirements in enough detail to both instruct design and support adequate validation.

  • Writing effective risk control / mitigation measures from safety hazard analysis, DFMEA, and other safety processes.

  • Utilizing a single, consistent approach for writing clearly defined, objective, and measurable risk control requirements.

  • Incorporating features that provide resiliency, such as safety margins, and avoiding single-point- of-failure design

  • Usability requirements specification and metrics

  • 13 principles important for the analysis of usability requirements

  • Workshop: You will analyze product artifacts and documents (e.g. Risk Analysis, DFMEAs, etc.) to create requirements based on risk control measures (safety functions) and usability.

Requirements Change Management

Changes in requirement can begin as early as the point at which the requirement is elicited and can last beyond the product's release. This section covers the process of managing changing requirements during the requirements engineering process, new product development, and maintenance.

  • Allocation, traceability, and the management of changes to requirements.

  • Evaluating, executing, communicating, and validating changes

  • The Agile change management process

  • Creating an effective change plan

Contact us to schedule this course!

We can integrate our core training materials with your unique terminology and products to create a custom workshop to maximize the benefit for your team.

Thank You