Project :Industry: Security, Manufacturing, Human Resources, Research and Development Services Provided: Project Management, Organizational Change Management Company: The client is a global leader in
High-Level Project Requirements Framework
Purpose. This framework helps define the activities and approach we will use in developing, evaluating and verifying business & technical requirements for the most XXX projects.
Requirements Framework Overview. The requirements framework is a 4-phase framework conducted in the concept and definition phases of the Project Management Methodology (PMM). The table below outlines the focus, major activities and desired outcomes from each requirements phase.
| Requirements Phase | Major Activities | Desired Outcomes |
| Requirements Elicitation | Define & Communicate Requirements Process Define Project’s Vision & Scope – Sponsor Identify User Classes, Process Owners and XXX SMEs If Necessary, Establish Focus Working Groups to develop & Evaluate System Requirements Identify Simple System Use Cases (Scenarios) Hold Facilitated Requirements Workshops – Planning Phase
| Define Requirements Process Define Project Scope (High Level Functionality) ID Common System Users ID Common (Universal) Functionality and System Objectives (Why we need this System?) ID New Requirements (May require Business Process Improvement, New Infrastructure and Skill-set Training)
|
| Requirements Analysis | Conduct workshops to define and prioritize new requirements (A, B, C Analysis: A= Must Have; B= Should Have; C= Desire [Nice to Have])) Create a Common Data Dictionary of Definitions and Processes Workshops to Graphically Model Requirements (e.g. Process Maps)
| Prioritized User Requirements ‘High-Level’ Assessment of Cost and Schedule for System Requirements Exec. Steering Committee Briefing- Approval of Initial Requirements Developed Common Data/Process Dictionary “High-Level” Graphical model of Proposed System
|
| Requirements Specification | Adopt a Requirements Identification Template Develop Requirements Traceability Matrix (Trace requirements to Project Deliverables and Mandates) Record Business Rules (Common [Legacy] and New Rules) Identify Quality Attributes to Requirements (E.g. Reduce Costs, reduce Paper, Cost, transaction Speed, response time, etc.) Develop High-Level Requirements Baseline
| Agreed-Upon Requirements Template Developed Requirements Traceability Matrix (Initial Draft) Agreed-upon Business Rules added to Data Dictionary Draft Baseline Requirements Specification Created – Approved by Exec. Steering Committee/Project Sponsor
|
| Requirements Validation | Formalize Project ‘Change Control’ Process (PMM) Review Draft Requirement Specs for Errors Validate Requirements Meet Customers’ Quality Needs (e.g. Prototype, Customer review, etc.) Develop High Level Test Cases (Reviewed by Users and Customers) Define User Acceptances Criteria
| Signed-Off Baseline Requirements Spec. Develop Family of Proposed Requirement Test Cases Developed User Acceptance Criterion (Approved by exec. Steering Committee/Project Sponsor)
|
Requirements Framework Model:
