introduction to babok- requirements mgmt

Introduction to BABOKTM : 

Introduction to BABOKTM IT BUSINESS ANALYSIS LECTURE 6 REQUIREMENTS MANAGEMENT & COMMUNICATION

Requirements Management & Communication : 

Requirements Management & Communication The Requirements Management and Communication Knowledge Area describes the activities and considerations for managing and expressing requirements to a broad and diverse audience. These tasks are performed to ensure that all stakeholders have a shared understanding of the nature of a solution and to ensure that those stakeholders with approval authority are in agreement as to the requirements that the solution shall meet.

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements Purpose Obtain and maintain consensus among key stakeholders regarding the overall solution scope and the requirements that will be implemented. Requirements may be baselined following approval. Any changes to requirements after baselining, if changes are permitted, involves use of a change control process and subsequent approval. As requirements are refined or changed as the result of new information, changes will be tracked as well.

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements Key Points All stakeholder and solution requirements must be assessed to ensure that they fall within the solution scope. As requirements are developed and reviewed, conflicts often arise. Facilitate communication between the stakeholders who are in conflict over the requirement in order to resolve the issue. Conflicts may be resolved through formal meetings among affected stakeholders, through research, resolution by a third party, or other methods as appropriate. Conflicts that affect the requirements must be resolved before formal approval is given to those requirements. When presenting requirements for review and approval, there needs to be enough formality to support the methodology and ensure that the stakeholders will review, understand, and approve them. Ensure that the stakeholder(s) responsible for approving requirements understands and accepts the requirements.

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements INPUTS Requirements Management Plan: Defines the process to be followed in managing the solution scope and requirements. Solution Scope: Requirements must support the solution scope in order to be approved, unless the solution scope is modified accordingly. Stakeholder List, Roles, and Responsibilities: This defines which stakeholders are involved in reviewing and approving requirements. Stakeholder, Solution, or Transition Requirements [Communicated or Traced]: Requirements may be managed at any point in their lifecycle (stated, specified and modeled, verified, validated, etc.), although stakeholder approval is normally restricted to requirements that have been verified and validated. Requirements must be communicated to be managed, as stakeholders cannot consent to requirements if they are not aware of them.

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements TECHNIQUES Problem Tracking Baselining Signoff

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements Baselining Once requirements are approved, they may be baselined, meaning that all future changes are recorded and tracked, and the current state may be compared to the baselined state. Subsequent changes to the requirement must follow the change control process. As changes are approved, the requirements management plan may require that the baselined version of the requirement be maintained in addition to the changed requirement. Additional information is often maintained such as description of the change, person who made the change, and the reason for the change.

Requirements Management & Communication : 

Requirements Management & Communication Manage Solution Scope & Requirements Signoff Requirements signoff formalizes agreement by stakeholders that the content and presentation of documented requirements is accurate and complete. Obtaining requirements signoff typically involves a face-to-face final review of requirements documentation with each stakeholder with authority to approve requirements. At the end of each review, the stakeholder is asked to formally approve the reviewed requirements document. This approval may be verbal or be recorded either physically or electronically.

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability Purpose Create and maintain relationships between business objectives, requirements, other team deliverables, and solution components to support business analysis or other activities.

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability Key Points “Tracing” a requirement refers to the ability to look at a requirement and the others to which it is related. Tracing links business requirements to stakeholder and solution requirements, to other artifacts produced by the team, and to solution components. Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability (derivation), its forward traceability (allocation), and its relationship to other requirements. There are three main reasons for creating these relationships: ▶Impact Analysis ▶Requirements Coverage ▶Requirements Allocation

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability INPUTS Requirements: All requirements may potentially be traced to other requirements, and all stakeholder and solution requirements must be traceable to a business requirement. Requirements Management Plan: Defines how and whether traceability is being performed, the tools that will be used to support traceability and the processes that will be used to manage it.

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability TECHNIQUES Coverage Matrix

Requirements Management & Communication : 

Requirements Management & Communication Manage Requirements Traceability Coverage Matrix A coverage matrix is a table or spreadsheet used to manage tracing. It is typically used when there are relatively few requirements or when tracing is limited to high-level requirements (e.g. features or models).

Requisite Pro : 

Requisite Pro

Requirements Management & Communication : 

Requirements Management & Communication Maintain Requirements for Re-use

Requirements Management & Communication : 

Requirements Management & Communication Maintain Requirements for Re-use Purpose To manage knowledge of requirements following their implementation and Identify requirements that are candidates for long-term usage by the organization. These may include requirements that an organization must meet on an ongoing basis, as well as requirements that are implemented as part of a solution.

Requirements Management & Communication : 

Requirements Management & Communication Maintain Requirements for Re-use Key Points To re-use requirements they must be clearly named and defined and easily available to other analysts. These requirements may be stored in a repository, and a person should be identified to manage the repository. Ongoing requirements are those requirements that an organizational unit is required to be able to meet on a continuous basis. These may include contractual obligations, quality standards, service level agreements, business rules, business processes, or requirements describing the work products the group produces. Even though a requirement has been satisfied, it is still a requirement as long as the business stakeholders need it. Maintaining these requirements helps with product enhancements and future system changes. Existing requirements may also be re-used on related business projects.

Requirements Management & Communication : 

Requirements Management & Communication Maintain Requirements for Re-use INPUTS Organizational Process Assets: These set standards regarding how and when requirements should be maintained for re-use. Requirements: Requirements may be maintained for re-use as long as they describe information of use to the organization beyond the lifetime of an initiative. Requirements will usually be candidates for maintenance only if the describe the actual current state of an organization.

Requirements Management & Communication : 

Requirements Management & Communication Maintain Requirements for Re-use TECHNIQUES None

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package Screen clipping taken: 12/27/2009, 7:50 AM

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package Purpose To select and structure a set of requirements in an appropriate fashion to ensure that the requirements are effectively communicated to, understood by, and usable by a stakeholder group or groups. Screen clipping taken: 12/27/2009, 7:50 AM

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package Key Points Possible forms for requirements packages may include: ▶Formal Documentation ▶Presentation ▶Models A work product is a document or collection of notes or diagrams used by the business analyst during the requirements development process. The work product may or may not become a deliverable (Meeting agendas and minutes, Interview questions and notes etc.) A deliverable is a specific output of the business analysis process that the business analyst has agreed to produce. A requirement deliverable is used as a basis for solution design and implementation.

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package INPUTS Business Analysis Communication Plan: This will typically describe the stakeholder groups, their communication needs, and define whether a single requirements package or multiple requirements packages are required. The business analysis communication plan will also define the level of formality that is appropriate for the requirements. Organizational Process Assets: May include templates that can be used to package requirements. Requirements: The business analyst must understand which requirements will be included in the package. Requirements may be packaged at any point in their lifecycle. Requirements Structure: A package should contain a consistent, cohesive, and coherent set of requirements.

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package TECHNIQUES Requirements Documentation Requirements for Vendor Selection

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package Requirements Documentation Requirements are frequently captured in a formal document. Many templates for requirements document exist and are in common use. ▶ Business Requirements Document ▶Product Roadmap ▶Software/System Requirements Specification ▶Supplementary Requirements Specification ▶Vision Document

Requirements Management & Communication : 

Requirements Management & Communication Prepare Requirements Package Requirements for Vendor Selection If the solution team thinks that a potential solution is available from an outside party, the business analyst may capture the requirements in the form of a Request for Information (RFI), Request for Quote (RFQ), or Request for Proposal (RFP). While these terms are sometimes used interchangeably, they are intended to reflect differing levels of formality in the vendor selection process. The organization’s purchasing agent, legal department or procurement organization is usually the owner of this process. ▶An RFI is generally used when the issuing organization is open to a number of alternative solutions and is seeking information to evaluate possible options. ▶An RFQ or RFP is used when the issuing organization understands the nature of the solution options available to it and is seeking vendors who can implement an option. An RFQ generally follows a less formal review and selection process than an RFP.

Requisite Pro : 

Requisite Pro

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements Screen clipping taken: 12/27/2009, 7:50 AM

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements Purpose Communicating requirements is essential for bringing stakeholders to a common understanding of requirements. Screen clipping taken: 12/27/2009, 7:50 AM

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements Key Points Requirements communication is performed iteratively and in conjunction with most of the tasks in the other knowledge areas. In many cases, requirements communication may lead to elicitation of additional requirements. ▶Enterprise Analysis Tasks: Business case and solution scoping information is communicated. ▶Elicitation Tasks: Each elicitation technique requires specific communication skills. Communication of requirements may be useful during elicitation activities, as it may help stakeholders to identify other related requirements. ▶Requirements Analysis Tasks: Requirements are refined, modified, clarified and finalized through effective communication. ▶Solution Assessment and Validation Tasks: Assessments of the solution, allocation of requirements to solution components, organizational readiness, and transition requirements all must be communicated.

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements INPUTS Business Analysis Communication Plan: Defines what information is to be communicated, which stakeholders need to receive it, when communication should occur, and the form it should occur in. Requirements: Any requirement may be communicated. Requirements Package: Requirements may be communicated without being in a requirements package, but if a package has been assembled, it must be distributed, reviewed, and the contents must be communicated to stakeholders.

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements TECHNIQUES Requirements Documentation Requirements for Vendor Selection

Requirements Management & Communication : 

Requirements Management & Communication Communicate Requirements Requirements Documentation Requirements are frequently captured in a formal document. Many templates for requirements document exist and are in common use. ▶ Business Requirements Document ▶Product Roadmap ▶Software/System Requirements Specification ▶Supplementary Requirements Specification ▶Vision Document

END OF SECTION : 

END OF SECTION

Q&A : 

Q&A