Rollout Plan - DOC

Document Sample
Rollout Plan - DOC Powered By Docstoc
					Enter Organization Name

     Enter Project Name
            Rollout Plan




                  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:




             Enter Project Name
                 Rollout Plan
           Enter Organization Name
                                 Document History
Reviewed By
    Organization                 Person




Copied To
    Organization                 Person




Revision Record
    Number   Date and Sections     Notes




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc   iii      7/28/12
                                     Acronyms
Acronym                Description




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc   v    7/28/12
                                    References
Document Title                                   File Name




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc   vii               7/28/12
                                     Table of Contents

1. INTRODUCTION                                                1

  1.1   Document Purpose                                       1
  1.2   Project Background                                     1
  1.3   Project Deliverable Roles                              1
  1.4   Related Documents                                      1

2. ROLLOUT PLANNING AND LAUNCH                                 1

  2.1   Iterative Rollout Plan                                 1
   2.1.1    Iteration Scope and Objectives                     1
   2.1.2    Iteration Activity Plan                            2
   2.1.3    Rollout Work Breakdown Structure (Detailed)        3
  2.2   Training Logistics                                     3
   2.2.1    Schedule                                           3
   2.2.2    Courses                                            3
   2.2.3    Trainers                                           3
   2.2.4    Facilities                                         3
     2.2.4.1 Location                                          3
     2.2.4.2 Equipment                                         3
   2.2.5    Training Configuration                             3
     2.2.5.1 Hardware                                          3
     2.2.5.2 Software                                          3
  2.3   Application Deployment Matrix                          4
  2.4   Access Control List                                    4
  2.5   Team Brief                                             4
  2.6   Training Class Assessment (Summary)                    4

3. INSTALLATION                                                4

  3.1   Lessons Learned (Installation)                         4
  3.2   Configuration Baseline                                 5
  3.3   Post-Installation Evaluation Report                    6
  3.4   Issue Log (enabling the whole-product solution)        7

4. ITERATIVE ROLLOUT REVIEW                                    8

  4.1   Effectiveness of Solution                              8
  4.2   Cost/Benefit Analysis                                  8
   4.2.1    Costs for Recommended Changes                      8


5. APPENDICES                                                  8




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc        ix        7/28/12
  5.1   Related Work Papers                                                            8
  5.2   Revision History                                                               8
  5.3   Problem Report / Change Request (related to the effectiveness of the solution) 9
   5.3.1   Required Enhancements                                                      9
   5.3.2   Problem Reports                                                            9


6. GLOSSARY                                                                           9




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc   x                                     7/28/12
1. INTRODUCTION

1.1 Document Purpose
The Rollout Plan provides the project team with information that identifies the rollout increments, summarizes
successes and problems with rollout, and includes recommended process improvements, amendments to
procedures, user guides, job aids, and standards and policies.

1.2 Project Background

1.3 Project Deliverable Roles
The people listed below will receive a copy of the Rollout Plan 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 28, 2012.

 Creator
 Organization                                               Name

 Reviewers
 Organization                                               Name



 Acceptor/Approvers
 Organization                                               Name




1.4 Related Documents



2. ROLLOUT PLANNING AND LAUNCH
2.1 Iterative Rollout Plan

2.1.1 Iteration Scope and Objectives
The following table contains the plan for the number of iterations for the rollout of the new technology including: the
scope of each iteration (functions, entities, etc.) covered, the objectives of each iteration (first pass, final pass, etc.),
and the estimated duration.

 Iteration          Scope                                          Iteration Objectives       Duration
 Number




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc                1                                                  7/28/12
2.1.2 Iteration Activity Plan
The following table contains the plan for the activities and individuals involved in each activity required to execute
each iteration.

 Iteration        Activities                                  Persons Responsible        Duration
 Number




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc               2                                               7/28/12
Activity Selection and Planning Table
                              Iteration #1        Iteration #2      Iteration #3    Iteration #4




2.1.3 Rollout Work Breakdown Structure (Detailed)
ID   Task                          Duration   Start   Finish     Resources




2.2 Training Logistics

2.2.1 Schedule

2.2.2 Courses

2.2.3 Trainers

2.2.4 Facilities

2.2.4.1 Location

2.2.4.2 Equipment

2.2.5 Training Configuration

2.2.5.1 Hardware

2.2.5.2 Software

Course      #   Course   Trainer     Backup       Date     Time       Location     TT    Size      Special
 Name            Level                                                                             Needs




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc          3                                        7/28/12
2.3 Application Deployment Matrix
The matrix documents the scheduling of hardware/software applications on nodes. Level of detail includes which
particular nodes are scheduled to receive which applications/components and when.


2.4 Access Control List
Table 1
                                      Access Levels / Roles
                 ADMIN             SUPERUSER     USER                  GUEST            [USER TYPE]
Read             X                 X             X                     X
No Read
Write            X                 X                   X
No Write                                                               X
Edit             X                 X                   X
No Edit                                                                X
Save             X                 X                   X
No Save                                                                X
Create           X                 X                   X
No Create                                                              X
Delete           X                 X
No Delete                                              X               X
Security         X
No Security                        X                   X               X
[Permission].    X                 X
[Limitation]                                                           X


Table 2

Table 3


2.5 Team Brief



2.6 Training Class Assessment (Summary)



3. INSTALLATION
3.1 Lessons Learned (Installation)
Below are the lessons learned from the installation routine from Rollout. These notes are documented so that actual
installations/deployment of the new technology during subsequent iterations (future projects) may be smoothly and
effectively achieved. Included in the lessons learned are risks and performance estimates of the component/package
against the existing technical architecture.

Component/Package                                      Installation Lessons Learned



1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc           4                                            7/28/12
Required Enhancements
This section documents and prioritizes enhancements that may be required in the form of Change Requests.
Enhancements may be necessary to achieve satisfactory performance levels and operational characteristics in
accordance with the findings presented in the previous section.

                                       Change Request Log
Change             Priority   Description
Request No.




3.2 Configuration Baseline

                                            Configuration Baseline
Configuration Component       Product(s)           Version       Release           Date           Notes/Descri
                                                                                                  ption




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc          5                                            7/28/12
3.3 Post-Installation Evaluation Report
Aspect                                                     Strongly   Agree   Disagree   Strongly
                                                           Agree                         Disagree
INSTALLATION PROCESS
 Installation was carried out expeditiously.
 Installation was carried out punctually, and in a
   timely manner.
 The installed software behaved correctly once
   installation was completed.
 Other software on the target machine continued
   to operate correctly after installation was
   completed.
FOOTPRINT OF INSTALLED APPLICATION
 The disk space provided on the target machine
   is adequate to support the application.
 The configured memory in the target machine
   is adequate to support the application.
 The disk and memory requirements of the
   application are not so great as to interfere with
   the functioning of other applications.
DOCUMENTATION AND HELP
 The application is provided with adequate
   paper and/or on-line documentation.
SECURITY AND ACCESS RIGHTS
 Necessary passwords were provided at install
   time.
 Necessary access rights were set up at install
   time.
 Password/access procedures were adequately
   explained and/or documented.
 Password/access procedures are not unduly
   onerous.
USABILITY
 The application is straightforward to learn and
   operate.
 The application is "well-behaved", i.e., complies
   with behavioral standards for its platform and
   does not exhibit surprising or perverse
   behavior.
PERFORMANCE
 The application loads and starts up in an
   acceptable time frame.
 Typically, application load and start-up takes:          N/A        N/A     N/A        N/A
   [specify time in seconds].



1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc               6                                       7/28/12
  Updating of the graphic display takes place at a
   satisfactory rate, and is not a source of
   distraction or frustration.
 Operations processed locally have a
   reasonable response time.
 A typical response time for a locally processed         N/A       N/A        N/A      N/A
   operation would be: [specify time in seconds].
 Operations processed remotely have a
   reasonable response time.
 A typical response time for a remotely                  N/A       N/A        N/A      N/A
   processed operation would be: [specify time in
   seconds].
RELIABILITY
 The application infrequently crashes, or
   "freezes" the machine.
 The application provides accurate information.
SUPPORT
 Support questions are answered promptly and
   clearly.
PROCEDURES
 Application operating procedures are not
   unduly complex or onerous.
 Manual procedures associated with the
   application are not unduly complex or onerous.


3.4 Issue Log (enabling the whole-product solution)

Identification

Ref #   Type     Priority   Description                                    Originator   Date Recorded




Resolution

Ref #   Status    Last      Actioner      Others                Decision   Resolution
                  Action                  Involved              Maker
                  Date




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc              7                                       7/28/12
Ref #    Status   Last      Actioner      Others             Decision      Resolution
                  Action                  Involved           Maker
                  Date




4. ITERATIVE ROLLOUT REVIEW
4.1 Effectiveness of Solution


4.2 Cost/Benefit Analysis

4.2.1 Costs for Recommended Changes

                             High Level, Total Costs for Changes
 Costs                                   Value    Assumptions

 Documentation                           $nnnK
 Training                                $nnnK
 Help Desk Resource                      $nnnK
 Communication Mechanisms                $nnnK
 Additional Vendor Support               $nnnK




5. APPENDICES
5.1 Related Work Papers
These work papers were used as inputs to this deliverable:

 Work Paper/Products                           Location




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

 Date      Description                   Person Responsible




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc             8                                     7/28/12
5.3 Problem Report / Change Request (related to the effectiveness of the solution)

5.3.1 Required Enhancements
This section documents and prioritizes application level enhancements that may be required in the form of Change
Requests.

                                        Change Request Log
Change             Priority    Description
Request No.




5.3.2 Problem Reports
This section documents and reports status of problem reports.
                                        Problem Report Log
Problem Report Status        Description
No.




6. 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.
Term                                Definition




1342b64c-88c4-45e2-a76b-ccee0a1fe1fa.doc             9                                             7/28/12

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:30
posted:7/27/2012
language:English
pages:19