Define Solution Scope - Business Analyst

Purpose

To define which new capabilities a project or iteration will deliver.

Description

The purpose of this task is to conceptualize the recommended solution in enough detail to enable stakeholders to understand which new business capabilities an initiative will deliver. The solution scope will change throughout a project, based on changes in the business environment or as the project scope is changed to meet budget, time, quality, or other constraints. The solution scope includes:

The scope of analysis (the organizational unit or process for which requirements are being developed) which provides the context in which the solution is implemented.

The capabilities supported by solution components, such as business processes, organizational units, and software applications.

The capabilities to be supported by individual releases or iterations.

The enabling capabilities that are required in order for the organization to develop the capabilities required to meet the business need.

Input

Assumptions and Constraints: Relevant assumptions and constraints may include assumptions about how stakeholders will respond to a new product or service or about the availability of technology. Constraints may include limitations on what may be included in the solution scope. Include any schedule or funding limitations and significant standards, policies, regulations to be followed and supporting data required.

Business Need: The goals, objectives, and desired outcomes of the organization.

Required Capabilities: Describes the new capabilities required to meet the business need, which serve as the basis for the solution scope.

Solution Approach: The general approach taken to delivery of the new capabilities required by the business will be used when assessing options for the implementation of solution components.

Elements

Solution Scope Example

1. Solution Scope Definition

The solution is described in terms of the major features and functions that are to be included, and the interactions that the solution will have with people and systems outside of its scope. State in-scope and out-of-scope components of the solution. Describe the business units that will be involved, business processes to be improved or redesigned, process owners, and IT systems and other technology that will likely be affected.

2. Implementation Approach

The implementation approach describes how the chosen solution approach will deliver the solution scope. For example, if the solution approach involves partitioning the proposed project into releases that will deliver useful subsets of functionality to the business, the implementation approach will describe the functionality in each release and the timeframe that it is expected to be delivered in. If the solution approach involves outsourcing key processes, the implementation approach will define which processes are candidates for outsourcing, or the process that will be used to identify those candidates. The implementation approach may break delivery down into specific releases or provide a roadmap that indicates the timeframe in which a capability can be expected.

3. Dependencies

Define major business and technical dependencies that will impose constraints to the effort to deploy the solution, including dependencies that may exist between solution components.

Techniques

1. General Techniques

Functional Decomposition : To understand the scope of work and to break the solution scope into smaller work products or deliverables.

Interface Analysis : Depict the scope of work required to integrate the new solution into the business and technical environments.

Scope Modeling : Identify appropriate boundaries for the solution scope.

User Stories : Describe stakeholders and the goals the system supports and as such can also be used to define the solution scope.

2. Problem or Vision Statement

A problem or vision statement states the business need, identifies key stakeholders, and briefly describes the positive impact that meeting the business need will have on those stakeholders.

Stakeholders

Domain SME:Will participate in identifying the affected organizational units, modeling the scope of possible solutions, and determining the relative priorities of the required capabilities.

Implementation SME: Will participate in the allocation of capabilities to solution components and in determining the time and effort required to deliver new capabilities.

Project Manager: May assist with the development of the overall solution scope, which will be used as an input into the Project Charter. The project manager is responsible for the definition of the project scope, which is the work required to deliver the solution scope or a portion of it. The project manager will play a major role in allocating capabilities to components and will be primarily responsible for determining the time and effort required to deliver a capability.

Sponsor: Will participate in setting priorities and approving the solution scope.

Output

Solution Scope:Defines what must be delivered in order to meet the business need, and the effect of the proposed change initiative on the business and technology operations and infrastructure.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Business Analyst Topics