Web Development Project Cost

Document Sample
Web Development Project Cost Powered By Docstoc
					                      Template Examples Disclaimer

Unless otherwise specifically stated, the information contained herein
is made available to the public by the Department of Human
Services, Office of Information Services, Project Management Office
for use as an example of template content information and may not
reflect the realities of an actual project. The intent of the template
example is to assist an individual creating a new document using the
PMO standard template.

Neither the DHS, OIS, PMO nor any other agency or entities thereof,
assumes any legal liability or responsibility for the accuracy,
completeness, or usefulness of any information, product or process
disclosed in these examples.

Reference herein to any specific commercial product, process,
service by trade name, trademark, manufacturer, or otherwise, does
not constitute or imply its endorsement, recommendation, or favoring
by the PMO or any entities thereof.

The views and opinions of the originators expressed therein do not
necessarily state or reflect those of the DHS, OIS, PMO or any
agency or entities thereof.




Author: Debra Herrli
C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc
Created on:  9/21/2011
    MMIS Web Technology Requirements Integrated Project Plan



      Oregon Department of Human Services
          Office of Information Services
    MMIS Web Technology Requirements Project

                        Integrated Project Plan
                       Approval Date: <mmm dd, yyyy>



                                           Planning




                    Determine work                       Determine work
                  activities, resources,                controls to ensure
                    schedule, costs                    project performance
                   (Core work Plans)                    (Facilitating Plans)
                                                                               Project Plan

                                   Incorporate planning
                                 outputs into one coherent
                                         document
                                 (Integrated Project Plan)




                                           Executing




                            Purpose of the Document
The Integrated Project Plan is used to guide both project execution and project
control. It is required to ensure that the various elements of the project are
properly coordinated. It is a document or collection of documents, which
communicate the project’s plan. The integrated plan should be expected to
change over time, as more information becomes available to the project.

The amount of planning performed should be commensurate with the scope of
the project and the usefulness of the information developed.



C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc
Last printed 9/21/2011 10:29:00 AM
    MMIS Web Technology Requirements Integrated Project Plan

                         Document Change Activity
The following is a record of the changes that have occurred on this document
from the time of its original approval
#   Change Description                                            Author Date
1   Initial Document Creation                                     DAH    9/30/03




C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc
Last printed 9/21/2011 10:29:00 AM
     MMIS Web Technology Requirements Integrated Project Plan


1  Problem/Opportunity .................................................................. 1
2  Scope Statement........................................................................ 1
 2.1    Objectives ........................................................................... 1
 2.2    Major Deliverable Milestones .............................................. 2
 2.3    Assumptions ....................................................................... 2
 2.4    Completion Criteria ............................................................. 2
3 Work Plan .................................................................................. 2
 3.1    Work Breakdown Structure (WBS) and Schedule ............... 3
 3.2    Budget Projection ................................................................ 3
4 Organization ............................................................................... 3
 4.1    Internal Roles & Responsibilities ......................................... 3
   4.1.1 Steering Committee ......................................................... 3
   4.1.2 Project Sponsor ............................................................... 3
   4.1.3 Project Manager .............................................................. 3
   4.1.4 Core Team Members ....................................................... 4
   4.1.5 Technical Oversight Group .............................................. 4
 4.2    Participating Members ........................................................ 5
5 Facilitating Controls .................................................................... 5
 5.1    Change Management Plan.................................................. 5
 5.2    Quality Management Plan ................................................... 6
 5.3    Risk Management Plan ....................................................... 6
 5.4    Status Reporting ................................................................. 6
 5.5    Project Document Standards, Approval, and Controls......... 7
 5.6    Cost Management Plan ....................................................... 7




C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc                 Page i
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan


1 PROBLEM/OPPORTUNITY
This project will investigate alternative web architecture and infrastructure
requirements for the new MMIS, and will evaluate them for benefits,
drawbacks, risk, additional cost and time to MMIS, and long-term impact on
DHS systems. As part of the project, the question about whether DHS
should develop and implement the MMIS system with an underlying
framework, and if so, whether that infrastructure might serve as the
foundation for development of future DHS systems will be addressed.

2 SCOPE STATEMENT
The project scope includes all the work required, and only the work
required to successfully complete the project. The defined work will be an
integration of the work required to plan and manage the project with the
work to define, implement and support the customer’s request. The
following section’s objectives, milestones, assumptions and completion
criteria indicates what is in scope for this project:
2.1Objectives

The following are the approved objectives from the product description.
   1. Objective-1
   Estimate the number and type of web-based systems that DHS will
   develop from 2005 through 2010. This information will be used as the
   basis for estimating some of the advantages and benefits of a web
   infrastructure.
   2. Objective-2
   Investigate and document the MMIS web architecture requirements,
   considering the option of a framework infrastructure. This effort will
   include an analysis of MMIS architectures currently being delivered to
   states.

   3. Objective-3
   Document the impact, advantages, disadvantages, risks, and cost for
   both the MMIS system and for future DHS system development.
   Recommend a preferred solution from the alternatives investigated.


C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 1
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

   4. Objective-4
   Prepare a report and presentation summarizing the project results for
   the MMIS Executive Steering Committee, the DHS Director, and the
   DHS Cabinet.
2.2Major Deliverable Milestones

This is the basis for a high-level plan. Planned complete dates may initially
be best guesses until more work has been defined as part of the project.
MS# Milestone Description                                                  Planned
                                                                           Complete
MS1 Estimate # and type of future DHS Web-based                            10/31/2003
systems
Develop an estimate of the number and type of web-based
systems that DHS will develop from 2005 to 2010.
MS2 Develop MMIS Web Architecture Requirement                              11/15/2003
Requirement must include the option of a framework
infrastructure.
MS3 Document Advantages, Benefits, Risk, Cost                              12/1/2003
Develop description of MMIS web architecture advantages and
benefits to MMIS and future DHS information systems.
MS4 Report and Presentation                                                12/19/2003
Prepare a report and presentation for the MMIS Executive
Steering Committee, DHS Director, and DHS cabinet.


2.3Assumptions

Define any known planning assumptions.
2.4Completion Criteria

All of the objectives and milestones have been satisfactorily met and
accepted by the business and OIS steering committee or responsible
management.

The report and presentation have been reviewed and approved by the
MMIS Executive Steering Committee, DHS Director, and DHS Cabinet.

3 WORK PLAN

C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 2
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

3.1Work Breakdown Structure (WBS) and Schedule

The work breakdown structure incorporates the milestone plan with the
management or coordination of the project. The System Maintenance
methodology – project control document is the basis for the major
milestones.

The WBS Dictionary is located in the appendix of this document due to the
page orientation and size.

3.2Budget Projection

This project is expected to utilize 8 staff for 20% of their time in October,
November, and December 2003. Total FTE is projected to be 1.6 for 3
months.

4 ORGANIZATION
4.1Internal Roles & Responsibilities

The Roles & Responsibilities Facilitating Plan contains a detailed
description of the roles and responsibilities for each team member.

4.1.1 Steering Committee

        MMIS Steering Committees: The MMIS Steering Committees,
        Sponsor, and Project Manager will meet monthly to review progress,
        provide objective issue resolution guidance, and ensure that the
        project team and other associated members are working
        collaboratively for a successful implementation.

4.1.2 Project Sponsor
       Sponsor: The Co-Sponsors will provide the Executive Leadership,
       priority and commitment to the project, its goals and objectives. The
       Sponsors assure appropriate resources, funding and the final
       decision on issues that may need resolution by the project team.

        Jim Joyce, MMIS Project Manager

        Clyde Saiki, Administrative Services Deputy Director

4.1.3 Project Manager

C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 3
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

       Debra Herrli, Project Manager, is responsible for the project plan,
       organization, work execution, and controls to ensure successful
       project performance relating to cost, schedule and quality. Delivers
       the agreed-upon business goals and objectives on time, within
       budget, and with the expected level of quality. Works closely with the
       sponsors to plan the project, resolve issues, and monitor team
       activities. Manages day-to-day project activities and supervises
       project team.
4.1.4 Core Team Members

        This team is responsible for providing technical expertise,
        coordinating and performing research, and writing the final
        recommendation.

        Team members include:
 Name                             Role                               Commitment
 Ron Hittner                      Facilitator                        20%
 Bryan Nealy                      PMO                                20%
 Jim Simpson                      DASG – ORCA                        20%
 Joyce Martinez                   MMIS                               20%
 Nick Knickerbocker               MMIS                               20%
 Ying Ki Kwong                    MMIS                               20%
 Digby Morrow                     T&S                                20%
4.1.5 Technical Oversight Group

       This group is responsible for reviewing and critiquing the technical
       conclusions of the core group, providing input and feedback from and
       all-OIS perspective. Team members include:

Name                            Role                                 Commitment
Margaret Armatrout              ISE/Mainframe Self-sufficiency       Occasional
                                systems                              meetings
Kurtis Danka                    DASG                                 Occasional
                                                                     meetings



C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 4
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

Walt Davis                      NEDSS                                Occasional
                                                                     meetings
Jason Sacks                     EXPRS                                Occasional
                                                                     meetings
Katherine Sherman               ISE/Admin. Systems                   Occasional
                                                                     meetings
Others as nominated by          OIS Technical                        Occasional
the technical group                                                  meetings
4.2Participating Members
Participating Members: The Participating Members shall review and verify
the draft work developed by the core members. The Participating Members
are:
   DHS AS Office of Information Systems ISE Managers:
   Sue Eastman, ASM                               Susan Akey, DASG
   Stacey Harrison, ASM                           Leo Ott, ATM
   Katherine Sherman, ATM                         Harold Gronsdahl, ATM
   Conch Virata, ATM                              Steve Simmons, ATM
   Harry Phelps, ATM                              Susam Strohm, NEDSS PM
   Pete Mallord, eXPRS PM                         Pam Davis, DSSURS PM
   Barbara Woods, TWIST PM                        Jarred Clark, HIPAA PM
   Darcel Pecyna, EDMS PM                         Buck Wooward, PSOB PM
   Julie Mallord, ISE

DHS AS Managers:
   Theresa Masse, DHS Information Security Manager
   DHS Business Analysts:
   TBD
   Preliminary estimated time commitment is 6 hours per month for
      the length of project.

5 FACILITATING CONTROLS
5.1Change Management Plan

C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 5
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

All changes will be negotiated between the Project Manager and Project
Sponsor. Changes will be documented using a change request form and
with result in an update to the project plan.
5.2Quality Management Plan

The Business and Technical Assessment indicated that this project was of
low complexity. The project will incorporate an outside consultant to
provide high-level quality assurance.

5.3Risk Management Plan

The project has determined the risks that are likely to occur and have a
high impact to the success and timing of the project. The following is a list
of the risks and the plan for how the project plans to mitigate each risk:
Risk: Team member bias may affect the product’s analysis and
recommendation.
Mitigation: An outside consultant will be included on the team to assist
with providing an un-biased evaluation and recommendation.
Risk: Execution of this project depends upon allocation of team members’
limited time. If team members are not able to work on the project the
specified amount of time, the product and timeframe will be impacted.
Mitigation: Closely monitor team member’s work on the project against
estimated work needed. Discuss any lags immediately with team member,
elevating if necessary.

Risk: The short project timeframe and scarce resources available to the
project will limit the amount of research that can be done. This may affect
the accuracy of some of the analysis, such as the estimate of future web
systems or the impact to cost and time to the MMIS project.
Mitigation: The addition of an outside consultant to the team will help
ensure a quality product. If it becomes apparent that accuracy is suffering,
the issue will be elevated to the Project Sponsor and Steering Committee
for discussion and possible time extension or additional resources to
ensure a thorough analysis.
5.4 Status Reporting
The project manager will deliver status reporting to the steering committee
and sponsor formally on a monthly basis during regularly scheduled

C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 6
Last printed 9/21/2011 10:29:00 AM
        MMIS Web Technology Requirements Integrated Project Plan

meetings. Informal status will be given weekly at the regularly scheduled
team meetings.
5.5Project Document Standards, Approval, and Controls
All internal work products being drafted or revised will be located in a
shared electronic project directory using the PMO Standard directory
structure. The directory is located on Pkwy2_ns1/data/shared/MMIS Web
Technology Requirements.

5.6Cost Management Plan

Team member’s time will not be tracked for this project. The project will
have one $5,000 contract that will be tracked using the standard contracts
and procurement tracking methods.




C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc   Page 7
Last printed 9/21/2011 10:29:00 AM
                                 MMIS Web Technology Requirements Integrated Project Plan

                                                                                                            Del Name & #   Dur.   Critically   Skill
#               WBS Dictionary                                                                                             Est.   Depend

                                                                                                            N/A
1. Phase        Initiate – Obtaining agreement on the business requirement and charting the project.
                                                                                                            N/A                                PM
               Project Proposal Approved by Jim Joyce, Clyde Saiki, Kristen Duus, and Fariborz
1.1.1.1. Milestone
                Pakseresht 10/15/03
                                                                                                            N/A
2. Phase        Plan – Creation and approval of the core work plan and facilitating plans that will guide
                project execution and control.
                                                                                                            N/A
2.1. Activity   Develop the Project Plan – Integrating the results of the other planning activities
                into a coherent document to guide the project execution and control.
                                                                                                            N/A            0                   PM
               Plan
2.1.1.1. Milestone and Schedule Approved by Project Sponsors
                                                                                                            N/A
3. Phase        Execute – Definition of the required work activities to define, construct, pilot, and
                implement the product scope or selected system functions.
                                                                                                            N/A
3.1. Activity   WBS Definition

3.1.1. Task     JAD Session to create WBS

3.1.2. Task     Compile and review draft WBS

3.1.3. Task     Modify draft WBS

3.1.4. Task     Obtain approval of WBS
                                                                                                            N/A            0
               WBS
3.1.4.1. Milestone documented, agreed and approved
                                                                                                            N/A
3.2. Activity   Execute WBS


     C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc        Page 8
     Last printed 9/21/2011 10:29:00 AM
                                 MMIS Web Technology Requirements Integrated Project Plan

                                                                                                         Del Name & #   Dur.   Critically   Skill
#               WBS Dictionary                                                                                          Est.   Depend


3.2.1. Task     Survey regarding future web system development

3.2.2. Task     Review High Level Analysis and Design document with Sponsors

3.2.3. Task

3.2.4. Task

3.2.5. Task     Resource needs
                                                                                                         N/A
4. Phase        Controls – Administer and manage work controls to ensure project performance.
                                                                                                         N/A
5. Phase        Close – Evaluate the project’s achievement of scope, objectives, and measurements.
                Identify the maintenance plan, turnover to maintenance, and release project resources.
                                                                                                         N/A
5.1. Activity   Project Evaluation – Recognize the achievements and lessons learned of the
                project, and determine readiness to close the project.
                                                                                                         Project                            PM
5.1.1. Task     Prepare a project evaluation – Review the project’s completion criteria, scope, Evaluation
                objectives, measurements, and lessons learned. Identify all items or components, and
                their 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 turnover. Identify maintenance staff and any associated budgets. Meet
                with maintenance lead and review this information.
                                                                                                         N/A            0
               Project successfully closed
5.1.1.1. Milestone




     C:\Docstoc\Working\pdf\255f1ae3-b59b-448b-8f05-6a361d1112a7.doc       Page 9
     Last printed 9/21/2011 10:29:00 AM

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:12
posted:9/21/2011
language:English
pages:13
Description: Web Development Project Cost document sample