SECTION I PROJECT SUMMARY (TRW)
|
|
|
- Elwin Payne
- 9 years ago
- Views:
Transcription
1 SECTION I PROJECT SUMMARY (TRW) Table I Summary Agency/Department Information TRW Information Executive Sponsor: Cynthia Lorenzo Received Date: Managers: Ron McCranie/Andy Loveland Status Meeting Date: Director: Tom McCullion TRW Analyst: Answer the following questions based on the last submitted Operational Work Plan. YES NO Is the project currently on schedule? YES Do you expect the project to complete on schedule? YES Are there any scope changes? NO Are there any risks or issues that the agency is not successfully managing? NO Is the project currently within budget? YES Do you expect the project to remain within budget? YES 1) If the project is not on schedule, briefly explain why and what the agency is doing to bring the project back on schedule. 2) If the project is not on budget, briefly explain why you do not expect the project to remain within budget and what the agency can do, if anything, to bring the project back within budget. 3) Briefly summarize the impact of any necessary scope changes identified in Section II-D of this report. None
2 SECTION II PROJECT PROGRESS A. Milestones & Deliverables Accepted or in Progress this Reporting Period From the last submitted Operational Work Plan (OWP), list in the following table the major milestones and deliverables that are in progress, accepted, or scheduled for acceptance during this reporting period and the next. Also list major milestones and deliverables that occurred but were not scheduled in the OWP during the reporting period. Identify the status of each line item and explain any actual or anticipated variance greater than 5% in planned vs. actual dates. Table II-A Milestones & Deliverables this Reporting Period Planned Actual Major Deliverable/Milestone & Description Planned Acceptance Acceptance Start Date Date Date Future State Business Process Analysis & Documentation 10/23/09 12/22/09 Use Case Development 12/11/09 3/5/10 Requirements Development 1/22/10 3/26/10 Status/Variance Explanation/Comment B. Major Tasks & Activities Accepted or in Progress this Reporting Period From the last submitted OWP, list in the following table the tasks and activities from the project s work breakdown structure that are in progress, accepted or scheduled for acceptance during this reporting period. Explain any actual or anticipated variance greater than 5% in planned vs. actual dates. Table II-B Major Tasks & Activities this Reporting Period Task/Activity Item & Description Planned Start Date Planned Acceptance Date Actual Acceptance Date Future State Business Process Improvement Interviews 10/23/09 12/14/09 1/7/10 Compile Future State Business Process Documentation 12/4/09 12/22/09 Conduct Use Case Interviews 12/17/09 1/22/10 Conduct Use Case Workshops 1/22/10 2/3/10 Status/Variance Explanation/Comment None C. Reports & System Interfaces Accepted or in Progress this Reporting Period From the last submitted OWP, list in the following table the reports and system interfaces that are in progress, accepted or scheduled for acceptance within this reporting period. Indicate whether each item meets federal, state, or local reporting requirements. Explain any actual or anticipated variance greater than 5% in planned vs. actual dates. Report/System Interface & Description Table II-C Reports & System Interfaces this Reporting Period Planned Actual Planned Acceptance Acceptance Start Date Date Date Status/Variance Explanation/Comment TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 2 of 10
3 D. Scope Changes Identified this Reporting Period List in the following table any changes from the original project objectives and deliverables that impact the project schedule or budget. Items listed should be all scope changes identified during this reporting period, including those that may impact the project in later reporting periods. Scope Change Description Include Workforce Services, Workforce Florida and Workforce Board in requirements Table II-D Scope Changes this Reporting Period Cost Impact Schedule Impact Schedule Yes/No Cost Yes/No Change Explanation of Need and Cost/Schedule Change Impact Yes $36,000 Unknown Unknown Completing a high-level requirements analysis with representatives of the Workforce entities. SECTION III PROJECT ISSUES An issue is an immediate problem that requires resolution or an important, unanswered question related to the project. Issues can roll in/out as they arise and are dealt with by the project team. Issues can be operational, functional, or technical in nature (e.g. user satisfaction/buy-in, process change requirements, training attendance, reporting, deployment, and staff acquisition), and may impact the project s timeline, resources, and/or quality of deliverables. Unlike a risk, the project team can usually resolve an issue. Issues this Reporting Period List in the following table any problems requiring immediate resolution. Items listed should include all open issues and those resolved within this reporting period, as well as issues identified during this reporting period, including those that may impact the project in later reporting periods. Issue Description Table III Issues Status (Open/ Closed) Impact Resolution Approach Resolution Date Owner TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 3 of 10
4 SECTION IV PROJECT RISKS Risks are factors that may cause a failure to meet the project s objectives. Risks usually relate to future events which may not be under the control of the project team and usually cannot be eliminated. Major risks must be mitigated throughout the project lifecycle. Examples of risks include statutory changes, stakeholder resistance, budget reduction, project size/complexity, project duration, project cost, process change requirements, and contractor reliance. Risks this Reporting Period List in the following table any factors that may cause a failure to meet the project s objectives. Items listed should include all risks recurring within this reporting period, as well as all risks identified during this reporting period. Risk Description 11) Due to the current UC workload, subject matter experts will be dedicated 50% or less to the project 12) The Agency does not have the necessary knowledge, skills and abilities to staff the project team with in-house resources Have secured the services of an experienced systems and business process analysis vendor (North Highland) and a seasoned Director. Currently working to bring on a qualified IV&V vendor (Contract awarded to E&Y with a target start date of January4, Table IV Risks Probability Risk of Tolerance Occurrence Level Mitigation Strategy High Medium managers and analysts will be as flexible as possible when scheduling meetings or JAD sessions. Ongoing All project meetings and JAD sessions will have clear and documented objectives, and should include only SMEs that are required to achieve those objectives. Complete Adequate time will be provided for the review and approval of project deliverables. Complete All training and testing activities involving SMEs will be thoroughly planned and efficiently executed. Complete Executive Management will regularly acknowledge SMEs for their contributions to the project. Complete Medium Low The Agency will use the state s competitive procurement process to engage qualified and reputable vendors who are able to provide the necessary knowledge, skills and abilities. In process Mitigation Status Open Open Owner Director; Phase 2 Vendor Manager; Executive Mgmt Director; Sponsor TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 4 of 10
5 Risk Description 13) Inadequate project management and oversight could result in project time and cost overruns Table IV Risks Probability Risk of Tolerance Occurrence Level Mitigation Strategy Medium Low An experienced, full-time Manager will be assigned to the project. Complete A Management Office will be established for the duration of the project to ensure industry best practices in project management or employed. Complete Additional project oversight will include IV&V, Quality Assurance, and an Executive Steering Committee. In process (IV&V) Mitigation Status Open Owner Director; Phase 2 Vendor Manager Well defined Risk Mitigation strategies will be developed for all identified project risks. Complete All project plans, risks and issues will be continuously reviewed and refined as the project progresses. In process The project schedule will include multiple checks and balances to ensure the project is meeting expectations and allocated timelines. In process The potential for cost overruns will be minimized by executing stringent change control and scope management practices. Complete 16) Product selected to meet UC functional requirements conflicts with IT and/or SSRC architectural standards. Medium Medium Ensure that the non-functional requirements of the ITN incorporate the IT and SSRC architectural standards. In process Open Director; Phase 2 Vendor Manager TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 5 of 10
6 SECTION V PROJECT SPENDING PLAN The project spending plan portion of the status report consists of this section and an Excel worksheet. After first updating the Excel project spending plan, complete this section based on the worksheet. Also provide the same information planned for the next reporting period. A. Discuss the major project costs incurred by the project for this reporting period. Ongoing Management Services B. Identify the major project costs planned for the next reporting period. Ongoing Management Services Workforce Strategy Planning and Requirements IV&V C. Specify planned project costs vs. actual project costs based on the last submitted OWP. For the major categories, provide the following information: 1. Staffing i. State FTE positions: (5) Re-engineering Staff (not included in project cost) Planned: $33,000 Actual: $33,000 ii. OPS positions: None iii. Contractor positions: This Period: (8) North Highland Deliverables based costing Next Period: 2. Deliverables i. This period: None. ii. Next Period: None. 3. Major Tasks from a funding perspective. 4. Hardware 5. COTS Software 6. Miscellaneous Equipment 7. Other major project costs 8. Progress payments (1) Information Systems of Florida ( Director) Planned: $24,800 Actual: $28,908 (7) North Highland Deliverables based costing (1) North Highland Workforce Strategy Planned: $21,600 (1) Ernst & Young IV&V Planned: $24,487 (1) Information Systems of Florida ( Director) Planned: $24,800 TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 6 of 10
7 SECTION V PROJECT SPENDING PLAN D. Indicate the budget vs. actual costs and variance up to and including the reporting period. Discuss any variance from the submitted spending plan in the OWP. Forecast: $149,518 Actual: $148,976 Variance: $543 No significant variance to plan. E. Indicate the specific appropriation amount and discuss any variance between the submitted spending plan and the appropriation. $2M appropriated for this phase. No variance to plan. TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 7 of 10
8 SECTION VI PROJECT OVERVIEW This section should provide concise background information (one page or less) regarding the project to a reader of this report who may not be familiar with the project. This information should be similar to what the agency provided in the project charter section of the last submitted OWP, unless scope changes have modified the project s objectives and deliverables since the last submitted OWP. If the project charter has changed since the last submitted OWP, identify the changes and provide the latest project charter. A. Scope Statement The scope of this project will include a significant business process analysis and requirements development effort as well as the design, development, testing, user training and state-wide implementation of a new business system that supports the following UC functions: Claims and Adjudications Customer Support Benefit Operations, including: o Wage Determinations o Special Payments o Employer Charges o Special Programs Benefit Payment Control UC Reengineering UC Appeals Quality Improvement and Federal Reporting The project scope will include development of the following customized interfaces: Online claimant portal Online employer portal Workforce services interface Also Included in the Scope Establishment of a Management Office Organizational Change Management Independent Verification and Validation (IV&V) Data conversion and migration Data warehouse design and development Statewide system implementation Content development for training materials and system help screens End-user training Operations and maintenance planning Reporting functions TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 8 of 10
9 SECTION VI PROJECT OVERVIEW B. Business Objectives Business Objective #1 Create flexible, integrated UC applications, information, and business processes for UC Benefits and Appeals in order to create operational efficiencies. Business Objective #2 Provide a consolidated system with user-friendly search criteria to provide internal and external stakeholders, partners, and the general public with easily accessible, secured and on demand access to claims data. Business Objective #3 Provide a system that is fully compliant with Federal and State laws and statutes as well as Agency procedures and rules. Business Objective #4 Provide a state-of-the-art technology system architecture that will effectively support the dynamic application processes and modifications required because of legislative changes and Agency needs. C. Critical Success Factors a. Benefits to the State: Comply with all requirements established in federal and state law for unemployment compensation. Integrate with the Department of Revenue s statewide unified tax system that collects unemployment compensation taxes. Cost savings from reduced call volume, fewer non-monetary determinations and a reduced number of appeals if the new system creates efficiency gains similar to what other states have experienced (15%). Reduced benefit overpayments if the new system facilitates the rate of improvement in overpayment reduction of 15% following the introduction of the new benefits system. Additional interest revenue due to reduced UC Trust Fund disbursements if the new system creates the projected efficiencies and improvements observed elsewhere. b. Benefits to the Agency: Wherever cost-effective and operationally feasible, eliminate or automate existing paper processes and enhance any existing automated workflows in order to expedite customer transactions and eliminate redundancy. Integrate benefit payment control with the adjudication program and collection system in order to improve the detection of fraud. Reduced UC Trust Fund disbursements by reallocating resources away from low value, high volume processing tasks to high value administrative tasks such as eligibility reviews that can contribute to shortened claim length. Reduced UC Trust Fund disbursements through the automation of low value, high volume processing tasks to high value tasks. c. Benefits to the Public: Enable on-line, self-service access to claimant and employer information and federal and state reporting. Reduced claim durations through greater integration with the Workforce Program and an emphasis on re-employment activities such as claimant profiling. TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 9 of 10
10 SECTION VI PROJECT OVERVIEW D. Key Dates September 15, 2009 Operational Work Plan - Complete November 18, 2009 RFI Complete - Complete November 23, 2009 Current State Business Process Document - Complete January 25, 2010 Start of IV&V Vendor (E&Y) January 26, 2009 Future State Business Process Document March 5, 2010 Update to TRW if any Major Variance(s) from the Schedule IV-B March 26, 2010 Use Cases April 23, 2010 Conceptual Data Model/High Level System Components April 23, 2010 Functional and Non-Functional Requirements April 30, 2010 Update Schedule IV-B May 7, 2010 Close-out Upcoming Target Dates May 1, 2010 October 1, 2010 Invitation To Negotiate (ITN) Released Phase 3 Start TRW Status Report, Template Version 2.0 Last Printed 1/19/2010 6:00 PM Page 10 of 10
SECTION I PROJECT SUMMARY (TRW)
AS OF OCTOBER 11, 2010 SECTION I PROJECT SUMMARY (TRW) Table I Project Summary Agency/Department Information TRW Information Executive Sponsor: Cynthia Lorenzo Received Date: Project Director: Tom McCullion
ID Task Name Time Pred
0 UC Modernization Project Plan 1115 d 1 1 Phase I - Business Case Development and Competitive Procurement 205 d 2 1.1 Complete Initial Feasibility Study 55 d 3 1.2 Prepare and Issue LBR 30 d 2 4 1.3 Competitive
Information Technology Project Oversight Framework
i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11
Project Knowledge Areas
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
Understand why, when and how-to to formally close a project
Project Closure Purpose: Understand why, when and how-to to formally close a project Audience: Project managers, project sponsors, team members and other key stakeholders Learning Objectives: Describe
Appeals Case Management System Project. Scope Management Plan. November 20, 2014
Appeals Case Management System Project Version 1.0 Health and Human Services Agency, Office of Systems Integration Template Revision History REVISION HISTORY REVISION # DATE OF RELEASE OWNER SUMMARY OF
Development, Acquisition, Implementation, and Maintenance of Application Systems
Development, Acquisition, Implementation, and Maintenance of Application Systems Part of a series of notes to help Centers review their own Center internal management processes from the point of view of
Program Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
A Guide To The Project Management Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition
A Guide To The Project Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition Major Changes The adoption of the verb-noun format for process names Amplification as to Enterprise
How To Write A Project Management Plan
Enter Project Name Project Management Plan (PMP) Kickoff Month, Day, Year 1 Purpose The Project Management Plan (PMP) is a formal, approved document used to manage project execution. The PMP documents
Request for Proposal for Application Development and Maintenance Services for XML Store platforms
Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview...
Introduction to the ITS Project Management Methodology
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects
State of Arkansas Office of Information Technology 124 W. Capitol Ave. Suite 990 Little Rock, AR 72201 501.682.4300 Voice 501.682.4020 Fax http://www.cio.arkansas.gov/techarch Best Practices Statement
HRMS - HRMS Charter - AI.18. Project Charter Human Resource Management System (HRMS) Replacement - Implementation Project Number: 2209.
Project Charter Human Resource Management System (HRMS) Replacement - Implementation Project Number: 2209 Final Version: 1.0 Date: June 5, 2012 Distribution List: Name Dan Guimond MaryAnn Kempe Heather
System/Data Requirements Definition Analysis and Design
EXECUTIVE SUMMARY This document provides an overview of the Systems Development Life-Cycle (SDLC) process of the U.S. House of Representatives. The SDLC process consists of seven tailored phases that help
CONNECTICUT HOUSING FINANCE AUTHORITY REQUEST FOR PROPOSAL FOR Development of Strategic Information Technology Plan
Overview The Connecticut Housing Finance Authority (CHFA) was created in 1969 as a public instrumentality by the State Legislature. As a quasi-public agency and political subdivision of the State of Connecticut,
STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840
MARYLAND STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840 Bobbie S. Mack, Chairman David J. McManus, Jr., Vice Chairman Rachel T. McGuckian Patrick H. Murray Charles
September 2005 Report No. 06-009
An Audit Report on The Health and Human Services Commission s Consolidation of Administrative Support Functions Report No. 06-009 John Keel, CPA State Auditor An Audit Report on The Health and Human Services
Analysis Item 65: Department of Revenue Property Valuation System
Analysis Item 65: Department of Revenue Property Valuation System Analysts: John Borden and Sean McSpaden Request: Allocate $1.5 million from the Emergency Fund for an increase to the Property Valuation
Project Team Roles Adapted for PAAMCO
Project Team Roles Adapted for PAAMCO Project Roles, Authority & Responsibilities Role a defined funciton assumed by or assigned to a person in the project Authority the right to apply project resources,
Financial and Cash Management Task Force. Strategic Business Plan
Financial and Cash Management Task Force January 30, 2009 Table Of Contents 1 Executive Summary... 4 2 Introduction... 6 2.1 External Reports on Project Aspire... 7 2.1.1 Council on Efficient Government
INFORMATION TECHNOLOGY PROJECT REQUESTS
INFORMATION TECHNOLOGY PROJECT REQUESTS Guidelines & Instructions for Maryland State Agencies Revised Two Step PPR/PIR Approval Process Fiscal Year 2013 Table of Contents Part 1: Overview... 2 1.1 Introduction...
VA ICJIS. Program Management Plan
VA ICJIS Program Management Plan 1 08/29/01 Program Management Plan VA Integrated Criminal Justice Information System (ICJIS) Program 1. Introduction. The Commonwealth of Virginia Integrated Criminal Justice
Information Technology Governance Overview and Charter
Information Technology Governance Overview and Charter Prepared by: Project #: Date submitted Document version: IT Governance Charter v03.05.2012 1.0 48.0 - Page 1 of 34 Document History Version Date Author
PHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
Software Development Risk Assessment
Software Development Risk Assessment Note: The purpose of this prompt list is to provide project managers with a tool for identifying and planning for potential project risks. It is process-based and supports
PHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
IT Project Management Practices Guide
IT Project Management Practices Guide Introduction The IT Project Management Practices Guide (Guide) contains a repeatable, institutionwide approach for the management of application development and/or
- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021
- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021 About this document this is a detailed description of typical Project Manager (PM) duties, responsibilities, and
MNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview
Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview 1/1 Table of Contents 1. Introduction...3 2. Executive Summary...4 3. Program Definition...5 3.1. Program
PROJECT MANAGEMENT PLAN <PROJECT NAME>
PROJECT MANAGEMENT PLAN TEMPLATE This Project Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
PMP Examination Tasks Puzzle game
PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in
ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES
1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through
Crosswalk Between Current and New PMP Task Classifications
Crosswalk Between Current and New PMP Task Classifications Domain 01 Initiating the Project Conduct project selection methods (e.g., cost benefit analysis, selection criteria) through meetings with the
CHAPTER 3: MANAGING IMPLEMENTATION PROJECTS
Chapter 3: Managing Implementation Projects CHAPTER 3: MANAGING IMPLEMENTATION PROJECTS Objectives Introduction The objectives are: Describe common problems that occur in implementation projects. Describe
<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
Department of Administration Portfolio Management System 1.3 June 30, 2010
E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2
HHS OCIO Policy for Information Technology (IT) Enterprise Performance Life Cycle (EPLC)
Office of the Chief Information Officer Office of the Assistant Secretary for Resources and Technology Department of Health and Human Services HHS OCIO Policy for Information Technology (IT) Enterprise
Draft Document STATE OF MICHIGAN. SACWIS Planning Department of Human Services Strategic Implementation Plan: Project Staffing
STATE OF MICHIGAN SACWIS Planning Department of Human Services Strategic Implementation Plan: Project Staffing Executive Summary The State of Michigan has dedicated integrated team of resources for the
ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
State of Oregon. State of Oregon 1
State of Oregon State of Oregon 1 Table of Contents 1. Introduction...1 2. Information Asset Management...2 3. Communication Operations...7 3.3 Workstation Management... 7 3.9 Log management... 11 4. Information
Systems Engineering Process
Systems Engineering Process Derek Vollmer, P.E. ITS Software and Architecture Coordinator Traffic Engineering and Operations Office Contents Federal regulations for ITS projects Overview of systems engineering
Blueprint for Selecting Improvement Approach
Kenan-Flagler Business School State of North Carolina Business Systems Infrastructure Study Phase II Blueprint for Selecting Improvement Approach Executive Summary January 5, 2004 Business Case www.osc.state.nc.us
Submitted by: Christopher Mead, Director, Department of Information Technology
Office of the City Manager INFORMATION CALENDAR March 21, 2006 To: From: Honorable Mayor and Members of the City Council Phil Kamlarz, City Manager Submitted by: Christopher Mead, Director, Department
ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 5 PROJECT CLOSEOUT PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 5 PROJECT CLOSEOUT PHASE Table of Contents Introduction... 3 Project Closeout Phase... 3 Activities and Documents in the Closeout Phase... 4 Project Closeout Task...
CARLETON UNIVERSITY POSITION DESCRIPTION. Position Title: Manager, HR Systems Position No.: 298879. Approved by:
CARLETON UNIVERSITY POSITION DESCRIPTION Position Title: Manager, HR Systems Position No.: 298879 Reports to: Department: Assistant Director HR, Talent Programs Human Resources Approved by: (Incumbent/Date)
Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs
HUMAN RESOURCE MANAGEMENT Organizational planning Staff Acquisition Project interfaces such as organizational interfaces, technical interfaces and interpersonal interfaces. Staffing requirements Staffing
Dallas IIA Chapter / ISACA N. Texas Chapter. January 7, 2010
Dallas IIA Chapter / ISACA N. Texas Chapter Auditing Tuesday, October Project 20, 2009 Management Controls January 7, 2010 Table of Contents Contents Page # Project Management Office Overview 3 Aligning
NASCIO EA Development Tool-Kit Solution Architecture. Version 3.0
NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5
Prepared for: Prepared by:
Executive Project Review Prepared for: Prepared by: Table of contents Introduction... 3 WHY an Executive Project Review?... 3 WHO is Involved?... 4 WHAT is an Executive Project Review?... 5 WHEN? - Schedule
The Florida Community College Software Development Program
This paper was presented at the 1995 CAUSE annual conference. It is part of the proceedings of that conference, "Realizing the Potential of Information Resources: Information, Technology, and Services--
PHASE 8: IMPLEMENTATION PHASE
PHASE 8: IMPLEMENTATION PHASE The Implementation Phase has one key activity: deploying the new system in its target environment. Supporting actions include training end-users and preparing to turn the
2003 Patricia Ensworth Page 1
1 1 Sample software development project 2 1.1 Start project 3 1.2 Initiation phase 4 1.2.1 Develop project charter 5 1.2.2 Project charter approved 6 1.3 Planning phase 7 1.3.1 Product activities 8 1.3.1.1
Streamline your staffing process with a vendor management system that fits your business
Peopleclick VMS Streamline your staffing process with a vendor management system that fits your business Peopleclick VMS is web-based, enterprise-wide vendor management software that automates, tracks
Project Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
Project and Portfolio Management Software Provider Request for Information
State of Florida Department of Revenue ISP Request for FDOR PPM Tool RFI #14/15 05 Reissued 1. Introduction The Florida Department of Revenue (the Department or FDOR ), hereby issues this Request for (
Oversight of Information Technology Projects. Information Technology Audit
O L A OFFICE OF THE LEGISLATIVE AUDITOR STATE OF MINNESOTA FINANCIAL AUDIT DIVISION REPORT Oversight of Information Technology Projects Information Technology Audit May 29, 2009 Report 09-19 FINANCIAL
Project Management Professional (PMP) Examination Content Outline
Project Management Professional (PMP) Examination Content Outline Project Management Institute Project Management Professional (PMP ) Examination Content Outline Revised August 2011 Published by: Project
Managing Successful Software Development Projects Mike Thibado 12/28/05
Managing Successful Software Development Projects Mike Thibado 12/28/05 Copyright 2006, Ambient Consulting Table of Contents EXECUTIVE OVERVIEW...3 STATEMENT OF WORK DOCUMENT...4 REQUIREMENTS CHANGE PROCEDURE...5
PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:
PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History
CITY OF SAN MATEO, CALIFORNIA
1 Background The City of San Mateo, CA, a full-service city with a population of approximately 97,207, is soliciting for professional project management services related to the City s Permitting and Project
Performance Audit Concurrent Review: ERP Pre-Solicitation
Performance Audit Concurrent Review: ERP Pre-Solicitation April 2002 City Auditor s Office City of Kansas City, Missouri 24-2001 April 10, 2002 Honorable Mayor and Members of the City Council: We conducted
Information Technology Project Oversight Framework
State of California California Technology Agency Information Technology Project Oversight Framework SIMM Section 45 Revised April 2011 This Page Intentionally Left Blank California Technology Agency Table
Template for FY16 Agency IT Plan
OVERALL AGENCY IT PLAN GUIDELINES: I. Top Five IT Goals Identify your agency s top five goals/objectives for utilizing information technology in FY16, and how they serve your agency s business needs. This
Enterprise Performance Life Cycle Management. Guideline
Enterprise Performance Life Cycle Management Guideline Version 2.1 PREPARED BY THE ENTERPRISE PROGRAM MANAGEMENT OFFICE MAY 2011 Table of Contents Document Control...i 1. Introduction... 2 1.1 Purpose...
ACC PRIMER Legal Project Management
By in-house counsel, for in-house counsel. OCTOBER 2011 ACC PRIMER Legal Project Management Association of Corporate Counsel 1025 Connecticut Avenue, NW, Suite 200 Washington, DC 20036 USA tel +1 202.293.4103,
IT Project Management Methodology. Project Execution Support Guide. Version 0.3
NATIONAL INFORMATION TECHNOLOGY AUTHORITY - UGANDA IT Project Management Methodology Project Execution Support Guide Version 0.3 Table of Contents 1 INTRODUCTION... 4 1.1 When should Project Execution
THE PROJECT MANAGEMENT KNOWLEDGE AREAS
THE PROJECT MANAGEMENT KNOWLEDGE AREAS 4. Project Integration Management 5. Project Scope Management 6. Project Time Management 7. Project Cost Management 8. Project Quality Management 9. Project Human
Department of Highway Safety & Motor Vehicles Motorist Modernization Project Phase One
Motorist Modernization Project Phase One For Period: April - June 2015 Project Description Quarter Ending: 6/30/2015 Agency Name: Department of Highway Safety & Motor Vehicles (HSMV) Project Name: Motorist
KMS Implementation Roadmap
KMS Implementation Roadmap Sample Excerpt Prepared by: The Knowledge Compass, Inc. TABLE OF CONTENTS 1. EXECUTIVE SUMMARY 5 1.1 Overview 5 1.2 Project Goals & Objectives 5 1.3 Implementation Approach 5
Migration Planning Guidance (Draft)
Financial Management Line of Business Migration Planning Guidance (Draft) Section 1.1 Overview The purpose of the Migration Planning Guidance document is to help agencies prepare for, and manage, a migration
Positive Train Control (PTC) Program Management Plan
Positive Train Control (PTC) Program Management Plan Proposed Framework This document is considered an uncontrolled copy unless it is viewed online in the organization s Program Management Information
ACQUISITION OF SOFTWARE AND SERVICES TO SUPPORT THE CORPORATE HUMAN RESOURCES INFORMATION SYSTEM
ACQUISITION OF SOFTWARE AND SERVICES TO SUPPORT THE CORPORATE HUMAN RESOURCES INFORMATION SYSTEM Audit Report No. 00-011 March 30, 2000 OFFICE OF AUDITS OFFICE OF INSPECTOR GENERAL Federal Deposit Insurance
Project Governance Plan Next Generation 9-1-1 Project Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1)
Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1) Date: October 1, 2014 Version: 3.1 DOCUMENT REVISION HISTORY Version Date Changes Updated By 0.1 02/13/014 Initial
Fixed Scope Offering for Oracle Fusion HCM. Slide 1
Fixed Scope Offering for Oracle Fusion HCM Slide 1 Today s Business Challenges Adopt leading Global HCM practices. Streamline the HCM processes and achieve measurable efficiencies. Achieve HR excellence
Final. North Carolina Procurement Transformation. Governance Model March 11, 2011
North Carolina Procurement Transformation Governance Model March 11, 2011 Executive Summary Design Approach Process Governance Model Overview Recommended Governance Structure Recommended Governance Processes
Project Management Methodology
Project Management Methodology 1/6/2015 PAGE 1 OF 28 Version 2.0 Contents INTRODUCTION... 4 1. Overview... 4 PHASE 1 PROJECT INITIATION... 5 1. Governance Model... 6 2. Project Prioritization Process...
Arkansas State Unified Plan Workforce Investment Act of 1998. M. Corrective Action. 1. Corrective Actions
M. Corrective Action 1. Corrective Actions [Federal Planning Guidance: Describe the corrective actions the State will take for each program, as applicable, if performance falls short of expectations.]
CDC UNIFIED PROCESS PRACTICES GUIDE
Purpose The purpose of this document is to provide guidance on the practice called Project Close-Out and to describe the practice overview, requirements, best practices, activities, and key terms related
Develop Project Charter. Develop Project Management Plan
Develop Charter Develop Charter is the process of developing documentation that formally authorizes a project or a phase. The documentation includes initial requirements that satisfy stakeholder needs
Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:
Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute
Auditing Capital Projects and Project Controls. March 2013
Auditing Capital Projects and Project Controls March 2013 Internal Audit Perspective Oversight Insight Foresight Is the process operating as planned? Are controls, resources, and performance measures adequate
Update on Information Technology Strategic Plan
Florida Department of TRANSPORTATION Update on Information Technology Strategic Plan April Blackburn Office of Information Systems August 19, 2015 IT Strategic Plan Overview FDOT undertook an initiative
LGS Project Management Methodology
Page: 32 LGS Project Management Methodoy The LGS project management methodoy is integral to our overall delivery methodoy. Based on inpro, one of the LGS inspiration series documents, our methodoy is compliant
How To Write An Slcm Project Plan
SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) Project Development Phases Pension Benefit Guaranty Corporation s (PBGC) System Life Cycle Methodology (SLCM) is comprised of five project development
Project Management Plan for
Project Management Plan for [Project ID] Prepared by: Date: [Name], Project Manager Approved by: Date: [Name], Project Sponsor Approved by: Date: [Name], Executive Manager Table of Contents Project Summary...
