Following is a sample of just some of the many templates available within APT Online. While the templates can be used standalone, they are designed to be used alongside the methods within APT Online describing how each section is completed and managed.
Feel free to download and tailor them for your own purposes.
Business Case for a Program Management Office (PMO)
The documented business case for your Program Management Office (PMO) is the single document that binds together the foundations for your PMO. Implementing or improving a PMO can be expensive in terms of the effort required to establish procedures, practices and methods, the effort required for assessment and planning and the direct costs such as purchasing training and tools.
Executive buy in across all business units involved in the PMO is critical to its success. A powerful presentation demonstrating the benefits, short, medium and long term gains of a PMO needs to be prepared and presented to the Executive. The input and discussion following the presentation will form the basis of the Business Case to be signed off by all stakeholders.
PEP for a PMO Improvement Project
The Project Execution Plan (PEP) for a PMO Improvement Project can be used for a startup PMO attempting to put some basic methods and practices in place through to an advanced PMO striving to reach the next level of maturity.
The PEP is developed only following executive buy in with all stakeholders agreeing on the Business Case, goals and objectives of the PMO. With the stakeholders committed to the project, an assessment of your current PMO or practices is undertaken to identify the current situation. The PMO PEP then provides the method on how to move from the current to the planned environment achieving the desired outcomes.
Project Management Templates
Project Execution Plan (PEP)
Many projects are undertaken using a popular shoe brand’s catch phrase – ‘Just do it…’. It is these projects, the ones that are run without any planning or communication, that reside in the high percentage of failed projects. For a project to have any chance of success, it is vital that a formal planning process is undertaken during its starting activities.
The APT Methodology uses the Project Execution Plan (PEP) as its formal planning document. The PEP becomes the ‘heart’ of the project keeping everyone informed of how the project is being performed, what the risks are, who is involved and how it is managed. While the PEP is authored by the Project Manager, the content is the result of input from all parties involved in the project. In large projects the PEP may be the result of a workshop session facilitated by the Project Manager.
The size, content and complexity of a PEP is almost a direct reflection on the size and complexity of the project itself. An organization’s Quality Manager or Project Office should maintain a library of template PEP’s for projects that are typically undertaken. A Project Manager can then draw on the library to help with consistency and familiarity across projects.
Web Architecture Manual
The Web Architecture Manual is built throughout the entire lifecycle of a web development project with the resulting manual becoming a valuable source of information for on-going support and development of the site.
The Web Architecture Manual is initially created in the early scoping and analysis activities of the Web Development phases where the background, scope, constraints, functionality and information requirements are first identified. The Design and Construction activities further develop the manual with the many of the design components and approaches including the publicity, development, testing. implementation and maintenance strategies.
The APT Methodology contains over 100 templates, forms and sample documents for enterprise and project management, systems development and quality management.