Because every member has a different level of project management skills and capabilities, some members are compliant with TAC 216 today and other members will need to work toward compliance over the next few years as they develop their project management skills.
To access the template, click the name of the template.
To access examples (if available), click the icon(s) to the right of the template name.
Core Documents
| 2018 Companion Guide (PDF) The TAC 216 Companion Guide helps project teams define a project, provide a method for classifying projects based on their complexity and risk, and outline minimum requirements for completing projects based on their classification level | |
| 2018 Complexity Assessment (xlsx) (NEW) Use the 2018 or 2016 Complexity Assessment to determine if the information resources effort is a project and if it is a project, classify it as a Level 1, Level 2, Level 3 or Level 4 project |  |
| 2016 Complexity Assessment (xlsx) Use the 2018 or 2016 Complexity Assessment to determine if the information resources effort is a project and if it is a project, classify it as a Level 1, Level 2, Level 3 or Level 4 project |
2018 Best Practices
| Project Request (docx) (UPDATED) Use a Project Request to describe the project and request approval to develop a Business case or a Project Charter |  |
| Business Case (docx) (UPDATED) Develop a Business Case to document a project's benefits and let decision makers review and decide if the project should be approved to go forward or rejected |  |
| Project Plan (docx) (UPDATED) Use a Project Plan to document key information about the project, including the scope, schedule, budget, stakeholders, resources and communication plans, and the project's approach to managing risk, quality and changes. The Project Planning template also documents how the result project will transition to IT operations when it finishes | |
| Project Portfolio Tracker (xlsx) (NEW) Use the Project Portfolio Tracker to let IT management track how projects are meeting organizational strategic goals | |
2016 Best Practices
| Project Charter (docx) Develop a Project Charter to provide a common vision and understanding of what the project will accomplish, an initial estimate of how much it will cost and how long it will take and who will be involved | |
| Risk Register (xlsx) Use the Risk Register to list project risks and strategies for managing them | |
| Lessons Learned (docx) Use the Lessons Learned to show how project events were addressed and what could be done differently on future projects | |
| Level 1 Project (docx) (UPDATED) Use the Level 1 Project to bring together elements of the Project Charter, the Risk Register and Lessons Learned for Level 1 small projects | |
Additional Templates
| Project Log (xlsx) Track issues, changes and lessons learned for the project | |
| Project Change Request (docx) Used to document a change to the project and the impact it will have | |
| Post Project Survey (docx) Helps you gather feedback from project participants and stakeholders | |
| Project Closure (docx) Document the final outcomes of the project | |
| TAC 216 Checklist (xlsx) Used to keep track of all the process group procedures and documentation |