eliverables

About This Document

·  This is an Active Deliverable (AD) document, which is attached to the Active Deliverable Development Kit template (ADDK.DOT).

·  The ADDK contains macros that perform special functions for the AD. These commands can be accessed either through the AD Tools menu or the AD Toolbar. If the commands or toolbar are not available, verify:

·  that the document is associated with ADDK.DOT by selecting Templates and Add-Ins from the Tools menu in Word 97 or Word 2000. In the Document Template text box, ADDK.DOT should be displayed.

·  that ADDK.DOT is in the Templates folder or in the same folder as this document.

·  Instruction Text throughout the document provides suggestions about how to complete various sections.

Using This Document

·  Where applicable, replace Instruction Text (hidden, red text) with project specific information.

·  Follow the instructions and suggestions included in Instruction Text.

·  It is recommended that the user keep the Instruction Text displayed until the document is completed.

How to convert Instruction Text to normal text

1. Select Instruction Text that needs to be changed

2. Press the Control button then the spacebar

How to update fields

·  Select the field, and press F9.

·  Alternatively, press Control + A to select the entire document and press F9.

·  To also lock a field, select Update and Lock Field from the AD Tools menu.

How to complete the title page

The title page contains important information about the Active Deliverable, such as the Project Name.

Enter the following information for the title page:

Organization Name

Project Name

Document Name

Author

Version

Date

Sponsor

Customer Representative

Technical Representative

How to reuse information from the title page

The information that the user supplies on the title page can be reused in other parts of the document.

Each of the items on the title page has an associated style, which is based on the item name and preceded by an asterisk (*).

1. Click where relevant title page information should be inserted in the document.

2. From the AD Tools menu, select Add Document Information.

3. In the dialog, choose a document information item.

4. Press OK.

This method can also be employed for other styles by doing the following:

1. Click where the information is going to be inserted in the document.

2. From the Insert menu, select Field.

3. Click the "Links and References" category, and then click the "StyleRef" field name.

4. To add a style click Options. Title Page styles appear at the top of the style list.

NOTE: If items are changed on the title page, the corresponding fields within the document will need to be updated as well.

How to add content to this document.

Content can be added to the document using either a tabular format (see each section), a textual format (see Example Boxes), a graphical format or any combination of these.

Enter Organization Name

Enter Project Name

Desired State Document

Prepared by:
Version:
Date:
Project Board:
Sponsor:
Customer Representative:
Technical Representative:

Approval Signatures

Name: / Name:
Title: / Title:
Name: / Name:
Title: / Title:
Name: / Name:
Title: / Title:
Name: / Name:
Title: / Title:
Name: / Name:
Title: / Title:

[INSTRUCTIONS - To update these fields, click on the item and press F9.]

Enter Project Name

Desired State Document

Enter Organization Name

Document History

Reviewed By

Organization / Person

Copied To

Organization / Person

Revision Record

Number / Date and Sections / Notes

ad_ds.doc x 7/5/00

Acronyms

Acronym / Description

ad_ds.doc x 7/5/00

References

[INSTRUCTIONS - Enter document title and its file name for each referenced document]

Document Title / File Name

ad_ds.doc x 7/5/00

Table of Contents

[INSTRUCTIONS - From the AD Tools menu, select Update Table of Contents or double-click the button]

tents

1. INTRODUCTION

1.1 Document Purpose

1.2 Project Deliverable Roles

1.3 Related Documents

2. IMPROVEMENT OPPORTUNITIES LIST

3. TECHNOLOGY EVALUATION

4. BENCHMARK DATA

4.1 Benchmarking Literature

4.2 Best Practices

5. BUSINESS PROCESS MODEL (OPTIMIZED)

5.1 [Optimized Process #1: The <OptimizedProcessName1> Process

5.1.1 [Optimized Process n1] Process Owner

5.1.2 [Optimized Process n1] Process Goals

5.1.3 [Optimized Process n1] Process Metrics

5.1.4 [Optimized Process n1] Activity List

5.1.5 [Optimized Process n1] Work Products

5.1.6 [Optimized Process n1] Process Diagram

5.1.7 [Optimized Process n1] Activity Sequence

5.2 [Optimized Process n2]

6. LEVERS OF CHANGE ANALYSIS

7. SOURCES OF RESISTANCE LIST

8. FUTURE TECHNOLOGY INNOVATIONS

9. APPENDICES

9.1 Related Work Papers

9.2 REVISION HISTORY

10. GLOSSARY

ad_ds.doc x 7/5/00

1.  Introduction

If a project name has not already been supplied, go to the first page and enter a project name in the appropriate place.

1.1  Document Purpose

The Desired State Document captures the redesign of the business processes that will better achieve the process goals (e.g. faster cycle time, reduced defects, and lower unit cost).

1.2  Project Deliverable Roles

The people listed below will receive a copy of the Desired State Document deliverable. See the Project Plan for a description of the roles of the Creator, Reviewers, and Acceptor/Approvers.

This list is current as of July 5, 2000. Select the date and press F9 to update. To lock this field, press the Update and Lock Field button on the AD Tools toolbar.

Creator
Organization / Name
[insert organization name here] / [insert name of person completing document here]
Reviewers
Organization / Name
[insert here the organization names of team leads and chief designers for interfacing projects] / [insert here the names of the individuals]
[insert name of group that needs to review this deliverable] / [insert name(s)]
Acceptor/Approvers
Organization / Name
[insert name of group that needs to accept/approve this deliverable (for example, the User Acceptor’s group)] / [insert here the names of the individuals]
[insert group name] / [insert name(s)]

1.3  Related Documents

[INSTRUCTIONS - List documents referenced in this document, noting author, location, access means, and version number.]

(Levers of Change material is adapted from "Better Change - Best Practices for Transforming Your Organization" by the Price Waterhouse Change Integration Team. Chicago: Irwin Professional Publishing, 1995.)

2.  Improvement oPPORTUNITIES lIST

Revisit the problems that were identified with respect to the current state and the updated requirements. Where possible, translate those problems and issues into potential opportunities for improvement.

The following improvements and/or innovations have been identified that can be applied to the existing business process to better meet the needs of the business.

ID number / Priority / Description of Opportunity / Next Step, if possible

3.  technology Evaluation

Experiment with the technology/packages. Consider the existing technical and business requirements. Identify hidden requirements and/or possible constraints that may influence the new business process and the future solution.

Technology/Package / Related Technical Requirement / Issue Under Investigation / Result

4.  Benchmark Data

4.1  Benchmarking Literature

Summarize findings from the review of benchmarking literature that will be incorporated into the Desired State. State the rationale for inclusion. If there is a lot of material related to the benchmarking activity (data, background, related papers and reports) include the additional material/data in a Benchmarking section in the Domain Knowledge Notebook.

4.2  Best Practices

Summarize results from any best practice information that will be incorporated into the Desired State. List the best practice information and the rationale for inclusion. If there is a lot of material related to best practice (related papers and reports) include the additional material/data in a Best Practices section in the Domain Knowledge Notebook.

5.  Business Process Model (Optimized)

List each optimized business process and provide information as indicated in each section below.

5.1  [Optimized Process #1: The <OptimizedProcessName1> Process

Overwrite <ProcessName1> with the name of the first optimized process to be described]

5.1.1  [Optimized Process n1] Process Owner

State who within the organization is responsible for the effectiveness, care, and maintenance of the process.

5.1.2  [Optimized Process n1] Process Goals

State what the goals of the process are within the organization, in terms of measurable targets, e.g., cycle time, defect rate, cost. Include any strategic observations about related policies, procedures, and standards.

5.1.3  [Optimized Process n1] Process Metrics

State the process metrics that are/will be used to measure the effectiveness of the optimized process.

5.1.4  [Optimized Process n1] Activity List

List each activity, and the organizational role responsible for performing that activity. Activities are performed by agents. An agent can be a role, an organizational unit or function, or an automated process.

Activity / Agent/Responsible Roles
Order Generated / Customer
Order Completed / Order Clerk

5.1.5  [Optimized Process n1] Work Products

List the work products that are required by a specific activity (inputs). Inputs are resources that are transformed by the activity to accomplish the activity.

List the work products that are generated by a specific activity (outputs). Outputs are work products produced by an activity.

Inputs / Outputs

5.1.6  [Optimized Process n1] Process Diagram

Provide a diagram of the process.

Sample Process Diagram:

5.1.7  [Optimized Process n1] Activity Sequence

List the activities in the order that they are performed. When activities are performed concurrently, document this in the Sequence Issues column. Record any critical dependencies that exist between activities.

Activity Name / Sequence Issues / Critical Dependencies

5.2  [Optimized Process n2]

6.  Levers of Change Analysis

Define the "dimensions/levers of change" that are needed to support the new technology rollout effort and the desired state. Remember that existing levers are supporting the current state. These will need to change to support the new technology and optimized business process.

Document any constraints on the project team that impact their ability to implement change. Identify the stakeholders, key individuals and groups, whose buy-in and/or support is essential for the effort. Include recommendations.

Lever of Change / Issue / Change
Recommendation / Feasibility:
Yes/No / Risk if lever is
not enabled
Markets and Customers
Products and Services
Business Processes
People & Reward Systems / Performance measures (related to individuals) are not linked with the reward system. Before implementing the internet environment individual performance measures and the reward system for the new way of working associated with the internet development technology need to be modified. / Define jobs and assignments in terms of results to be accomplished, not duties and functions to be performed. Use strategic and financial objectives as the basis for incentive compensation. Modify the reward system to reflect incentives based on the new performance targets. / Yes / Employee’s sustained, energetic commitment will diminish. Focus on objectives laid out in the strategic plan as related to the internet environment will not be retained.
Organization Structure & Facilities
Technologies

7.  Sources OF RESISTANCE List

Identify potential sources of resistance. Document observations, anticipated reactions, and mitigation ideas.

Impact / Sources of Resistance / Anticipated Reaction/Issues / Mitigation Ideas

8.  Future Technology Innovations

Record observations about future directions and opportunities for innovation in the organization. Include recommendations, where appropriate.

9.  Appendices

9.1  Related Work Papers

These work papers were used as inputs to this deliverable:

Work Paper/Products / Location
[Insert work paper/product name here] / [Describe location here; include full network path to on-line documents]

9.2  REVISION HISTORY

The following table shows the history of revisions that have been made to this document.

Date / Description / Person Responsible
[Date] / [Description of change] / [Name of person who made the change]

10.  Glossary

A standard glossary of terms, including the names of all Best Practices Process Library methodologies and stages, is included in the standard Glossary. This section defines additional terms, including those specific to this business or project.

Avoid duplicating terms from the standard Best Practices Process Library Glossary here.

If there are no additional terms to define, delete the term and definition line below as well as the sentence beginning with “This section defines...” in the unhidden paragraph above.

Term / Definition

[INSTRUCTIONS - From the AD Tools menu, select Remove Instructions or double-click the button.]

tions

ad_ds.doc 6 7/5/00