Project Review Closure Report
Content
Event Management System
Project Review and Closure Report
1.
Overview
1.1.
Background
It is a web application that user uses to choose his desired event from a series of events. This
application is also provides number of venues along with decoration.
1.2.
Reason for closing the project
The project is being closed as all the required features have been implemented and the project has
been approved by the project guide.
1.3.
Highlights and innovations
One important feature of our project is that user is constantly updated via mail and SMS. Based on
his selection, the approximate amount (or bill) is calculated. Accordingly he can .
2.
Project performance
2.1.
Performance against objectives
To overcome the drawbacks of the existing system, the proposed system has been evolved.
The system provides with the good user interface. The efficient reports can be generated
by using this proposed system.
2.2.
Performance against outcomes
The Existing system is offline windows applications where client need to interact with the
event management team .This drawback is overcome in our system. In this system we
provide a web application where client log-on to our application and co-ordinates with the
team.
2.3.
Performance against schedule
The project has been completed according to the schedule and the proposed time.
2.4.
Performance against budget
The project has been completed according to the budget and the proposed cost estimation.
3.
Lessons Learnt
3.1.
What worked well?
Communicating as a team and understanding exactly what were the requirements of the project
helped. The various documents that were made helped us in ensuring that we have included all the
required features in the project. Also dividing the various activities within the team helped save
time and also completes the project faster.
3.2.
What could be improved?
Maintaining a better schedule and using different algorithms can improve the project.
4.
Closure activities
This section should cover the various activities required to close the project. Where relevant, the
sub-sections should include:
Issues Management – Identify any outstanding issues and who will continue to progress the
issues.
Risk Management – The project should be protected from threats. Database should be
maintained properly and the program must function properly. The reports generated by the
system must be accurate.
4.1.
Financial Management – The project has been completed in proposed budget.
Records Management – The entire record has been stored on the database.
Post Project Responsibilities - The admin is supposed to maintain the database records of the
property.
Recommendations
It would be expected that one of the recommendations would be for the Project Sponsor to agree
that the project can be deemed closed as it has fulfilled all of the requirements as documented in
the relevant Project Plan or brief, or where this is not the case, the Project Sponsor is satisfied that
all outstanding items have been satisfactorily addressed.
Project Review and Closure Report
1.
Overview
1.1.
Background
It is a web application that user uses to choose his desired event from a series of events. This
application is also provides number of venues along with decoration.
1.2.
Reason for closing the project
The project is being closed as all the required features have been implemented and the project has
been approved by the project guide.
1.3.
Highlights and innovations
One important feature of our project is that user is constantly updated via mail and SMS. Based on
his selection, the approximate amount (or bill) is calculated. Accordingly he can .
2.
Project performance
2.1.
Performance against objectives
To overcome the drawbacks of the existing system, the proposed system has been evolved.
The system provides with the good user interface. The efficient reports can be generated
by using this proposed system.
2.2.
Performance against outcomes
The Existing system is offline windows applications where client need to interact with the
event management team .This drawback is overcome in our system. In this system we
provide a web application where client log-on to our application and co-ordinates with the
team.
2.3.
Performance against schedule
The project has been completed according to the schedule and the proposed time.
2.4.
Performance against budget
The project has been completed according to the budget and the proposed cost estimation.
3.
Lessons Learnt
3.1.
What worked well?
Communicating as a team and understanding exactly what were the requirements of the project
helped. The various documents that were made helped us in ensuring that we have included all the
required features in the project. Also dividing the various activities within the team helped save
time and also completes the project faster.
3.2.
What could be improved?
Maintaining a better schedule and using different algorithms can improve the project.
4.
Closure activities
This section should cover the various activities required to close the project. Where relevant, the
sub-sections should include:
Issues Management – Identify any outstanding issues and who will continue to progress the
issues.
Risk Management – The project should be protected from threats. Database should be
maintained properly and the program must function properly. The reports generated by the
system must be accurate.
4.1.
Financial Management – The project has been completed in proposed budget.
Records Management – The entire record has been stored on the database.
Post Project Responsibilities - The admin is supposed to maintain the database records of the
property.
Recommendations
It would be expected that one of the recommendations would be for the Project Sponsor to agree
that the project can be deemed closed as it has fulfilled all of the requirements as documented in
the relevant Project Plan or brief, or where this is not the case, the Project Sponsor is satisfied that
all outstanding items have been satisfactorily addressed.
