APPO Project Phase I Kick-Off July 24, 2002

Slides:



Advertisements
Similar presentations
MIGRATION MIGR-09. How to Run Your Next Implementation... Don't Let It Run You! Patricia Johnson Senior Systems Consultant Strategic Systems Group, Inc.
Advertisements

The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
Roadmap for Sourcing Decision Review Board (DRB)
Project Kick-off Meeting > > Presented By: > >
DEVELOPING A TECHNOLOGY PROJECT IN STUDENT AFFAIRS A Guide to the Process Paul Schantz November, 2010.
Financial Systems Needs Assessment Project Update Monthly Research Administrators Meeting March 11, 2010.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
Project Kick-off 14-Jan-09.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
Oct. 30, 2003CS WPI1 CS 509 Design of Software Systems Lecture #9 Thursday, Oct. 30, 2003.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Project Execution.
Office of Information Technology (OIT) PROJECT INITIATION DOCUMENTS - BUSINESS CASE, ALTERNATIVE ANALYSIS AND STATEMENT OF WORK (SOW)
ADMINISTRATIVE SYSTEMS Information Session April 23, 2013.
Advanced Project Management Project Plan Templates
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Financials – Phase II Kick-Off Meeting September 11, 2008 Brenda Bolander, State Comptroller Michael Grisser, Project Manager.
Project Management Process Overview
S/W Project Management
PMP® Exam Preparation Course
OSF/ISD Project Portfolio Management Framework January 17, 2011.
Lessons Learned – Keys to a Successful Implementation Atlanta OAUG January 21, 2005 Atlanta, Georgia.
SPLIT Campus Solutions & Human Capital Management UPGRADE Financials & Human Capital Management & Portal Kickoff May 13, 2014.
Grants Information System Project Notes for Presentation to CAST February 27 th, 2004 Steve Hahn, Director Office of Information Technology The Graduate.
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
ADMINISTRATIVE SYSTEMS Information Session Tuesday, March 26, 2013.
Executive Steering Committee Presentation
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
IT Requirements Management Balancing Needs and Expectations.
SacProNet An Overview of Project Management Techniques.
Office of Process Simplification May 20, 2009 Planning an Improvement Project.
TEXAS NODAL Board of Directors Austin, Texas July 15, 2003.
Managing the Information Systems Project © Abdou Illia MIS Spring /26/2015.
Community Board Orientation 6- Community Board Orientation 6-1.
Fleming College Quality and Risk Management Review Summary February 2, 2006.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
ABOUT MARINO ASSOCIATES Full Service Business Consulting and Education Firm In Third Decade of Business Some Clients ; AT&T, Eastman Kodak, Canbera, Arris,
Introducing Project Management Update December 2011.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Validate Scope What we have: Requirement Traceability Matrix Verified Deliverables What we do: Inspection What we get: Accepted Deliverables.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
1 Program Release 2008 Update to the Administrative Council August 9, 2007.
Project Management Skills For Life [Insert Date Here] [Insert Instructor Name Here]
Project Organization Chart Roles & Responsibilities Matrix Add Project Name.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
AP Payments to Employees 2012/2013 Sacramento State.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
1 TenStep Project Management Process ™ PM00.5 PM00.5 Project Management Preparation for Success * Manage Scope *
Info-Tech Research Group1 Manage the IT Portfolio World Class Operations - Impact Workshop.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
Project Management ISE 5101 Karl Smith Project Monitoring & Control I Project Meetings.
November 12, 2009 PM Process Improvement Plan: Employee Presentation.
The Committee will: Assess and report on technology resources, status and needs. Create concept papers in support of strategic directions approved by.
For Life™ [Insert Date Here] [Insert Instructor Name Here] Project Management Skills.
Presenter: Igna Visser Date: Wednesday, 18 March 2015
THE VALUE (SUPPLY) CHAIN STRETCHES FROM THE BEGINNING OF YOUR SUPPLIER’S SUPPLY CHAIN THROUGH ALL OF YOUR PROCESSES THAT CREATE VALUE FOR YOUR CUSTOMERS.
Cowlitz County, WA Accounting Function Review
TEXAS NODAL (ERCOT REVISIONS)
Project Kick-Off Meeting
Description of Revision
Ctclink executive leadership committee May 31, 2018
Project Integration Management
{Project Name} Organizational Chart, Roles and Responsibilities
Project Name Here Kick-off Date
Presentation transcript:

APPO Project Phase I Kick-Off July 24, 2002

Agenda Project background Project objectives and team charge Project goals Project scope Deliverables Project organization Project plan Project management approach Team meeting ground rules Next step. APPO Kick Off, July 24, 2002

Project Background Retirement of mainframe Maintenance Cost Evolving Business Needs Shared Financial Systems - SFS Eliminating legacy GL dependency Migrating Legacy Programs/Processes off Mainframe. APPO Kick Off, July 24, 2002

APPO Project Objectives and Team Charge To explore solution alternatives for migrating legacy accounts payable programs/processes off mainframe and to recommend a best accounts payable migration alternative that is technically attainable, financially cost-effective, and functionally feasible and practical. APPO Kick Off, July 24, 2002

APPO Project Objectives Technically Attainable Solutions should be built on technology that currently exists. Financially Cost-Effective Analyze and compare implementation costs and operational costs. Cost-benefit analysis to justify solution alternatives. Functionally Feasible and Practical Chosen technology and solutions should be able to meet majority of business requirements. Solutions should be able to simplify processes, reduce manual touches and reduce current processing cycle time. APPO Kick Off, July 24, 2002

Project Goals Team training of procurement and payable processes. Identify legacy AP process improvement opportunities. Identify potential technology & software. Perform software gap analysis. Identify possible alternatives for legacy AP processes. Analyze alternatives (technical, functional and financial). Solution recommendations. APPO Kick Off, July 24, 2002

Project Scope – Business Scope Major Processes In Scope Encumbrance Direct charge PO invoice payment cycle Pre-Audit Post-Audit Check printing & payment distribution File maintenance and storage. Processes Out of Scope (To be addressed in projects separate from APPO Phase I) Procard transactions SWAP? Property Control? Electronic internal billings within campus Inter campus billings MDS. APPO Kick Off, July 24, 2002

Project Scope – System Scope Legacy Programs In Scope EPRQ VPAM INQV INQC INQR GENR 1099 payments. Legacy Programs Out of Scope (To be addressed in projects separate from APPO Phase I) File Interface with Accrual Accounting Systems Tax-related reporting. QFO2 INQP ADDI APPO Kick Off, July 24, 2002

Project Deliverables Charter (scope, plan, risk assessment, communication plan, project schedules, etc.) Current process model and baseline Future process model and desired measurements Software gap analysis report Final project report and recommendation to the management. APPO Kick Off, July 24, 2002

Project Organization Project Team APPO Kick Off, July 24, 2002

Project Organization SFS Steering Committee John Torphy Don Minor Nancy Wilkinson Pennie Maclean Diane Mann Al Benzschawel SFS Strategic Planning Committee Bob Dye Jim Knickmeyer Ken Mount Diane Barrett Colleen Kerl Jan Richardson Donna Halleran Paul Jelle Pennie Maclean Maggie Roth Mike Hardiman Al Benzschawel Larry Wold Cathy Holmes APPO Team Procurement Accounts Payable SFS Team Campus Representatives APPO Kick Off, July 24, 2002

Project Team Responsibilities Team Members Serve as functional expert in responsible process areas and share expert knowledge with the team. Participate in team meetings & discussions. Learn from other functional experts on the team to gain an understanding of APPO processes. Gather and share process related data for the project. Apply functional expertise and judgment in the development of project deliverables. Participate in the development of project deliverables. APPO Kick Off, July 24, 2002

Project Team Responsibilities Strategic Planning Committee Authorize and approve APPO project. Define project objectives and team charge. Allocate and approve project resources. Approve project deliverables. Resolve project related issues. APPO Kick Off, July 24, 2002

Project Team Responsibilities Steering Committee Authorize and approve APPO project. Approve project objectives and team charge. Approve project budget. Approve project deliverables. Resolve project related issues. APPO Kick Off, July 24, 2002

Project Plan APPO Kick Off, July 24, 2002

Project Management Approach Scope Management Process Project team recommendation of scope change with justifications. Scope change request should be made to SPC for approval. Significant scope change should also be made to Steering Committee for approval. APPO Kick Off, July 24, 2002

Project Management Approach Issue Management Document issues that can have significant impact on the project or that require further clarification or investigation. Prioritize issues. Assign issues to related functional team members for investigation and issue resolution. Track documented issue status. Issue status: Accepted, rejected or resolved. APPO Kick Off, July 24, 2002

Project Management Approach Communication Plan Status report to SPC at each milestone. Regular project briefings with the management team representatives. Issues meeting: Periodic review of issue log by the team. Steering Committee report: Summarized final project report from the team. Regular status report on SFS website. APPO Kick Off, July 24, 2002

Ground Rules for Team Meeting One person speaks at a time. Do not interrupt while someone is speaking. Give other people the opportunity to speak. Think what you are going to say and say it clearly. No side conversations. Focus on issues and opinions, not the person with opinions. Show respect and courtesy to each other. Do not blame or make negative comments about other people. No one person makes decision. All ideas and decisions belong to the team. Don’t be afraid to ask for clarification. Start and stop meetings on time. Make every possible effort to attend team meetings. Check in during team meeting for the next meeting. Take responsibility to catch up with missed meetings. APPO Kick Off, July 24, 2002

Next Step Schedule team meetings – biweekly Develop Charter – Hua Team approval of Charter SFS SPC approval of Charter Team training on business processes – procurement. APPO Kick Off, July 24, 2002