{"id":2715,"date":"2016-11-30T09:46:33","date_gmt":"2016-11-30T14:46:33","guid":{"rendered":"http:\/\/flevy.com\/blog\/?p=2715"},"modified":"2016-11-28T09:56:29","modified_gmt":"2016-11-28T14:56:29","slug":"requirements-management-plan-why-do-we-need-it-anyway","status":"publish","type":"post","link":"https:\/\/flevy.com\/blog\/requirements-management-plan-why-do-we-need-it-anyway\/","title":{"rendered":"Requirements Management Plan: Why Do We Need It Anyway?"},"content":{"rendered":"

\"dilbert\"Requirements gathering is a small phase of the project. \u00a0Why do we need a plan for it?<\/em><\/p>\n

We have a project management plan for the project. Why do we need one more plan?<\/em><\/p>\n

We follow agile life cycle where in the project cycle is shortened. Then, why is requirements management plan needed?<\/em><\/p>\n

Given below is an indicative list of items\/aspects that are managed in Requirements management plan.<\/p>\n

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

                                                A requirements management plan is needed as much as a project plan is needed for a project and smooth functioning of the project.<\/p>\n

                                                Please see a video demonstration of the template\u00a0here<\/a>.<\/p>\n

                                                You can acquire an exhaustive Requirements Management Plan Template from the author on Flevy\u00a0here<\/a>.<\/div>\n","protected":false},"excerpt":{"rendered":"

                                                Requirements gathering is a small phase of the project. \u00a0Why 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… Requirements Management Plan: Why Do We Need It Anyway?<\/span><\/a><\/p>\n","protected":false},"author":95,"featured_media":2716,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"categories":[84],"tags":[1160,1159],"class_list":["post-2715","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-information-technology","tag-business-requirements","tag-requirements-management"],"_links":{"self":[{"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/posts\/2715","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/users\/95"}],"replies":[{"embeddable":true,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/comments?post=2715"}],"version-history":[{"count":1,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/posts\/2715\/revisions"}],"predecessor-version":[{"id":2717,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/posts\/2715\/revisions\/2717"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/media\/2716"}],"wp:attachment":[{"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/media?parent=2715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/categories?post=2715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/flevy.com\/blog\/wp-json\/wp\/v2\/tags?post=2715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}