This course can be tailored to your needs for private, onsite delivery at your location.
IIBA (CDU)
ASPE is an IIBA Endorsed Education Provider of business analysis training. Select Project Delivery courses offer IIBA continuing development units (CDU) in accordance with IIBA standards.
This course offers 14.00 IIBA CDUs.
NASBA (CPE)
NASBA continuing professional education credits (CPE) assist Certified Public Accountants in reaching their continuing education requirements.
This course offers 17.00 NASBA CPEs.
PMI (PDU)
Select courses offer Leadership (PDU-L), Strategic (PDU-S) and Technical PMI professional development units that vary according to certification. Technical PDUs are available in the following types: ACP, PBA, PfMP, PMP/PgMP, RMP, and SP.
This course offers:
12.00 PMP/PgMP Technical PDUs
12.00 PMI-PBA Technical PDUs
1.00 PMI-ACP Technical PDUs
1.00 PMI-RMP Technical PDUs
1.75 PMI-SP Technical PDUs
1.00 PMI Strategic PDUs
1.00 PMI Leadership PDUs
In this business analysis course, you will learn how to manage requirements and requirement designs throughout the whole solution development life cycle, using a structured and standardized approach based on latest “Business Analysis Body of Knowledge” (BABOKTM) from IIBATM and various sources from PMITM.
Requirements Life Cycle Management is one of the six knowledge areas identified in BABOKTM and describes the tasks required to manage and maintain requirements and design information from their inception to their retirement. These tasks include establishing and maintaining meaningful traceability between related requirements, designs, and other related elements/components, maintaining requirement attributes/properties, prioritizing requirements, assessing impacts of requirements and/or requirement changes, and gaining consensus and approval on which requirements/designs to implement.
The purpose of requirements life cycle management is to ensure that:
- business, stakeholder, and solution requirements and designs are aligned to one another
- requirements attributes/properties (e.g. status, priority, etc.) are well maintained/tracked, communicated, and understood by all stakeholders
- solution implements requirements/designs that are in-scope and have been approved
- project teams have the required means and information to assess impact of proposed requirements and requirement changes
- targeted requirements/designs are developed and maintained for reuse (within or across projects)
*Please note, if you are taking this class as part of the St. Louis University Certificate requirements, there is a $500 fee to claim your certificate once you have completed ALL requirements.
- Upcoming Dates and Locations
-
All Live Online times are listed in Eastern Time Guaranteed To Run
- Course Outline
-
1. Business Analysis: Overview, Core Concepts
- 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)
2. Introduction to RLCM: Core Concepts
- Purpose
- RLCM and the BACCMTM
- RLCM Tasks:
- Trace Requirements
- Maintain Requirements
- Prioritize Requirements
- Assess Requirement Changes
- Approve Requirements
3. RLCM in the BA Context/Big Picture
- Where does RLCM fit in the SDLC framework (spectrum)?
- RLCM and the BA Core Concepts Model
- IIBA vs. PMI
4. Task: Trace Requirements
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
5. Task: Maintain Requirements
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
6. Task: Prioritize Requirements
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
7. Task: Assess Requirements Changes
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
8. Task: Approve Requirements/Design
- Purpose (WHY)
- Stakeholders (WHO)
- Inputs, Activities, Outputs (WHAT)
- Process, Guidelines, Tools, and Techniques (HOW)
- Knowledge Check and Practice
9. RLCM's relationships with other KAs
- Strategy Analysis
- Requirements Analysis & Design Definition
- Solution Evaluation
- Elicitation and Communication
- BA Planning and Monitoring
- RLCM [iterative & incremental]
10. RLCM in the context of related BA Perspectives:
- 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
Class Demos, Exercises, and Case Study
- Demonstrate (instructor) and practice (students) the topics covered in class, using Hands-on activities, examples, and case study
- Many individual, team, and whole-class exercises and discussions to check for understanding, review and apply/expand acquired knowledge and skills
Appendix:
- Case Study Information/Hand-outs
- Abbreviations, Glossary
- Who should attend
-
People who need to learn how to do it:
- Business Analysts
- any professional acting in the Business Analyst role
People who need to understand it:
- Project and/or Program Managers
- System Engineers (Analysts, Architects/Designers, Programmers/Database, etc.)
- Testers/QA
- Business partners