BAO111: Core Competencies for the Business Analyst Draft Requirements Management Plan 1.0 INTRODUCTION 1.1 Purpose This document outlines requirements roles and responsibilities, presents a stakeholder analysis, defines the activities, deliverables, and tools and techniques for requirements processes, addresses risk, and defines scope and change management processes. 1.2 Scope This document covers the requirements of the Scenic Hotels Website Enhancement Project managed by Juan Cabrera. The business purpose of this project is to enhance the company s website in order to: Accept online queries about room availability Accept online reservations of rooms 1.3 Definitions and Acronyms Corporate Headquarters Team Senior project stakeholders, including: business owners, project manager/it Manager, Operations and Finance Manager, Marketing Manager CCB Change Control Board. This is the governing body of stakeholders responsible for reviewing and approving requirements and subsequent changes. 2.0 REQUIREMENTS MANAGEMENT 2.1 Stakeholder Roles and Responsibilities (See the solution to the Stakeholder Analysis exercise.) 2.2 Processes and Techniques 2.2.1 Elicitation 2.2.1.1 Inputs Project charter and vision statement Project scope statement Stakeholder analysis Client/server documentation 2.2.1.2 Techniques Elicitation techniques will include, but not be limited to, the following: Requirements workshop facilitated by the business analyst Individual interviews conducted by the business analyst and one technical team member acting as scribe Focus groups Surveys Interviews 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved. 1
Draft Requirements Management Plan Analysis of the interfaces to the existing client-server system and to the credit card agency s credit approval system Review of online reservation systems of other hotels. 2.2.1.3 Elicitation Techniques to Be Used for Selected Stakeholders Stakeholder Juan Cabrera, Project Manager Susan and Robert Johansson, Business Owners Martin Schroeder, Operations and Finance Manager Sarah Benson, Marketing Manager Hotel Managers Prospective and Current Guests Representative Hotel Reservation Staff Members Credit Card Agency Processor Representative Requirements Process Role Techniques to Be Used Source of non-functional requirements for maintainability and security Source of business requirements as well as project time and budget constraints requirements for management reporting requirements for billing, reservations, and financial reports encompassing all hotels requirements for promotions, pricing, and online marketing campaigns and non-functional requirements for the web site including performance, reliability, and usability requirements for billing, reservations, and financial reports for individual hotels requirements and nonfunctional requirements (interoperability, usability) for reservations requirements and nonfunctional requirements (availability, interoperability, usability) for reservations requirements for credit card processing by the credit card processor Individual interview Requirements workshops 2 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.
BAO111: Core Competencies for the Business Analyst Stakeholder Booking Agents Internet Web Hosting Service Staff and Contract IT Specialists Trainers Requirements Process Role Techniques to Be Used requirements and nonfunctional requirements (availability, interoperability, usability) for reservations and nonfunctional requirements related to the web site hosting Not a source for requirements Not a source for requirements 2.2.2 Requirements Analysis and Documentation 2.2.2.1 Techniques: Employed Concurrently with Elicitation Techniques Context diagram Use case model, including text-based specifications (use case descriptions) Activity diagrams System use cases Business rules Storyboards Entity relationship diagrams 2.2.2.2 Outputs Analysis models Business rules Functional requirements Non-functional requirements User interface requirements Transition requirements 2.2.3 Requirements Communication 2.2.3.1 Inputs Elicitation and Analysis and Documentation outputs 2.2.3.2 Techniques Preparation of requirements documents Presentation to corporate headquarters team 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved. 3
Draft Requirements Management Plan 2.3 Activities 2.3.1 Milestones Requirements management plan completed Elicitation completed Requirements documents prepared Requirements presentations completed Requirements approved 2.3.2 Tasks, Estimates, Resources The business owners will personally invite the corporate headquarters team to the first requirements workshop. They will introduce the first workshop and stress their commitment to the processes. The workshops will be scheduled to ensure that all corporate headquarters team members are available to participate. Task Requirements Workshops Individual Interviews Resources Required: Time Estimate Per Resource Business Analyst: 5 days Corporate headquarters team: 5 half-day sessions Focus Group: Current Guests Focus Group: Prospective Guests Focus Group: Hotel Reservation Staff Interface Analysis Surveys Requirements Documents: Preparation 4 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.
BAO111: Core Competencies for the Business Analyst Task Requirements Documents: Reviews Resources Required: Time Estimate Per Resource Requirements Documents: Presentations 2.3.3 Tools Requirements will be documented using ReqDocPro. All technical team members, including the project manager and the business analyst will participate in a 2-day training session on this product, provided by the vendor per the license agreement. 2.3.4 Assumptions The project sponsors have the ultimate authority over the requirements, and their input will be used to resolve any conflicts about requirements among other stakeholders. The IT Department will investigate third-party products that facilitate online queries and reservation processing. 2.3.5 Reports and Measures 2.3.5.1 Traceability A traceability matrix will map collected requirements back to the core business objectives, and will map requirements to subsequent design documents, program code, and test cases. The business analyst is responsible for maintaining the traceability matrix and communicating changes. 2.3.5.2 Attributes A report will document key attributes for each requirement. Attributes to be documented include: Requirement number Description Use case ID Source: individual or group Date identified Planned release Approver of planned release Verification method Test case number(s) Number of changes 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved. 5
Draft Requirements Management Plan 2.3.5.3 Requirements Stability Report A requirements stability report will be produced monthly throughout the project. This report will document the number of added, modified, and deleted requirements during the reporting period and the cumulative totals to date. The business analyst will ensure that the report is distributed to the required stakeholders. 3.0 CHANGE MANAGEMENT 3.1 Purpose of Change Management This plan describes the way that the business sponsor, project manager, subject matter experts, business analysts, and the development team will work together to manage changes. 3.2 Change Request Form [Reference to location of change request template. See Job Aid 14.] 3.3 Change Management Roles and Responsibilities Names / Titles Role in Change Management Process 3.4 Process Steps Initiate change request Assess impact Administers change management process Decide whether to approve a change request Informed of changes Initiator completes the change request form (CRF). Project manager forwards CRF to the appropriate personnel to assess impact. The CCB meets weekly to review open change requests, making disposition decisions. Project manager ensures that: The CRF is stored with its recorded disposition. The CRF is communicated to stakeholders who are affected by the change. All requirements documents that the change affects are reviewed and revised as necessary. 3.5 Emergency Procedures The project manager may convene the CCB at any time, to deal with a change request that cannot wait for the next status meeting. 6 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.
BAO111: Core Competencies for the Business Analyst 3.6 Measures and Reports The following metrics will be tracked: Number of changes per month Number of change requests per software module Number of change requests opened and the number closed within any time period 4.0 RISK MANAGEMENT 4.1 Roles and Responsibilities Risk identification, analysis, and will occur iteratively throughout the project, approximately bi-weekly. Juan Cabrera is responsible for project risk management. Individuals involved in risk management activities include: Name / Title Juan Cabrera, Project Manager Frank Melanson, Business Analyst Susan and Robert Johansson, Business Owners Martin Schroeder, Operations and Finance Manager Sarah Benson, Sales and Marketing Manager Technology Team Staff Members 4.2 Preliminary Risks Risk Management Role Risk management owner Contributes to risk identification, analysis, and Owns requirements-related risks Contribute to risk identification, analysis, and Approve risk response plans and authorizations of reserves Contributes to risk identification, analysis, and Contributes to risk identification, analysis, and Contribute to risk identification, analysis, and Since much of the work will be done by outside vendors, and they will not be hired until after this plan is completed, there may not be enough internal expertise to fully and accurately develop the requirements for this project, resulting in an incomplete set of requirements. The project stakeholders are not familiar with the importance of Elicitation, they may not be willing to participate in requirements activities, leading to a product that does not adequately meet their needs. Actions will be taken by the project manager to ensure that the business owners communicate their full support and commitment to the requirements processes to the corporate headquarters team. Conflicts between members of the team may occur, leading to delays in Elicitation and approval. Facilitators skilled in conflict resolution and negotiation must be available. 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved. 7
Draft Requirements Management Plan 5.0 TRAINING AND RESOURCES The following requirements-related training needs have been identified: Training in Elicitation processes and change management Participants: Business analyst, all technical team members, corporate headquarters team, hotel managers Conducted by: External consultant Duration: 1 day Estimated cost: $2,000 Training on ReqDocPro Participants: Business analyst, all technical team members Conducted by: ReqDocPro vendor Duration: 2 days Estimated cost: $0 included in vendor license agreement Training in conflict management and negotiation skills Participants: Business analyst, project manager Provided by: External consultant Duration: 1 day Cost: $1,000 8 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.