flevyblog

Flevy Blog is an online business magazine covering Business Strategies, Business Theories, & Business Stories.
MANAGEMENT & LEADERSHIP STRATEGY, MARKETING, SALES OPERATIONS & SUPPLY CHAIN ORGANIZATION & CHANGE IT/MIS Other

Requirements Management Plan: Why Do We Need It Anyway?

dilbertRequirements gathering is a small phase of the project.  Why do we need a plan for it?

We have a project management plan for the project. Why do we need one more plan?

We follow agile life cycle where in the project cycle is shortened. Then, why is requirements management plan needed?

Given below is an indicative list of items/aspects that are managed in Requirements management plan.

  1. Overview of the project – Describing the overview and objectives of the project
  1. Terms and Glossary – Terms, abbreviations and definitions specific to the project used in the document can be described here
  1. Infrastructure – Hardware, software, tools needed for the project
  1. Communication plan/mechanism – what will be the communication mechanism, frequency and audience /stakeholders
  1. Structure – Which part of the requirements will be contained in which document e.g. SRS will contain use case description, BRD will contain the business requirements
  1. Traceability Guidelines – How the requirements will be traced e.g. project objectives à stakeholder request àBRDàSRS
  1. Prioritization Guideline – How the requirements will be prioritized e.g. statutory/legal requirement, Critical business objective then it will be high priority
  1. Techniques – what techniques will be used in which situation, from the usual techniques like SWOT, Matrix model, surveys and techniques etc
  1. Change Management – How will requirements change be handled, the requirements change management process can be documented here
  1. Change control board – the constitution and the authority of the board can be described here e.g. functional requirements  <20 Hrs can be authored by Requirements analyst, reviewer can be Lead BA and Domain SME, approver can be PM
  1. CM Plan – who will be owner for which document like Flow diagrams, prototypes
  1. Metrics – Typical metrics can be % of requirements delivered as per requirements management plan, Average effort spent per detailed requirements document, Number of defects identified per use case
  1. Attributes – Attributes of the requirement can be detailed here will need to contain the attribute name, description, type, Values
  1. System context – Various system context such as stakeholders, interfacing systems etc
  1. Sources and techniques – This will detail out the type of requirements, Source of the requirement, techniques for Elicitation and Modelling
  1. Stakeholder Matrix – This will have details of the various stakeholders like name, type, role, Criticality, expectations, contact details etc
  1. Resource structure of the BA/RE team with name, role, contact details etc
  1. Skill gap analysis and Competencies needed
  1. Effort estimate for the Requirements engineering task
  1. RACI Matrix for the various types of requirements
  1. Risks and assumptions – Risks and Assumptions for the requirements of the project with impact, mitigation plan
  1. Activity plan – Activity/ task plan with schedule, responsibility, effort needed, deliverable details
  1. RMP checklist – To ensure all the planned activities and tasks are completed

A requirements management plan is needed as much as a project plan is needed for a project and smooth functioning of the project.

Please see a video demonstration of the template here.

About Ananya Pani

Ananya Panyi is a Director and Co-founder of Adaptive Processes, a technology consulting firm specializing in Business Analysis training services and materials. Adaptive Processes is also an author on Flevy, offering a wide selection of BA, IT, and business training guides (see their materials here). You can reach Ananya directly by email here: [email protected].

,




Complimentary Business Training Guides


Many companies develop robust strategies, but struggle with operationalizing their strategies into implementable steps. This presentation from flevy introduces 12 powerful business frameworks spanning both Strategy Development and Strategy Execution. [Learn more]   What does it take to achieve Operational Excellence? Read this guide and learn to build an integrated Business Execution System from Six Sigma Master Black Belt Frank Adler, co-founder of Operational Excellence Consulting. [Learn more]
The Fiaccabrino Selection Process (FSP) is a proven methodology for increasing sales and reducing turnover, developed by "Mr. Roche," Charles Fiaccabrino. Mr. Fiaccabrino is a Sales Executive with over 50 years of experience. [Learn more]   Learn this time-tested approach to Change Management authored by Ron Leeman, recipient of the Change Leader award by the World HRD Congress in 2012. Ron Leeman has been Change, Process and Project professional since 1974. [Learn more]
Recent Articles by Corporate Function

  

  

  

  

  


The Flevy Business Blog (http://flevy.com/blog) is a leading source of information on business strategies, business theories, and business stories. Most articles have been contributed for management consultants and industry executives with over 20 years of experience. If you would like to contribute an article, please email our editor David Tang at [email protected].

Flevy (http://flevy.com) is the marketplace for premium business documents, such as management frameworks, presentation templates, and financial models. Our documents are of the same caliber produced by top tier consulting firms, like McKinsey, Bain, Accenture, BCG, and Deloitte. Learn more about Flevy here.


Connect with Flevy:

   
  


About Flevy.com   /   Terms   /   Privacy Policy
© 2015. Flevy LLC. All Rights Reserved.