Business Process Overview

Document Revisions

Approvals

Introduction

Project Summary

Objectives

[These should describe the overall goal in developing the product, high level descriptions of what the product will do, how they are aligned to business objectives, and the requirements for interaction with other systems.]

· Deliver a Widget Interactive Naming System (WINS) that synchronizes naming and linking of all widgets in all systems across the enterprise.

· Avoid duplication of widget names and reduce time to production for existing projects.

· Support text searching on widget names or business descriptions.

· Sync widget names and changes to Windows and Linux platform administration tools.

· Tracks changes to widgets including new widgets, modified widgets, and widgets to be archived.

Background

[Provide a brief history of how the project came to be proposed and initiated, including the business issues/problems identified, and expected benefit of implementing the project/developing the product.]

Timely and accurate synchronization of widget names will reduce development levels of efforts across the enterprise by eliminating duplicate names of widgets in development and deployed. Acme uncovered seriously high levels of errors across testing environments, production error messages, and increased rework due to lack of knowledge about widgets already in production.

Business Drivers

[List the business drivers that make development of this product important. These can be financial, operational, market or environmental.]

· Customers are looking for faster updates to information on the [product] website, and may consider competitors if needs are not met.

· Development group requires a scalable solution to track the widgets being deployed into all environments to better manage resources.

Project Scope

[Describe what work is in scope for the project, and specifically what work is out of scope… beyond the current budget, resources and timeline as approved by the project stakeholders. This is designed to prevent “scope creep” of additional features and functions not originally anticipated.]

In Scope Functionality

· Create name records for widgets by category

o Supply Chain

o Production Lines

o Internal web apps

o External web apps

· Ability to create/delete widget names restricted by role

· Search by name, team, date, last modified

· Synchronize widgets across product/operations lines

· Provide audit trail

· Reporting on new, modified, and archived widgets by time period and team

Out of Scope Functionality

· Create widgets for subsidiary company product lines

· Search by approver, or rationale

· Archiving of widget objects

System Perspective

[Provide a complete description of the factors that could prevent successful implementation or accelerate the projects, particularly factors related to legal and regulatory compliance, existing technical or operational limitations in the environment, and budget/resource constraints.]

Assumptions

· Inventory of existing widgets completed by Q1.

· Testing data comprises scrubbed production data as of December 31.

Constraints

· Impending changes to privacy regulations may impact data dictionary design.

· Timeline for enterprise platform updates will impact execution of testing plan.

Risks

· Previously approved Q2/Q3 development projects may limit availability of development and QA resources, necessitating outsourcing or additional budget requisitions to meet the anticipated timeline.

· .

Issues

·

Business Process Overview

[Describe how the current process(es) work, including the interactions between systems and various business units. Include visual process flow diagrams to further illustrate the processes the new product will replace or enhance.

Use case documentation and accompanying activity or process flow diagrams can be used to create the description(s) of the proposed or “To-Be” processes.]

Date: 2015-12-11; view: 890