Docstoc

Simple Business Plan Outline - Excel

Document Sample
Simple Business Plan Outline - Excel Powered By Docstoc
					Traditional New Development WBS Dictionary

#               Phase/Activity/Tasks                                                             Del Name & #            Dur. Est.   Critically   Skill
                                                                                                                                     Depend
1.0 Phase        Initiate – Obtaining agreement                       on     the    business N/A
                 requirement and charting the project.
1.1 Activity     Develop the Business Requirement – Establish a common N/A
                 understanding of the base requirements that are to be addressed by
                 the project.
1.1.1 Task      Create the Product Description – define, scope, and give context to the product & Product Description                             PM
                services that the project will be chartered to develop, deliver, and support.
1.1.2 Task      Prepare and Review the Product description – depending on audience Project Proposal, Document Approval
                preference, summarizes the content of the product description into an executive
                summary and deliver it or prepare and conduct a review of the product description.
                Obtain approval to charter a project that will assign initial planning resources to
                develop the project plan.
1.2 Activity     Charter the Project – Obtain the commitment and agreement N/A
                 between the sponsor and project team indicating how the project will
                 be conducted and who needs to be involved.
1.2.1 Task      Create the Project Charter – define the mission, authority, and level of project Project Charter                                  PM
                planning and controls necessary for the project, and indicate the personnel or
                groups expected to be involved in the project. Assign the project manager,
                sponsor, and any required resources to complete the overall project planning.
                Project Proposal Approved by
1.2.1.1 Milestone                                                                                N/A                                              PM
2. Phase        Plan – Creation and approval of the core work plan and N/A
                 facilitating plans which will guide project execution and
                 control.
2.1 Activity     Develop the Core Work Plan (CWP) – The development of the work N/A
                 scope, supporting schedule, budget, and project organization that
                 focuses and guides the project work effort.
2.1.1 Task      Develop the Scope Statement – Develop the scope statement with the customer CWP – Scope Statement                                 PM
                that indicates an agreement on work scope, project objectives and measurements,
                hi-level deliverables, assumptions, and completion criteria.




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                  1
Traditional New Development WBS Dictionary

2.1.2 Task     Develop the WBS – Define the work Activities, sequencing, effort estimates, and          CWP – WBS                               PM
               deliverables. Indicate the type of resource(people, equipment, materials, facilities)
               needed to complete the work activities. Review and obtain agreement of the WBS
               work activities with the customer, sponsor, and management of other groups
               expected to support the project.
2.1.3 Task     Develop the Project Schedule – Develop approximate cost estimates of all the             CWP – Schedule and Budget Projection    PM
               types of resources. Build a project schedule from the WBS and cost estimates.
               Produce a time-phased cost budget from the schedule.
2.1.4 Task     (Note) On large projects a feasibility study maybe a major phase prior to detailed       CWP – Feasibility and Recommendations
               planning. On very small or maintenance project the feasibility may be limited to
               cost/benefit assumption and recommendations. This project is considered a small
               project.
               Determine the Project Feasibility and Recommendation – Approximate and
               define the life span of the product or service being delivered. Approximate and
               define a dollar value for soft and hard benefits and any cost reduction or avoidance
               that may be the result of the product or service delivery. Chart or summarize the
               information and provide a recommendation
2.1.5 Task     Organize Project & Staff Acquisition – provide an overall framework to describe          CWP – Organization                      PM
               the roles, responsibilities and membership of the Project. Obtain the staff needed for
               the core team and staff need from other groups in the organization that will be cross-
               committed to the project. Obtain from management commitment of all non-
               contracted personnel. (Note– any contracted staff is acquired via the contract
               activity, however none are planned for this project.)
2.2 Activity   Develop the Facilitating Plans for Controls (FPC) – The plans for N/A
               ongoing work required to ensure that the project can anticipate
               possible problems, solve, and make coordinated work plan
               adjustments.
2.2.1 Task     Risk Management – Determine which risks are likely to affect the project, evaluate FPC – Risk Id and Mgmt
               potential risk outcomes and indicators, define plan to respond to key risks indicators.

2.2.2 Task     Change Management – Outline a simple change management process to FPC – Chg Mgmt
               coordinate approved changes in the project plan.
2.2.3 Task     Project Standards, Approval, And Document Controls – Define and setup the FPC – Stds, Apvls, Cntls
               documentation standards, document storage locations, project notebook, document
               approval and promotion process, and securities.




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                             2
Traditional New Development WBS Dictionary

2.2.4 Task      Communication Plan and Management – Outline a plan that identifies “who”               FPC – Comm. Plan & Mgmt
                needs “what” communications, in “what” media, “how” often and by “whom”.
2.2.5 Task      Status Reporting – Define how status will be reported, by whom, how often, and in      FPC – Status Rptg
                what formats and media.
2.2.6 Task      Procurements & Contracting – Determine what to procure and when, document              FPC – Proc. & Cntrkg
                requirements and identify potential sources.
2.2.7 Task      Quality Assurance – Identify the project’s relevant quality standards and determine    FPC- QA
                how to satisfy them.
2.2.8 Task      Time Tracking – Determine what level to track time at, how time will be tracked,       FPC – Time Tracking
                how frequently, and administer the time tracking activities.
2.2.9 Task      Issue and Decision Management – Determine process for raising and resolving            FPC – Iss. & Decision Mgmt
                project issues that impact the scope, schedule, cost or quality of the project.
2.3 Activity    Develop the Project Plan – Integrating the results of the other N/A
                planning activities into a coherent document to guide the project
                execution and control.
2.3.1 Task      Plan Integration – Summarize and incorporate the outputs of the planning Project Plan
                activities into a single reference document – the <project name> Project Plan. The
                plan is the reference document for work to be performed by all involved in the
                project and must be made easily accessible to all in electronic format.
2.3.2 Task      Plan Presentation and Review – Distribute, review and obtain approval of the Presentation, & Document Approval
                project plan from the project directing authoritie(s) and managers who have staff
                assigned to the project.
2.3.2.1 Milestone
                Plan and Schedule Approved by                                                      N/A                              0   PM
3.0 Phase       Execution                                                                              N/A
3.1 Activity    Feasibility Study – Note: Requirements definition is an extension of the               N/A
                process started in the Feasibility Study. Please see the Feasibility Lifecycle model
                to determine if all or some of the steps are necessary.
3.2 Activity    Define Requirements                                                                    N/A
                Specific deliverables depend on the tools and techniques used by the development
                staff and on the existing data documentation. The deliverables listed are examples
                of possible deliverables.
3.2.1 Task      Identify and describe the business area(s) to be affected by the new system            N/A




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                     3
Traditional New Development WBS Dictionary

3.2.1.1 Subtask     Define in detail the procedures, high level data requirements, existing reports and Function hierarchy diagrams
                    documents, roles and responsibilities, and organization of the user areas to be
                    impacted by the product being developed.
3.2.1.2 Subtask     Describe in detail business procedures and their data requirements.                 Procedure flow diagrams
3.2.1.3 Subtask     Describe existing computer systems and their data.                                  Responsibility/ function matrices
3.2.1.4 Subtask     Ensure that all required data elements have been identified in the data analysis.   Data flow diagrams (of the current physical system)
3.2.1.5 Subtask     Ensure that the sources and destinations of the data are known.                     Procedure descriptions
3.2.1.6 Subtask     Identify and prioritize candidates for procedural change and automation.            *Critical procedures
                  Note: This activity starts as a decomposition of the project management - product    *Candidates for procedural change
                  description. The degree to which it must be performed depends on the scope of the
                  project and the availability of existing documentation.
                                                                                                       *Entity Relationship diagrams
                                                                                                       *Entity descriptions
                                                                                                       *Index and descriptions of existing reports and
                                                                                                       documents
                                                                                                       *Descriptions of existing reports and documents
                                                                                                       *Changes and additions to the data dictionary
3.2.2 Task        Define data requirements (data model consisting of entities, data elements,          N/A
                  transactions, etc.)
3.2.2.1 Subtask      Ensure that all entities of consequence to the application area have been         Entity Relationship diagrams
                     identified.
3.2.2.2 Subtask      Identify and define the data elements to be used, changed, or created (attributes Definitions of all relationships between entities
                     analysis).
3.2.2.3 Subtask      Determine the source of data elements in the business process.                    Definition of data elements (attributes)
3.2.2.4 Subtask      Identify the business functions and/or existing computer systems that use each    *Data elements/ business functions (CRUD) matrix
                     data element.
                  Note: The relationship of data elements to functions (the CRUD) matrix provides a *Changes and additions to the data dictionary
                  validation of the data entity analysis. Data entity (or object-oriented) analysis is
                  intended to identify all required. In some cases it may be decided to include a
                  smaller set of data in the application.
3.2.3 Task        Identify and describe the functions of the new system                                N/A


3.2.3.1 Subtask       Identify the functions to be included in the new system and their data            *Identification of critical success factors
                      requirements.


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                      4
Traditional New Development WBS Dictionary

                                                                                                        *Function hierarchy diagrams of the processing
                                                                                                        requirements identified by the user
                                                                                                        *Function descriptions (policies, algorithms, input
                                                                                                        and output data flows, etc.)
                                                                                                        *Data flow diagrams (of the proposed logical
                                                                                                        system)
                                                                                                        *Description of data flow contents (data elements)
3.2.4 Task        Identify and describe constraints (e.g., critical time restrictions, etc.)            N/A
3.2.4.1 Subtask       Ensure that all operational and delivery requirements (e.g., response times,      *Response time expectations
                      product delivery deadlines, maximum number of users, volume restrictions,
                      frequency of use, and expected product life span, other expectations, etc.) are
                      known.
                                                                                               *System availability requirements
                                                                                               *Product delivery requirements (target dates for all
                                                                                               or parts of the product)
                                                                                               *System platform constraints (e.g., specific
                                                                                               hardware and system software requirements)
                                                                                               *Interoperability requirements
3.2.5 Task        Reevaluate initial development approach, impact analysis, costs and benefits N/A


3.2.5.1 Subtask       Ensure that the approach recommended in the Feasibility Study and reaffirmed Revisions to:
                      in phase 1.0 is still valid, given the detailed understanding of requirements.
3.2.5.2 Subtask       Ensure that cost benefits assumptions are still valid.                            *Statement of approach
3.2.5.3 Subtask       Ensure that impacts/interfaces on other projects and systems are accurately       *Statement of the scope of effect of the project
                      stated.
3.2.5.4 Subtask       Ensure that the development platform is sufficient to support the development     *Agreement(s) regarding inter-project
                      effort.                                                                           dependencies, including the sharing of software,
                                                                                                        data, etc.
3.2.5.5 Subtask       Revise approach and cost benefits statements as appropriate.                      *Development platform
                                                                                                        *Benefits/savings estimate
                                                                                                        *Cost estimate
3.2.6 Task        Prepare and submit Requirements Specification Document                                N/A
3.2.6.1 Subtask     Documentation of the requirements that can be validated by users, sponsors, IT      Requirement Specification Document
                    management, and developers.
3.2.7 Task        Reaffirm or revise the project plan                                                   N/A




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                      5
Traditional New Development WBS Dictionary

3.2.7.1 Subtask     Ensure that the project plan is accurate given the information determined during      Revised or reaffirmed project plan
                    this phase.
                                                                                              Detailed plan for the next phase(s)
3.2.8 Task        Obtain formal user and sponsor concurrence with requirements specifications N/A

3.2.8.1 Subtask    Ensure that users, sponsors and IT management authorize continued work on the Formal project plan and requirements acceptance
                   project.                                                                      form or memo by IT management and the sponsor
3.2.8.2 Subtask    Avoid effort on projects that should be ended or redirected.                  N/A
3.3 Activity      Macro/Architectural Design                                                     N/A
3.3.1 Task        Define the hardware/system software platform (including DBMS) for                       The following bullets must be done in collaboration
                  development and operations                                                              with NCS, P&P, CSS, SA, SSI and AMS.
3.3.1.1 Subtask     Identify the hardware upon which the new system will operate.                         *Hardware and system software requirement
3.3.1.2 Subtask     Identify the specific Internal Processing Facility (IPF).                             *Development platform
3.3.1.3 Subtask     Identify the system software under which the application will operate.                N/A
3.3.1.4 Subtask     Identify the DBMS and/or file system that will be used in the system.                 N/A
3.3.1.5 Subtask     Identify portability requirements.                                                    N/A
3.3.1.6 Subtask     Choose development tools and platform.                                                N/A
                  Note: If there is need to acquire hardware, system software, and/or network
                  software, use the Hardware and LAN Acquisition/Installation activity list to identify
                  those activities that are relevant to this project.
                  Note: There may be more than one platform upon which an application will run,
                  either because different functions will be best supported by different platforms or
3.3.2 Task        Determine how functions and data will be distributed                                    N/A

3.3.2.1Subtask      Identify how system functions will be distributed geographically and technically      *Description of distribution strategy
                    (across platforms).
                                                                                                          *Description of alternatives considered
3.3.3 Task        Identify which network system(s) will be used                                           N/A
3.3.3.1 Subtask     Determine the network(s) that will support the application.                           Statement of networks involved
3.3.4 Task        Define environmental controls (e.g., security, contingency planning, restart            N/A
                  recovery)
3.3.4.1 Subtask     Identify the security features of the system.                                         Specifications for security, contingency and back-
                                                                                                          up/restart requirements
3.3.4.2 Subtask     Create contingency plan and/or revise existing contingency plans.                     N/A
3.3.5 Task        Define audit and control functions (error control, control totals, etc.)                Plan back-up and recovery processes.




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                        6
Traditional New Development WBS Dictionary

3.3.5.1 Subtask      Identify and describe the controls to be built into the system and used to ensure      *Audit and control specifications
                     that data integrity is maintained.
                                                                                                            *Audit trail capture and reporting requirements
3.3.6 Task         Define application standards (e.g., screen formats) and common software                  N/A
                   functions
3.3.6.1 Subtask      Establish application wide standards to create a consistent user interface.            User interface standards
3.3.6.2 Subtask      Identify the software functions that will be developed as common routines or           *Common routine/ software tool specifications
                     software tools.
                                                                                                            *Identification of existing reusable code to use
3.3.7 Task         Identify which requirements are to be automated                                          N/A
3.3.7.1 Subtask      Identify the specific functions described in Activity 2.3 to be included in the new    Specifications for each function
                     system.

3.3.8 Task         Create product delivery plan (for phased delivery)                                       N/A
3.3.8.1 Subtask      Identify the functions to be delivered in the planned versions of the system.          Product delivery plan
                   Note: This activity is included for use in large development efforts in which there is
                   need to deliver the product in phases or versions instead of as the result of a single
3.3.9 Task         Identify subsystems, their data requirements and interfaces                              N/A
3.3.9.1 Subtask      Package the new system's functions into subsystems and map the flow of data            Systems flow diagrams
                     between them.
3.3.9.2 Subtask      Identify files and/or databases.                                                       Data flow descriptions extended to indicate media
3.3.10 Task        Estimate storage, telecommunications and/or processor impacts                            Identify the media (screen, paper, electronic file,
                                                                                                            document, etc.) for each data flow.
3.3.10.1 Subtask  Determine the impact of processing and storage volumes on the hardware (data              Hardware and communications resource
                  storage, processor capacity) and on communications resources.                             acquisition requirements.
                Note: If the system requires the acquisition of new hardware and network
                resources (as opposed to increased capacity) see the Hardware and LAN
                Acquisition/Installation project type.
3.3.11 Task     Conduct walk-through(s) of the design                                                       N/A
3.3.11.1 Subtask Ensure that the various aspects of the design fulfill the requirements and comply          *Issues list
                  with standards.
                                                                                                            *Issues resolutions
                                                                                                            *Changes to design or requirements
                                                                                                            documentation
                                                                                                            *Sign-off(s) indicating concurrence
3.3.12 Task     Reevaluate development approach, impact analysis, costs and benefits                        Revisions to:
3.3.12.1 Subtask Statement of approach                                                                      *Statement of the scope of effect of the project


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                          7
Traditional New Development WBS Dictionary

3.3.12.2 Subtask     Ensure that the approach recommended in the Feasibility Study and reaffirmed in *Agreement(s) regarding inter-project
                     phase 2.0 is still valid, given the design results.                              dependencies, including the sharing of software,
                                                                                                      data, etc.
3.3.12.3 Subtask     Ensure that cost benefits assumptions are still valid.                           *Development platform
3.3.12.4 Subtask     Ensure that impacts on other projects and systems are accurately stated.         *Benefits/savings estimate
3.3.12.5 Subtask     Revise approach and cost benefits statements as appropriate.                     *Cost estimate
3.3.13 Task        Prepare a Macro/Architectural Design Document
3.3.13.1 Subtask   Describe the macro/architectural design in a document.                             Macro/Architectural Design Specification
3.3.14 Task          Reaffirm or revise the project plan                                              Revised or reaffirmed project plan
3.3.14.1 Subtask     Ensure that the project plan is accurate given the information determined during *Detailed plan for the next phase(s)
                     this phase.
                                                                                                      *Sign-off acknowledging acceptance of
                                                                                                      requirements, design and project plan
3.4 Activity       Design Data Base and/or Files                                                      N/A
3.4.1 Task         Refine the data model into a logical, application data model                           N/A
3.4.1.1 Subtask      Normalize the data model.                                                            Description of the logical data model in the form of
                                                                                                          file, record, table, segment and other descriptions
                                                                                                          with keys and response and access requirements
3.4.1.2 Subtask      Identify the data required to support computerized functions.                        N/A
3.4.1.3 Subtask      Identify data segments or records based on the way data will be used in the          N/A
                     system.
3.4.2 Task         Design physical data base and/or files                                                 N/A

3.4.2.1 Subtask      Map the logical data base design to the specific database or file management         Physical data base design
                     system(s) to be used.
3.4.2.2 Subtask      Describe the data, as it will be stored on the physical media.                       N/A

3.4.3 Task         Refine storage impact estimates                                                        N/A
3.4.3.1 Subtask      Reevaluate storage utilization and system capacity estimates previously made         Revised storage and other hardware capacity
                     (Activity 3.10) based on the completed design.                                       requirements
3.4.3.2 Subtask      Provide computer operations and hardware acquisition people with accurate            N/A
                     information regarding requirements for operations, including conversions.
3.4.4 Task         Conduct walk-throughs of the data designs                                              N/A


3.4.4.1 Subtask      Validate the designs (logical and physical) to ensure that they adequately fulfill   *Issues list
                     requirements.


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                         8
Traditional New Development WBS Dictionary

                                                                                                           *Issues resolutions
                                                                                                           *Changes to design or requirements
                                                                                                           documentation
                                                                                                           *Sign-off
3.5 Activity      Functional Design                                                                        N/A
                  Note: The use of prototyping and Joint Application Design (JAD) are recommended
                  for the design of reports, screens and documents. See the RAD template to use
                  activities related to prototyping.
3.5.1 Task        Design reports                                                                           N/A

3.5.1.1 Subtask     Layout the format of reports.                                                          Report layouts added to data flow descriptions
3.5.2 Task        Design dialogues, expected query requirements and user procedures                        N/A

3.5.2.1 Subtask     Identify the dialogues needed to support the procedures that will be followed by       *Dialogue maps - screen flow diagrams.
                    system users.
                                                                                                           *User procedure descriptions
3.5.3 Task        Design screens                                                                           N/A
3.5.3.1 Subtask     Layout the format of the screens that will be required within the system.              Screen layouts
3.5.4 Task        Refine logical and physical data base designs                                            N/A
3.5.4.1 Subtask     Determine if the functional design has caused any change to the data base design       Revisions to logical and physical data base designs
                    and, if so, make the changes.
3.5.5 Task        Design forms and other documents                                                         N/A
3.5.5.1 Subtask     Layout of the forms and documents that will be required within the system.             Form and document layouts
3.5.6 Task        Define data and transaction editing requirements                                         N/A
3.5.6.1 Subtask     Identify and describe the editing/validation rules for each data element and each      Editing rules per data element and transaction
                    transaction (input data flow) in the system.
                  Note: Data element editing can be defined as soon as the data elements are               Error message text
                  identified. All editing rules should be recorded in a data dictionary, if one is being
                  used.
3.5.7 Task        Prepare program (software component) specifications                                      N/A


3.5.7.1 Subtask     Prepare descriptions of the programs (Software components) to be developed,            Program (software component) specifications
                    identifying inputs, processing, performance constraints and outputs.
3.5.8 Task        Refine the macro/architectural design                                                    N/A
3.5.8.1 Subtask     Determine if the macro/architectural design should be changed based on the             Revisions to the macro/architectural design
                    findings of the functional design.



975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                         9
Traditional New Development WBS Dictionary

3.5.9 Task        Define audit and control functions (error control, control totals, etc.)               N/A
3.5.9.1 Subtask     Identify and describe the controls to be built into the system and used to ensure    *Audit and control specifications
                    that data integrity is maintained.
                                                                                                         *Audit trail capture and reporting requirements
3.5.10 Task     Validate that all requirements have been addressed                                       N/A
3.5.10.1 Subtask Ensure that the functional design covers all functions identified in the                Cross reference matrix of requirements to software
                  requirements.                                                                          components and data flows described in the
                                                                                                         functional specifications
3.5.11 Task     Reaffirm or revise the project plan                                                      N/A
3.5.11.1 Subtask Ensure that the project plan is accurate given the information determined during        *Revised or reaffirmed project plan
                  this phase.
                                                                                                         *Detailed plan for the next phase(s)
                                                                                                         *Sign-off(s) indicating concurrence
3.6 Activity      Plan for Implementation                                                                N/A
                  Note: This phase may be performed in parallel with the previous phase. Changes
                  to any of the aspects of the implementation plan may be made as a result of findings
                  in other phases.


3.6.1 Task        Acquire hardware and system software resources

                  (See Hardware and LAN Acquisition/Installation project type).                          Purchase orders
3.6.1.1 Subtask     Initiate the process of ordering any hardware and system software required.          *Installation plans and schedules

                  Note: Hardware/software acquisition may require long lead times; therefore, initiate *Revisions to cost estimates and project schedules
                  the acquisition process as early as possible.                                        (based on responses from vendors and
                                                                                                       contractors, including computer operations)
3.6.2 Task        Plan for file/data base conversions                                                    N/A
3.6.2.1 Subtask   Identify conversion requirements.                                                      Data Conversion plan
3.6.2.2 Subtask     Determine the way the conversion will be performed (what programs, what              Conversion program specifications
                    controls, etc.).
3.6.2.3 Subtask     Schedule the conversion effort.                                                      Conversion procedure
3.6.3 Task        Develop test strategy and plans                                                        N/A
3.6.3.1 Subtask     Ensure that test plans for all levels of testing are available to validate the new   *Test objectives
                    system and all systems being affected by it.
                  Note:                                                                                  *Levels of testing


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                      10
Traditional New Development WBS Dictionary

                    1.      Unit test planning is not included in this activity; it is part of the program   *Test cycles
                    development phase.
                    2.      If testing software is needed it should be specified here and developed as       *Test plan data
                    part of Activity 7.1
                                                                                                             *Acceptance criteria.
                                                                                                             *Role and responsibility assignments for testing
3.6.4 Task        Develop user/ operator training and documentation development plan                         N/A
3.6.4.1 Subtask     Identify required user, support staff and/or operator documentation and training.        *Document descriptions and outlines
                  Note: Documentation includes Help screen contents, tutorials, training materials,          *Plan for creating the documents, including
                  quick reference cards and manuals. Documentation may be on paper or in                     responsibility assignments
                  electronic form.
3.6.5 Task        Review (walk-through) Implementation Plans                                                 N/A
3.6.5.1 Subtask     Ensure that all required implementation activities have been identified and              *Issues and resolutions
                    scheduled.
                                                                                                             *Sign-off indicating concurrence

3.6.6 Task        Reaffirm or revise the project plan                                                        N/A
3.6.6.1 Subtask     Ensure that the project plan is accurate given the information determined during         *Revised or reaffirmed project plan.
                    this phase.
                                                                                                             *Detailed plan for the next phase(s)
                                                                                                             *Sign-off acknowledging acceptance of
                                                                                                             implementation and project plan
3.6.7 Task        Schedule system implementation                                                             N/A
3.6.7.1 Subtask     Specify when the system will be introduced into the production environment and           *Turnover schedule
                    when the user will be expected to begin testing and actual use.
                                                                                                             *Data conversion schedule


                                                                                                             *Volume and acceptance test schedule
3.7 Activity      Program Development                                                                        N/A
                  Note: This project type assumes software development, as opposed to acquisition
                  or reengineering.
3.7.1 Task        Design software components (program design)                                      N/A
3.7.1.1 Subtask     Identify program structures and modules for the programs (software components) *Program hierarchy diagrams for application and
                    specified.                                                                     data conversion programs




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                        11
Traditional New Development WBS Dictionary

                  Note: The extent of detail depends on design standards and on the level of detail in *Data flow diagrams
                  program specifications developed earlier.
                                                                                                       *Pseudo code

3.7.2 Task        Perform walk-throughs of the program designs                                        N/A
3.7.2.1 Subtask     Ensure that program designs comply with standards and fulfill requirements as     Issues and resolutions
3.7.2.2 Subtask     specified.
                    Identify opportunities for using previously developed components.                 N/A
3.7.2.3 Subtask     Identify components that may become reusable.                                     N/A
3.7.3 Task        Program software components                                                         N/A
3.7.3.1 Subtask     Construct or generate the programs.                                               Coded components
3.7.4 Task        Unit test and integration test (including necessary reprogramming)                  N/A
3.7.4.1 Subtask     Ensure that software components perform according to specifications.              Test plan (data and cycles)
3.7.4.2 Subtask     Ensure that groups of components perform according to spec and interface with     *Test job control or command lists
                    one another properly.
                  Note: A walk-through of the unit test plan should be held to ensure that the plan   *Test results (error log, acceptable test results)
                  covers all required tests. Unit planning can be performed prior to coding.
                                                                                                      *Changes to components with errors
                                                                                                      *Tested components in a controlled library
3.8 Activity      Implementation – Transition to Production                                           N/A

3.8.1 Task        Develop user documentation, operations and support documentation and                N/A
                  training materials
3.8.1.1 Subtask      Develop new materials or make changes to existing documentation and training     *Documentation and training materials (e.g.,
                     materials based on the specified plan.                                           manuals, Help screens, tutorials, run books, etc.)
                                                                                                      *Completed contingency plan documentation)
                                                                                                      *Service level agreement log entry
3.8.2 Task        Train users, operators, and support staff                                           N/A
3.8.2.1 Subtask     Ensure that all users, operators and support staff are able to use the system.    Trained users, operators, and support staff
3.8.3 Task        System test (including necessary rework)                                            N/A
3.8.3.1 Subtask     Ensure that the new system operates according to specification, using the plan    Systems test Job control or command lists
                    developed in Activity - Develop test strategy and plans.
3.8.1.2 Subtask     Ensure that the system performs as expected under volume and exception            *Systems Test results (error log, error reports,
                    conditions.                                                                       acceptable test results)




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                   12
Traditional New Development WBS Dictionary

                  Note: A walk-through of the system test plan should be held before the test to            *Changes to programs and documentation
                  ensure that the plan covers all required tests.
                                                                                                            *System tested software in controlled library(ies)

3.8.1.3 Subtask     System testing can be broken down into levels of testing to include volume test,        N/A
                    usability test, etc., see guidelines on testing.
3.8.4 Task        Acceptance Test (including necessary rework)                                              N/A
3.8.4.1 Subtask     Provide the user and/or sponsor the proof that the changed system works                 *Appropriate job control or command lists
                    according to expectations.
                  Note: Acceptance testing may include parallel test, usability test, Beta Test, or other   *Test results (error log, error reports, accept-able
                  tests. It may be performed in a special test environment.                                 test results)
                                                                                                            *Changes to programs and documentation
                                                                                                            *Written approval by user acceptance authority
                                                                                                            *Accepted software in controlled library
3.8.5 Task        Prepare for transition to production                                                      N/A
3.8.5.1 Subtask     Ensure that the production environment (including users, operations personnel,          Implementation schedule (revised)
                    and support staff) is prepared for the start of production.
3.8.5.2 Subtask     Install required new hardware, system software, and communications systems.        *Operations schedules (batch schedule and on-line
                                                                                                       availability)
                  Note: For applications to be run by computer operations all forms must be filled out *Programs transferred to production libraries
                  and submitted, as required by current procedures.
                                                                                                       *Production file space properly allocated
                                                                                                       *Production job control or command lists available
                                                                                                       *Necessary changes made to high level menus for
                                                                                                       user access
                                                                                                       *New or changed security data (passwords, etc.) in
                                                                                                       the proper tables
                                                                                                       *Users and support staff of systems that may be
                                                                                                       effected by the new system advised of the
                                                                                                       transition
3.8.6 Task        Perform data conversions                                                             N/A
3.8.6.1 Subtask     Make data set (files, data bases, tables) ready for the start of production.       *Converted or initialized production data sets
                                                                                                       *Control reports
3.8.7 Task        Perform environment test
3.8.7.1 Subtask     Ensure that the new software operates without disrupting the production            *Test results (error log, error reports, acceptable
                    environment.                                                                       test results)


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                           13
Traditional New Development WBS Dictionary

                                                                                                            *Changes to programs and documentation
                                                                                                            *Software accepted by operations and support
3.8.8 Task        Complete system installation                                                              N/A
3.8.8.1 Subtask    Put the new system into production use.                                                  *Documentation distributed
                                                                                                            *System installed
3.9 Activity      Post Implementation Evaluation                                                            N/A
                  Note: Project performance evaluations can be performed for groups of small
                  Product performance (Systems performance and Change impact) reviews may be
                  held more than once during the life of a product. When all or part of the change or
3.9.1 Task        Project performance exercised
                  new system will not be evaluationuntil long after the project (e.g., a change that will   N/A
3.9.1.1 Subtask     Evaluate project performance                                                            Project performance review with suggestions for
                                                                                                            improving the SDP and technical guidelines
3.9.2 Task        System performance review                                                                 N/A
3.9.2.1 Subtask      Evaluate the performance of the changed system in terms of resource use,               System performance review with recommendations
                     usability, and the degree to which it met user expectations.                           for change
                  Note: This review should be held after use of the system provides sufficient data for
                  analysis.
3.9.3 Task        Change impact review                                                                  N/A
3.9.3.1 Subtask      Evaluate the user environment to determine if expected benefits were achieved. Cost analysis review with recommendation for
                                                                                                        change.
                  Note: This review should be held after learning curves have been experienced and
                  after the system has been in use for enough time to accurately determine if it has
                  provided expected benefits.
4.0 Phase         Controls – Administer and manage work controls to N/A
                  ensure project performance.
4.1 Activity      Project Procedures and Controls –                                                         N/A
4.1.1 Task        Risk Management – Manage risks by responding to identified risk indicators as FPC – Risk Id and Mgmt
                  they occur.
4.1.2 Task        Change Management – Identify, plan, and conduct ongoing change control of the FPC – Chg Mgmt
                  project. Ensure that the requirements, budget, and schedule milestones remain in
                  line with the current approved project plan or are changed officially providing new
                  requirements, budget, or schedule milestones.
4.1.3 Task        Project Standards, Approval, And Document Controls – Conduct administration FPC – Stds, Approvals, & Cntls
                  of approvals, project library, administrative filing, and securities.
4.1.4 Task        Communication Management – Deliver communications or facilitate FPC – Comm. Plan & Mgmt
                  communication delivery and conduct ongoing administration of communications


975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                                      14
Traditional New Development WBS Dictionary

4.1.5 Task      Status Reporting –Conduct ongoing project status reporting of work activities,       FPC – Status Rptg
                budgets achievements and issues.
4.1.6 Task      Procurements & Contracting Management – obtain quotations, bids, offers, or          FPC – Procurements & Contracting
                proposals, choose from among potential vendors, administer the contract, and
                close.
4.1.7 Task      Quality Assurance – monitor and identify way to eliminate causes of unsatisfactory   FPC- QA
                quality performance.
4.1.8 Task      Time Tracking – administer the time tracking activities and team recording of        FPC – Time Tracking
                individual time
4.1.9 Task      Issue and Decision Management – Administer the issue and decision process.           FPC – Issue and Decision Mgmt
5.0 Phase       Close – Evaluate the projects achievement of scope,                                  N/A

                objectives, and measurements. Identify the maintenance
                plan, turn-over to maintenance, and release project
                resources.
5.1 Activity    Project Evaluation – Recognize the achievements and lessons N/A
                learned of the project, and determine readiness to close the project.
5.1.1 Task      Prepare a project evaluation – Review the project’s completion criteria, scope, Project Evaluation & Lessons Learned    PM
                objectives, measurements, and lessons learned. Document and analyze the
                information and review with the sponsors. Obtain agreement from the sponsors on
                readiness to proceed with project closure.
5.2 Activity    Plan for Maintenance and Turn-over – Coordinate “what” will be N/A
                maintained and prepare supporting materials to enable smooth
                transition to maintenance. Close Project.
5.2.1 Task      Coordinate Maintenance Turn-over – Identify all items or components, and their Maintenance Turn-over
                production version/location, which will become maintenance responsibility. Ensure
                change request log is accurate and up-to-date. Ensure all issues and prior
                decisions are documented for turn-over. Identify maintenance staff and any
                associated budgets. Meet with maintenance lead and review this information.
5.2.2 Task      Close out Project – Prepare for and celebrate project closure. Release project Project Celebration Closing
                resources.
                Project successfully turned-over to maintenance and closed
5.2.2.1 Milestone                                                                                 N/A
5.2.3 Task




975fa871-a8cf-49d3-8342-d18eef8e2a41.xls                                                                                                     15

				
DOCUMENT INFO
Description: Simple Business Plan Outline document sample