"Without a method [like this], the user giveth and the developer taketh away."  - Steve Bender

Requirements Series WEBinar

Part 4: Resolving Requirements Conflicts and Inaccuracies

Abstract: This WEBinar series shows a 6-step process for gathering, analyzing, and checking business requirements in a more defect free way.  

This WEBinar shows all parties how to resolve requirements conflicts, to verify, and to validate requirements.

Part 4: Resolving Requirements Conflicts and Inaccuracies

• Parts 4, 5, and 6 of the model
• Resolves conflicts, verifies, and validates requirements
• Delivers final statement of requirements
• Understand the balance between the costs and the benefits of the new requirement 
• Resolve technical conflicts between what users want and what is economically achievable with technology 
• Use risk assessment to properly balance benefits with hidden costs and risks 
• Balance structural software characteristics to minimize software failure 
• Resolve emotional conflicts between different groups that sometimes arise
• Verify requirements with various models and measurements to prove requirements are correct 
• Minimize high cost of erroneous requirements 
• Prevent propagation of incorrectly installed (and otherwise correct) requirements

This WEBinar (rqts conflicts) will go deeper into the strategies and tools used in the final Steps 4, 5, and 6  the Quality Requirements Model. (See table below.) 

The Requirements Model is a 6 step requirements gathering process useful for end users, business analysts, and developers.  By means of its structure, it automatically assures mission-based, needs-based requirements that are not solutions-driven.  

Resolving Conflicts and Trade-offs 
What to do—without playing the “You-bet-your -job-game” - when, for example:  

• Users can’t agree and are scrimmaging

• Business analysts are ignoring customer input

• Customers are ignoring business analysts

• Powerful people are skirting or manipulating the priority-setting process …and other requirements gathering people-related problems?

Answer: Agree on a process to resolve these conflicts like the process we'll demonstrate in this WEBinar. 

Verifying Requirements

The objective of Step 5 - Verify Requirements is to ensure that the requirements in the Statement of Requirements do, in fact, not only meet the business need but are also defect-free. 

Important Points about Validating Requirements

Many of the tools in this step ought to be carried out by or with the assistance of the customer. 

The more tools that are used, the higher the quality of the requirements. 

Defects During Requirements Definition

The following are defects that frequently occur during the requirements definition phase because they are inadequate or partially missing: 

• Operating rules (or information)
• Performance Criteria
• Environment information
• System mission information 

Validating Requirements, Step 6 
This WEBinar will describe important techniques to quality control check the accuracy of the Final Requirements Statements before they are distributed. In addition, important techniques will be shown to insure that these correct, QC'ed requirements are correctly installed. 

This WEBinar series describes how to prevent requirements defects and how to gather those requirements more accurately.  Complete information on the full course on requirements can be found here. 

Conducted Wed. June 6, 2012

Register Now 

Want to catch up with part 1? Click Here.

Want to catch up with part 2? Click Here.

Want to catch up with part 3? Click Here.

Please insure all payment and registration name, phone, and email addresses are those of the attendee,  even if the cardholder is different. Why?

All WEBinars now 1 hour and 15 minutes in length.

On Demand DVD now available when ordered along with recording below.  To add this to your order, click here first or learn more.

"On Demand" recording

$24.95 USD

Key Objectives

Note: For more detail on the key learning objectives of the full course go to Requirements Gathering.