Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
Unit 8: D3
74
D3: Project closure report
Project Introduction
At the end of any project (successful or not) a project closure report is created.
This is a FORMAL document so must be accurate in terms of SPELLING and GRAMMAR!
You will need to pay close attention to this as I cannot pass this D level work with errors in this area.
Project Introduction
Project Closure
This report is used to look at why the project has ended and what went well/what lessons can be learned
It is important to appreciate that not all projects come to an end because the project/product has been created.
Layout
Title - Project closure report for....
Subheading - Actions identified
Create a table identifying any actions that were identified from the phase review that needed to be completed so that the project could be closed (p5)
User Research
Project Summary
The next heading will be used to give an overview of the project that you have just completed....to create an e-commerce website.....and what this planned to achieve
Reason for closure
In this section you will talk about the reason that project came to an end. This could be because the website has been created, or it could be due to a project failure i.e. a disagreement between the project team and client.
Assessment of performance
Longest section
In this section you are to look at how well your project has performed when compared to your business case (c2b analysis)
Did you produce all deliverables?
Questions to answer
Did you achieve objectives set in business case?
What aspects of project were successful/unsuccessful?
Performance against time, resources and cost
Performance against time, resources and costs
On time or not? why/why not?
Did you need all of the resources in your project plan? Did you need more/would you get more next time? Why?
Are you on budget or over/under? What is the reason for this?
Performance against savings and benefits
You identified lots of benefits in your business case - have you delivered on these? Where is the evidence? How do you know if you have been successful or not?
WHY
Lessons learned
In this section you discuss the things you would do differently next time. This could be things such as allocating additional time to tasks, employing additional members of staff or having more/less resources available. It could also include changes to financial projections or costs.
User Mapping
Celebrating success
Success
This section is your chance to reflect upon the positives. Even if you project was closed prematurely there will be things that did go well.
These become the things that you don't change when you take on your next project.
Team?
Resources?
Anticipated benefits?
You are looking to record down the biggest successes of your project
The next steps
These are the things that still need to happen
You must include:
Outstanding activities - What do you still need to do? P6 and M3 documentation for a start!
Remaining risks/issues - is there any other risks or issue between you and your client
Prototypes
On-going dependencies - These are the things that still need to happen. I.E. does testing still need to be completed before handover? Does the site need to still be launched
Costs of on-going support - If you said you were offering support/on-going training then list here how much this will cost the client and what will be included/excluded in and support packages
Stakeholder Communication
A table would be good here
Stakeholder comms
Here you list any communications that need to take place with stakeholders - Client, Companies involved with project i.e. web hosting/domain names etc.
How will you communicate, when will this happen and who is responsible?
Handover
This is where you formally handover any assets or contracts to the client
List the asset/contract, who has current ownership, who it will be handed over to, when this will happen
Handover
Task
Use the bullet points on page 15 of your PDF
You MUST include ALL of these to pass the distinction level task
This is a very detailed piece of work and will take a significant amount of effort - these tasks could get you an A* UCAS remember