Producing Effective Requirements

Registration Fee: $795.00 per person

Team Registration Fee (3 or more attendees): $695.00 per person

Availability - On Site In Person, Private Virtual Classroom, Open Enrollment
Duration - 2 Days In Person - 12 Hours Virtual
 
Overview
 
Learn the latest techniques for eliciting requirements and transitioning them into requirements that are implementable.  Demonstrations and realistic practice exercises provide you with confidence to improve project outcomes through better requirements.  Gain a thorough understanding of the challenges faced when correctly defining requirements.  Learn practical approaches for refining requirements, as well as strategies for managing requirements throughout the project life cycle.  If you participate in any requirements activities you can’t afford to miss this workshop! This workshop is very interactive with over a dozen activities in two days.  This workshop is compliant with BABOK® Version 3. 
 
Audience
 
This workshop is valuable for those in the role of a business analyst regardless of title (business customer, systems analyst, designer, developer, team leader or project manager).
 
Learning Outcomes
 
Upon completion, the participants will be able to:
 
  • Analyze project information and other organizational assets to uncover initial requirements.
  • Implement practical methods for understanding the various types of requirements and assess their impact to downstream designers and builders.
  • Apply questioning techniques to refine requirements and make them more effective.
  • Gain exposure to alternate ways of communicating requirements.
  • Conduct a requirements interview.
  • Package and organize requirements depending on the receivers of those requirements.
  • Apply various validation methods.

Topics Addressed
  • Requirements: What are they?
  • The Life of a Requirement: Iterative Elicitation and Analysis
  • Making Requirements Effective
  • Assessing and Validating the Solution

Virtual Classroom Schedule
 
Virtual classroom sessions are conducted as follows:
1:00 pm to 5:00 pm DAILY, Eastern Time (New York)
 
Virtual sessions are delivered using Cisco Webex Meeting Center. When you join the online meeting using the link provided in a confirmation email, you will be asked to either phone a US toll number or connect using a computer head set. If you phone in to the audio conference using the toll number provided, long distance toll charges will apply. If you connect using a computer head set with microphone (VOIP), no toll charges will apply.  
 
Agenda
 
Part 1 - Requirements: What are they?

Part 1 focuses on putting context around the requirements and the activities to uncover them. We address the benefits of conducting requirements engineering activities for every initiative and the challenges faced when performing those activities.  We also identify and plan how these activities fit within business analysis and their impact to future deliverables.

  • Defining Requirements Engineering and Business Analysis
    -  Terminology 
    -  Business Analysis Framework
    -  Requirements Development vs. Management
    -  Activity: Terminology Map
    -  Requirement Types 
    -  Characteristics of an Effective Requirement
    - Activity: Is it a Requirement?
 
  • Requirements Engineering Challenges
    -  Accounting for Requirements Activities
    -  Cost of Requirements
    -  Avoiding Analysis Paralysis
    -  Requirements and Project Dates
    -  Requirements Impact to Other Activities and Deliverables
    -  Activity: Map Your Deliverables
 
  • Prior to Projects
    -  Assessing Problems and Opportunities
    -  Developing a Request for Information
    -  Reviewing Initial Information
    -  Activity: Case Study Assessment
 
  • Project Start
  -  Collaborating with the Project Manager
  -  Using Project Management Deliverables to Get Started
  -  Adaptive vs. Predictive Approaches
  -  Validating Scope – The Context Diagram
  -  Activity: Which Approach Would You Use
  -  Stakeholder Analysis and Maps
  -  Intentionally Address Communications
  -  Requirement Roles and Responsibilities
  -  Plan for the Management of Requirements
 
Part 2 - The Life of a Requirement: Iterative Elicitation and Analysis
 
Part 2 focuses on the life of the requirement that changes throughout the initiative as more information is learned, more questions are asked and answered, as assumptions become clarified and scope is more clearly defined.  We will take the participant through the analysis phase of a typical project and help them move requirements to a more structured state by asking the right questions and ensuring that additional requirements are uncovered. A starter set of questions will be provided. This session will focus on just a few, but lengthier, activities. 
 
Requirements evolve into different levels, types and states.  
 
  • Eliciting Requirements
   -  Activity: Build a Stakeholder Diagram
   -  Elicit Stakeholder Requirements
   -  Elicitation Techniques for Stakeholder Requirements
   -  Tap into Core Communication Skills
   -  Getting to the Questions 
   -  Activity: Prepare and Conduct an Interview or Meeting
 
  • Analyzing for More Effective Requirements
   -  Systems Analysis Concepts
   - Using Diagrams and Models
   -  Applying Gap Analysis Techniques (KRAC)

  • Further Refining Requirements 
   -  Moving from a Stated Requirements to Verified
   -  Reducing Assumptions
   -  Class Discussion: Assumption Games
   -  Identifying Trigger questions
   -  Level of Detail and Questioning
   -  Level of Detail Variances
   -  Leveraging State Transitions
   -  Moving from Verified to Structured
   -  Activity: Practice Verifying and Refining Requirements
 
Part 3 - Making Requirements Effective
 
  • Considerations When Writing Requirements
   -  Requirement Communication Trap 
   -  Requirement Characteristics
   -  Documenting in Natural Language 
   -  Remove Ambiguity
   -   Reduce Complexity
   -  Add Structure
   -  Activity: Add More Structure to Your Requirements
 
  • Alternatives and Supplements to Natural Language
   -  Use Cases for Elicitation and Documentation
   -  Decision Matrix or Trees
   -  Modeling (Various Notations)
   -  Relationship or Comparison Matrix
   -  Activity: Build a Decision Matrix or Write a Use Case
 
  • Packaging Requirements 
 
-  Forms for Presenting
-  Putting Context Around Requirements
-  Requirement Attributes 
-  Prioritization Techniques
-  Steps for Putting Together a Requirements Package
-  Activity: Package and Document Your Requirements

Secion 4 - Assessing and Validating the Solution

How will you know the requirement has been met? How will you know what is impacted when a requirement changes? How will change be managed during the solution build?  

  • Tracing Requirements 
   -  Ensuring Verifiability
   -  Reviews and Baselines
   -  Managing Scope through Traceability
   -  Changes to Requirements
   -  Class Discussion: Build a matrix to trace requirements

  • Implementation Considerations 
   -  Organizational Readiness
   -  Transition Requirements 
   -  Evaluate Performance of Solution
   -  Requirements for Re-use
   -  Class Discussion: Identify transition requirements
 
  • Requirement Risks
   -  Gold Plating
   -  Lack of Stakeholder Participation
   -  Unrealistic Customer Expectations
   -  Unrealistic Timeframe for Analysis
   -  Requirement Volatility
   -  Activity: Situational – What Would You Do?

  • Method of Validation – Requirements and Activities

   -  Walkthroughs and Inspections
   -  Evaluate Performance of Activities
   -  Validation of Requirements through Testing   
   -  Activity: How Well Did We Do?
   -  Activity: Workshop Lessons Learned