Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

THIS IS A DRAFT AND A WORK IN PROGRESS.  ALL COMMENTS ARE APPRECIATED.

true
Section
border

Overview

Column
width30%
Include Page
public:OIT Project Left Navigation Panepublic:OIT Project Left Navigation Pane
Column
width5%
Column
width75%
78%

Once a project is initiated and a project manager is assigned, detailed planning, analysis and requirement definition should occur for a project.  OIT uses a comprehensive Software Development Life Cycle that ensures project implementation follows industry best practices and requirements definition can begin. While OIT teams generally manage projects in a way appropriate to the structure of the team and the nature of the work being performed, all teams are encouraged to follow consistent processes and industry best practices to ensure that projects are implemented consistently and include appropriate quality controls.  A deliverable  Deliverables of the planning phase will be include a requirements document and project plan including a task timeline, resource assignment, and effort estimation. It is required that the project sponsor and any other organizations committing resources review and approve this plan . Projects proceed before a project is allowed to proceed to the development or implementation phase after this agreement is received.

Once this detailed plan is complete, the project will be baselined for budgeted hours and timeline. This baseline information will be tracked against for project performance and will be the basis for computing project metrics.  For smaller projects, where a detailed project plan may not be required, at a minimum, the information for the budget and timeline must be completed on the Project Status Document.

Smaller projects, usually defined as those that can be implemented within a 9 month timeframe and with 2 programmer FTEs,  are usually reviewed and managed within the internal, OIT Review Committee.    Projects that are of a larger scope, more complex, or require significant budgets or FTEs, are escalated for review and monitoring by the OIT Oversight Committee.

Projects that undergo significant scope creep or requirements changes may need to re-reviewed. If there is a documented and approved change in scope or approved change in timeline, the project may be rebaselined with the approval of the OIT Oversight Committee. The OIT Oversight Committee must approve any material change in scope for an approved project. A material change in scope is defined as a 25% change in project duration or a 10% change in resource requirements.

Proposal and Project Monitoring

Approved, In Progress Projects

For projects in progress, the following will trigger a review:

  • Dollar cost exceeds 110% of baseline budget.
  • Effort in hours exceeds 110% of baseline budget
  • Project duration exceeds 125% of baseline budget
Approved, To Be Scheduled Projects
  • During the quarterly prioritization and scheduling process, any proposals that have been approved but are not scheduled to execute in the next twelve months are returned to OIT Oversight Committee for further review.
Submitted, Under Review Proposals
  • Project proposals will be accepted into the process once completed proposal information, with estimates, is received.

Projects exceeding any of the above thresholds as reported on the project status summary report, with more than 30 days left until project completion, will be reviewed by the OIT Oversight Committee at their next meeting. The OIT Oversight Committee may suspend any projects not proceeding satisfactorily at its discretion.

Section

.

OIT has developed a Unified Project Framework that is flexible enough that it can be used for most IT projects. Teams with no specific framework in place are encouraged to use the framework with whatever adaptations are required to make it better fit their requirements.

Column
width2%
 
Column
width20%
Include Page
OIT Project Navigation Pane
OIT Project Navigation Pane