Delivering organizational strategy through the use of standardized project management practices.
PM Lite (Project Management Lite) is a project management process made up of tools, templates, and best practices that empowers its users to be more efficient and effective in project delivery regardless of project size or complexity.
This methodology is based on the Project Management Institute's "A Guide to the Project Management Body of Knowledge (PMBOK Guide) and the
Texas Project Delivery Framework. It's meant to facilitate a scalable, and easy to use, toolset that aligns to a global standards.
The Project Management Office (PMO) at DIR created PM Lite to help enable state and local entities to achieve their core missions through successful project delivery. PM Lite is an optional process. Using these tools and templates can help your organization achieve project consistency, standardization, and project success.
IMPORTANT: PM Lite does NOT supersede the Texas Project Delivery Framework.
Processes and Tools
The below documents help to further explain the PM Lite process, giving an in depth look at each of the project phases and templates.
|Overview||The Overview Document provides some background on the PM Lite methodology and describes its underlying principals
||PM Lite Overview - DOCX (59 KB)|
|Agile||Agile Document instructs Project Managers how to use the PM Lite templates to plan and execute a project using an Agile approach.|
For more information about Agile, please request access to the
Application Development Decision Framework
PM Lite Agile - DOCX (187 KB)|
|Waterfall|| The Waterfall Document instructs Project Managers on how to use the PM Lite templates to plan and execute a project using a more traditional, waterfall, approach. ||
PM Lite Waterfall - DOCX (121 KB)|
|Glossary|| Defines the terms and acronyms used throughout the PM Lite 2.0 process, tools, and templates.|
|PM Lite 2.0 Glossary v1.0 - XLSX (44 KB)|
|Business Case*||The Business Case defines the business need along with the necessary information, from a business standpoint, to determine whether or not the project is worth the required investment. It demonstrates alignment to business and strategic objectives and is used to prioritize the project among other project demands.||
PM Lite Business Case - DOCX (54 KB)|
|Project Charter*||The Project Charter officially authorizes the project and allocates resources. The chartering process forms the project core team and officially kicks off the project.||PM Lite Project Charter - DOCX (49 KB)|
The Requirements document details specific project and product requirements that must be met to satisfy the business objectives.
PM Lite Requirements Document - XLSX (32 KB)
|Backlog||A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome. The product backlog is the single authoritative source for things that a team works on.|
The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.
|PM Light Agile Backlog - XLSX (27 KB)|
|Project Management Plan||The project management plan defines how the project is executed, monitored and controlled, and closed.|| PM Lite Project Management Plan - DOCX (151 KB)|
|Project Register*||The Project Register is a tool that can be used to capture and track key project information, making it easier to monitor, control, and track project details throughout the life of the project.||
PM Lite Project Register - XLSX (74 KB)|
|Project Change Request||The Project Change Request (PCR) is used by the Project Manager to request a change to the project scope, schedule, costs, project milestones and/or deliverables.||PM Lite Project Change Request - DOCX (41 KB)|
|Lessons Learned*||The Lessons Learned document is used to identify and preserve the lessons learned on each project. The purpose of this document is to help the project team share knowledge gained from the experience. A successful Lessons Learned program will help project teams repeat desirable outcomes and avoid undesirable outcomes.||
PM Lite Lessons Learned - DOCX (43 KB)|
|Project Closure*||The Project Closure document formalizes the completion of the project.|| PM Lite Project Closure - DOCX (45 KB)|
*These templates are highly recommended when using PM Lite.
If you have any questions about PM Lite, please contact the Project Management Office at
Project Management Office.
Why use PM Lite? Standard Project Management processes such as PM Lite drives up business value by consistently and predictably delivering organizational strategy.
NOTE: PM Lite does not replace the Project Delivery Framework for major projects. To confirm that your project is eligible for PM Lite, consult the