Guidance for the Basic Project Methodology

The basic project methodology includes a set  of templates suitable for all projects. It is particularly suitable for smaller projects, e.g. less that 100 days effort, and projects with relatively few external dependencies.

Any project that involves the deployment of a system onto the Applications Division system must follow the Division's procedures for deployment, including the creation or update of a Deployment Checklist, System Description Document, Technical Architecture Document and Service Level Agreement.

The  templates provided for the Basic Project Methodology are:

Project Brief Provides a complete and unambiguous description of the project with scope, business objectives, suggested approach, costs and benefits.
Project Organisation Lists all members of the project team and described their roles within the project.
Stakeholder Map and Communications Plan Identifies the stakeholders for the project and ways in which the project will communicate with them.
Project Estimate An Excel based tool which allows you to create a resource estimate for the project, based on the best case, most likely case, and worst case scenarios.
Stage Plan A plan identifying the project stages with dates for approval and sign-off. Also includes a link to a simple Excel based project plan.
Milestone Completion Log A record of key milestone dates, including description and details of planned dates and dates actually achieved.
Milestone Sign Off Review Used to record stakeholder agreement on the achievement of each milestone together with any outstanding actions or issues.Achievement of milestones should be formally signed off by the relevant project stakeholders. For example acceptance of project deliverables should normally must be signed off by the project sponsor and user representatives.
Risk Log Used to identify and evaluate project risks. Used to track and monitor risks as part of the activity to successfully deliver the project.
Project Issue and Change Control Log (PICCL) Used to record and manage all project issues and changes. Each entry includes a description of the issue or change along with the recommended and agreed way forward. The PICCL is an important tool used to provide a governance framework for the project.
Project Status Report A report used to report on progress throughout the project. Includes a summary of progress, milestones achieved in the last period, milestones for the next period, and details of any issues.
Completion Report A report completed as part of the project closure process summarising the project deliverables and identifying any outstanding issues.

Notes

  1. These templates may be supplemented as required by any templates from the Standard Software Project Methodology
  2. For Basic projects managed by IS Applications the process for getting an ASTA project code is the same as for the Standard Software Project Methodology Guidance for a Standard Software Project - Planning  

If you would like to add your project to the Projects Web Site please complete the Add a Project form on the Requests page. Please use the the Feedback Form so that we can use your input to improve the site!

jump to left-hand (main) navigation