The A&M System has developed a TAC 216 Companion Guide to 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. The Companion Guide also outlines TAC 216 requirements for project governance, assessment and reporting.
Members may use any IT project management methodology and templates. The Companion Guide has been tested with both agile and waterfall development approaches.
Members are welcome to develop their own approach to compliance with TAC 216, addressing the policy, requirements and standards of TAC 216, or they are welcome to use the TAC 216 Companion Guide.
TAC 216 Companion Guide
The TAC 216 Companion Guide (pdf) organizes these knowledge areas across four project management process groups:
Best Practice Elements for Calendar Year 2016
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. The following Companion Guide elements provide a starting point towards compliance:
- Use the Complexity and Risk Assessment (xlsx) on all IT projects to determine if the effort is a project and if it is a project, classify it as a Level 1, Level 2, Level 3 or Level 4 project.
- Develop a Project Charter (docx) for all project levels (using either the member’s template or the Companion Guide template). See an Example Project Charter (docx).
- Develop and maintain a Risk Register (xlsx) for all project levels (using either the member’s template or the Companion Guide template).
- Develop Lessons Learned (docx) for all project levels (using either the member’s template or the Companion Guide template).
- For smaller projects, the Level 1 Project template (docx) brings elements of the Project Charter, the Risk Register and Lessons Learned into one concise document.
For members with IT project management processes already in place, use the Companion Guide as a best practice check of your current processes.
Project Management Glossary
A Glossary of Project Management Acronyms and Terms (pdf) is available. This glossary is available for TAMUS use, licensed from the Project Management Institute and the copyrighted title, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition.
Additional Templates Available
Additional templates are available for use:
- Develop a Project Request (docx) to describe the project and request approval to develop a Business case or a Project Charter. See an Example Project Request (docx).
- Use a Business Case (docx) to describe the project and seek funding approval. See an Example Business Case (docx).
- Detail the approach to completing the project work with a Project Plan (docx).
- Monitor day-to-day project activities with the Executing, Monitoring and Controlling Document (docx).
- Track issues, changes, risks and lessons learned with the Project Log (xlsx).
- Document a change to the project and the impact it will have with a Project Change Request (docx).
- Using a Post Project Survey (docx) will help you gather feedback from project participants and stakeholders.
- Document the final outcomes of the project with a Project Closure (docx) template.
- Keep track of all the process group procedures and documentation using the TAC 216 Checklist (xlsx).
If you have questions about the TAC 216 Companion Guide, please contact your institution or agency CIO.