1 / 9

NMSU IT Enterprise Software Project Structure

NMSU IT Enterprise Software Project Structure. Presented by: Pamela Jeffries, Assistant Director ICT Project Management Office. Background. Project Management Office (PMO) created as a department within ICT Enterprise Application Services (EAS)

khansen
Télécharger la présentation

NMSU IT Enterprise Software Project Structure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NMSU IT Enterprise Software Project Structure Presented by:Pamela Jeffries, Assistant Director ICT Project Management Office

  2. Background • Project Management Office (PMO) created as a department within ICT Enterprise Application Services (EAS) • Current Scope – Provide centralized guidance and support of IT Enterprise Software Projects • Key Functions: • Streamline project requests • Foster better prioritization of projects • Manage the project portfolio • Provide project management standards • Perform project management functions

  3. Background (cont’d) • Project Evaluation & Prioritization (PEP) Committee established – Meets every 2 weeks • Primary Functions: • Evaluate project requests • Make decisions on project priorities • Determine impacts on the current project portfolio • Present project impacts to NMSU Executive Level Management and seek resolution on project conflicts

  4. PEP Committee Structure Operational Units

  5. Value Added • Centralized coordination of IT Enterprise Software Projects • Minimize duplication of effort and product purchases • Define common sets of requirements as a University • Early definition of project scope leads to: • Fewer false starts • Fewer out of scope situations • Fewer scope changes

  6. Value Added (cont’d) • PEP Committee is key • Increased client involvement on projects • Increased collaboration between client offices • Increased awareness of overall project priorities • Better Planning = Better Projects

  7. Expected PEP Committee Outcomes • Encourage business needs to be formulated and submitted early on • Better planning and decision making • Improved customer satisfaction • Encourage utilization of the Banner System • System of record • Reduction in data entry • Phase out shadow systems

  8. Expected PEP Committee Outcomes (Cont’d) • Create policy for the evaluation / selection of new software products (i.e. third party vendor packages) • IT / Purchasing engaged early in the process • Business needs defined • Client offices / NMSU needs met • Reduction in cost and resources • Encourage NMSU Executive Level Management involvement in the process • Brief on projects at Vice President meetings as needed • Participate in project conflict resolution as needed

  9. QuestionsPamela Jeffries, Assistant DirectorICT Project Management Office575.646.7224ict_pmo@nmsu.eduMore information:http://pmo.nmsu.edu

More Related