Vision and Scope Document For [project name]

Version [1.0] [approved or draft] Prepared by [author name(s)] CenturyTel [authors title] [date]

Copyright 2008 by CenturyTel. All Rights Reserved.

Vision and Scope for [Project Name]

Table of Contents
Version [1.0] [approved or draft]..................................................................................i Prepared by [author name(s)]........................................................................................i CenturyTel [authors title]..........................................................................................i [date]..............................................................................................................................i 1. Business Requirements....................................................................................................3 1.1. Executive Summary - Background, Business Opportunity, and Customer Needs. 3 1.2. Business Objectives and Success Criteria..............................................................4 1.3. Business Risks .......................................................................................................4 2. Solution Description........................................................................................................5 2.1. Scope: Major Features............................................................................................5 2.2. Assumptions and Dependencies ............................................................................6 3. Limitations and Exclusions..............................................................................................6 3.1. Limitations..............................................................................................................6 3.2. Exclusions (Out of Scope)......................................................................................7 4. Business Context.............................................................................................................8 4.1. Stakeholder Profiles ...............................................................................................8 4.2. Project Priorities ....................................................................................................9 4.3. Vision and Scope Approvals:...............................................................................10 Appendix I. Glossary of Terms.......................................................................................11 Appendix II. Business Rules............................................................................................11

Revision History
Date Reason For Changes Version Name

References
Bibliography of references Document file name author date Document file name author date Document file name author date Document file name author date

- ii -

Vision and Scope for [Project Name]

1. Business Requirements
1.1. Executive Summary - Background, Business Opportunity, and Customer Needs
[BACKGROUND: This section should reflect the rationale and context for the new product/system/service. This section should include a general description of the history or situation that led to the decision to create this request.] [BUSINESS OPPORTUNITY and CUSTOMER NEEDS: This section should cover as many of the following as are relevant to clearly describe the need for this project: the market opportunity that exists, the environment in which the product will be competing, the problem being solved, the process being changed, the environment in which the system will be operating, a comparative evaluation to existing products, explain what problems cannot be resolved without this product, describe benefits and advantages of this product, show relevance to market trends/ technology/ corporate strategy] EXAMPLE: CenturyTel recently partnered with the city of Vail, Colorado to install a wireless mesh network and web portal using Wi-Fi technology. The physical network portion of the technology allows anyone with a Wi-Fi enabled device such as a PC, cell phone, or PDA to connect when in proximity of a mesh access point. The web portal portion of the installation allows connected users to subscribe (via credit card) to wireless access plans, view local content, and log into the portal for internet access and navigation. The portal features shared site branding between CenturyTel and the city of Vail, and includes additional sub-branding with select hotels and businesses within the community. The premier installation was highly successful, driving plans for roll-outs of similar technology into numerous additional markets, both in and out of territory. While initial roll-out plans are simplistic, rich content management and high-end services will soon follow. WiFi offers a unique opportunity for CenturyTel to provide quality, value added services to existing customers and at the same time engage the increasingly mobile marketplace in new, non-traditional ways. The ever increasing availability of Wi-Fi access into both business and home spaces will quickly open doors for numerous expanded capabilities, such as security system monitoring, internet TV, satellite radio, and tele-medicine just to name a few.

-3-

Vision and Scope for [Project Name]

1.2. Business Objectives and Success Criteria

Note: The specific ROI measurements for this project are documented in the Business Case document. See Dennis Long or Emmett McDaniel for additional information. ID BO-1 Objective Description Objectives will generally be to either generate revenue or reduce expenses. Success Criteria Success criteria must be measurable. Release If only one release is planned, delete this column Feature link the objective to the feature

1.3. Business Risks

The Risk Matrix will be a living document throughout this project which will be managed by the IS Project Manager. Risks identified to date:
Probability (Percent chance of occurrence) Impact Exposure (Probability * Impact)

Risk

RI-1

Risk Description Note that this table is a sub-set of the information in the Risk Matrix document. The full document will be passed to the PM after SRS approval. The PM will ensure that mitigation/contingency plans are in place.

1 (low) to 10 (high)

What would be impacted?

10%

0.4

-4-

Vision and Scope for [Project Name]

2. Solution Description
2.1. Scope: Major Features
GUIDELINES FOR WRITING FEATURES (Business Specific) 1. Define the business features to be used in the Vision and Scope, SRS and Change Management deliverables a. When describing the feature it does not need to be detailed. Provide a few sentences that give a general explanation of the feature. This should be understandable by both the Business area requesting the functionality and the Development team. Please see the example below. b. Use the acronym CRUD to help in the wording of the feature. CRUD refers to all major functionality within the SDLC and helps to simplify the description of this functionality through accepted action words. CRUD = Create, Review, Update and Delete. Other examples would be view, display, modify, edit, remove, hide or show. http://en.wikipedia.org/wiki/Create,_read,_update_and_delete 2. Enter the features into the appropriate document as part of the associated lifecycle phase. (Vision and Scope during the Feasibility and Planning phases, SRS during the Analysis phase and Change Control during the Design, Construction, Testing, Implementation and Post-Implementation phases) a. All features should be numbered based on the agreed upon standard (FE-1, FE-2, etc). b. A description should accompany each feature and follow the rules outlined in the first guideline listed above c. All features should list the owner of the feature. This person is the Business/IT person requesting this feature d. When a project is spanning multiple releases, please list the release number the feature is to be delivered in. e. The features are initially entered into the Vision and Scope document. Once the Vision and Scope is approved these Features will be moved over to the SRS document. Within the SRS document, the features are elaborated on in the form of Functional Requirements and Use Cases. The Feature information is also entered into the Traceability Matrix during Change Control and paired up with the information from the SRS.

-5-

Vision and Scope for [Project Name]

EXAMPLES: The example below uses the CRUD rules in the wording of the Features. For Feature 2 (FE-2) the business wants a way to manage meal service subscriptions. In this example, by using the CRUD rule the feature is written as follows Create, view, modify and delete meal service subscriptions.
Feature Number FE-1 Feature Description Order meals from local restaurants to be delivered Feature Owner Rodney Barton Jake Ford Cam Nolan Mark Wallace Marlene Williams Keith Parker Stephen Heyward Rodney Barton Release

FE-2

Create, view, modify, and delete meal service subscriptions

FE-3

Register for meal payment options

2.2. Assumptions and Dependencies

Number (AS=Assumption DE=Dependency ) AS-1 DE-1 Description

3. Limitations and Exclusions

3.1. Limitations
Limitation Number LI-1 Description

-6-

Vision and Scope for [Project Name]

3.2. Exclusions (Out of Scope)

Exclusion Number EX-1 Description

-7-

Vision and Scope for [Project Name]

4. Business Context
4.1. Stakeholder Profiles
Business Partner Participant Name Stake

-8-

Vision and Scope for [Project Name]

4.2. Project Priorities

Dimension Schedule Features Quality Staff Cost Driver Constraint Degree of Freedom

-9-

Vision and Scope for [Project Name]

4.3. Vision and Scope Approvals:

By signing this document, we agree it represents our best understanding of the scope for this project. We understand this document is not the final detailed requirements specification and that detailed requirements gathering may identify additional needs or issues. We agree to make any further changes to this baseline through the projects defined change process. We realize further changes must be approved, and might require a renegotiation of cost, resource, and scheduling commitments.

Project Sponsor (Name)

Date

Project Sponsor (Name)

Date

VP - Engineering

Date

VP - Marketing

Date

VP Customer Service

Date

VP Information Systems

Date

VP Regions

Date

VP - Operations

Date

- 10 -

Vision and Scope for [Project Name]

Appendix I. Glossary of Terms

Term Definition

Appendix II. Business Rules

This section is optional. If business rules are identified during elicitation for the Vision and Scope document, they should be recorded here rather than in the Assumptions section. If a business rule would affect development of a feature, it should also be referenced in the Major Features section. Upon sign-off of the Vision and Scope, any new business rules should be copied to the Business Rules Repository. A format for this section will be added at a later date.

- 11 -