The Project Management Life Cycle (PMLC) is a standard project management methodology used for project planning and implementation at the George Washington University. #PMLC offers a clearly defined process for how to take a project from idea stage through closing, while using project management principles that clarify expectations, streamline communications, and ensure thoroughness in planning and execution.
PMLC was developed in 2009 as a joint effort between GW's Division of Information Technology and Finance Division. Purposed to drive standardization of methodology, documentation, reporting and approval across GW organizations, PMLC also enables clear ownership and empowerment of project leadership. At GW, PMLC is used for any complex cross-functional initiative that requires the use of a trained project manager for an EVP&T and/or university-wide technology initiative.
Benefits to utilizing PMLC during project management include:
- Clearly defined roles, requirements, and responsibilities allow for greater ownership, buy-in, coordination and efficiency of process
- Clear communication with project sponsors, project owners, and project team
- Standardized methodology that allows for clear expectations and more stream-lined training and process
There are seven phases within PMLC.
Short evaluation of request to determine (1) if resources should be expended to pursue, and (2) if it is actually a project, versus an operational request.
Detailed business case, solution description and comparison of alternatives. Includes business requirements, estimated resource requirements and funding requirements.
Planning, Analysis & Design Phase:
Charter approval, project kickoff, schedule development, project planning.
Begin solution/change development, and plan for testing, readiness and deployment.
Testing & Readiness:
Test solution/changes in controlled environment. Begin readiness activities for go‐live of solution. Go‐live.
Cut-over/Post Go Live:
Monitor implementation of the solution/changes for a predetermined period.
Lessons learned. Formally transition the solution/changes to permanent owner. Release project team.