Overview
Requirement lifecycle management is one of the six knowledge areas identified in the BABOK™ and describes the tasks required to manage and maintain requirements and design information from their inception to their retirement. This business analysis course equips participants with the skills and knowledge required for managing requirements and requirement design throughout the complete solution development lifecycle using a structured and standardized approach, based on the latest ‘Business Analysis Body of Knowledge (BABOK™)’ from IIBA™ and various sources from PMI™.
What You'll Learn
- Trace requirements’ relationships to/from other requirements and to/from other elements upstream (e.g. enterprise goals/objectives, mission/vision, values) and/or downstream (e.g. design/architecture, implementation components, testing, etc.)
- Capture/maintain requirements’ attributes (e.g. type, status, functional area, release, complexity, etc.)
- Assess and prioritize requirements (e.g. based on value to organization, value to customers, compliance, risks, etc.)
- Manage changes to requirements (e.g. identify and assess requests to change, analyze/document changes, create a business case, evaluate and approve changes, monitor change implementation, track changes, etc.)
- Manage project/product scope (e.g. define scope, agree/approve changes, avoid scope creep/gold plating)
- Plan, monitor and control implementation of requirements/design
- Manage requirements quality (e.g. identify missing/incomplete and/or bad requirements)
- Analyze impact of proposed changes to requirements/design
- Plan/optimize resource utilization
- Reuse requirements within and across projects and solutions
Curriculum
- What is a Requirement?
- Project vs. Product Requirements
- Requirements Engineering Overview
- Cost of Requirements Errors
- Business Analysis Core Concepts Model (BACCMTM)
- Requirement Levels and Requirement Types
- Systems Thinking
- SDLC Phases and Artifacts; Examples
- Knowledge Areas, Tasks, and Task Definition (Inputs/Outputs, Stakeholders, Guidelines & Tools, Other factors to consider)
- Purpose
- RLCM and the BACCMTM
- RLCM Tasks:
- Trace Requirements
- Maintain Requirements
- Prioritize Requirements
- Assess Requirement Changes
- Approve Requirements
- Where does RLCM fit in the SDLC framework (spectrum)?
- RLCM and the BA Core Concepts Model
- IIBA vs. PMI
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
- Strategy Analysis
- Requirements Analysis & Design Definition
- Solution Evaluation
- Elicitation and Communication
- BA Planning and Monitoring
- RLCM [iterative & incremental]
- RLCM in Agile
- RLCM and Business Architecture
- RLCM according to PMI
- Overview of PMI’s approach on RLCM
- PMI Publications, Resources
- PMI-PBA Certification
- Business Analysis Domains
- Requirements Management and Change
- Tasks covering/related to RLCM:
- Business Analysis Planning
- Requirements Elicitation and Analysis
- Traceability and Monitoring
Who should attend
The course is highly recommended for –
- Business analysts
- Project managers
- Program managers
- System engineers
- Testers
- Business partners
Prerequisites
There are no prerequisites for this course.
