Development of a Restaurant Management System: Project Closure Report

Verified

Added on  2022/11/29

|23
|3754
|383
Report
AI Summary
This project closure report details the development of a restaurant management system for BigTen Restaurant. The project aimed to improve inventory and financial management. The report covers project background, highlights, and a synopsis of the closure. It assesses project metrics, including goals, success criteria, milestones, schedule, and budget performance. Key findings include the successful development of a touch screen interface linked to a financial and inventory database, although the project exceeded its budget. The report also addresses resource, issue, risk, and quality management, along with communication and customer expectation management. Lessons learned include the importance of detailed requirements gathering and effective scope management. Recommendations include better planning, resource management, and risk mitigation. The report concludes with post-project tasks and recommendations for future projects, such as the development of an employee time attendance system, and continued system support.
Document Page
Project Closure Report
Project Name: Development of a Restaurant Management System
Department: IT
Focus Area: Software Development
Product/Process: Develop a Software for BigTen Restaurant, a new restaurant where
the owner/ manager has been unable to efficiently manage inventory or finances.
Prepared By
Document Owner(s) Project/Organization Role
Project Closure Report Version Control
Version Date Author Change Description
1/01/201
9
Final version One
Confidential
10456060209767643136.docx
Last printed on 6/1/2004 1:22:00 PM
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Project Closure Report
TABLE OF CONTENTS
1 PROJECT CLOSURE REPORT PURPOSE.............................................................3
2 PROJECT CLOSURE REPORT GOALS..................................................................3
3 PROJECT CLOSURE REPORT SUMMARY............................................................3
3.1 Project Background Overview...........................................................................3
3.2 Project Highlights and Best Practices................................................................3
3.3 Project Closure Synopsis...................................................................................3
4 PROJECT METRICS PERFORMANCE....................................................................3
4.1 Goals and Objectives Performance...................................................................3
4.2 Success Criteria Performance...........................................................................3
4.3 Milestone and Deliverables Performance..........................................................3
4.4 Schedule Performance......................................................................................3
4.5 Budget Performance..........................................................................................3
4.6 Metrics Performance Recommendations...........................................................3
5 PROJECT CLOSURE TASKS..................................................................................3
5.1 Resource Management.....................................................................................3
5.2 Issue Management............................................................................................3
5.3 Risk Management..............................................................................................3
5.4 Quality Management.........................................................................................3
5.5 Communication Management............................................................................3
5.6 Customer Expectation Management..................................................................3
5.7 Asset Management............................................................................................3
5.8 Lessons Learned...............................................................................................3
5.9 Postproject Tasks..............................................................................................3
5.10 Project Closure Recommendations...................................................................3
Confidential Page 2 9/6/2024
Document Page
Project Closure Report
6 PROJECT CLOSURE REPORT APPROVALS.........................................................3
7 APPENDICES........................................................................................................... 3
7.1 Project Closure Report Sections Omitted..........................................................3
Confidential Page 3 9/6/2024
Document Page
Project Closure Report
WBS
Source: Author
Confidential Page 4 9/6/2024
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Project Closure Report
1 PROJECT CLOSURE REPORT PURPOSE
Project Closure Report Purpose
The closure report is produced to enable the assessment of project success,
resolve all issues that are open, identify best practices that can be used in future
projects, and close the project formally (Aziz, 2015)
2 PROJECT CLOSURE REPORT GOALS
Project Closure Report Goals
The following goals are will be achieved through the creation of this project
closure report;
Review and evaluate the project milestones and success.
Confirm outstanding issues, risks, and recommendations.
Outline the tasks and activities required for close the project.
Outline the accomplished tasks and activities.
Identify project highlights and lessons learned as well as best practices for
future projects.
3 PROJECT CLOSURE REPORT SUMMARY
3.1 Project Background Overview
Project Background Overview
The objectives were to evaluate the existing processes at BigTen Restaurant,
Confidential Page 5 9/6/2024
Document Page
Project Closure Report
identify problems and opportunities for improvements, and develop a solution
that solves the clients’ problems as well as improves operations and
management at the restaurant.
Test the system and ensure it meets set functional and non functional
performance metrics within time and on budget.
Create suitable project documentation and manage the system over a three
year period.
3.2 Project Highlights and Best Practices
Project Highlights and Best Practices
Confidential Page 6 9/6/2024
Document Page
Project Closure Report
Project Highlights:
Project budgeted for accurately
Solution developed iteratively in the presence of customer resulting in a final
solution with very few problems
Project delivered within time and scope
Solution meets client expectations and offers avenues for future
improvements and up-scaling
Best Practices:
Effective project planning
Use of project management methodologies and techniques
Risk identification and management used
Stakeholders identified and communicated with effectively
Use of a suitable project management methodology (Agile XP)
Project tracked and monitored against the scope baseline
Effective planning minimized the need for significant changes to the project
scope
these are consistent with those proposed by the project management
institute (Salapatas, 2010)
3.3 Project Closure Synopsis
Project Closure Synopsis
The project is being closed because objectives and nearly all of the
deliverables were fully achieved
Confidential Page 7 9/6/2024
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Project Closure Report
Confidential Page 8 9/6/2024
Document Page
Project Closure Report
4 PROJECT METRICS PERFORMANCE
4.1 Goals and Objectives Performance
Goals and Objectives Performance
The objectives were largely met; the vision was to develop a cross platform
system to enhance the operations and management of the restaurant, which
were largely achieved with a touch screen interface linked to a financial and
inventory database. However, some objectives such as employee time
management was not achieved. Further, the project cost went above the initial
budget by 23%, above the 10% that had been budgeted for as contingency. In a
nutshell, the objectives were met 87%
4.2 Success Criteria Performance
Success Criteria Performance
Most performance criteria were achieved and the success level is placed at
87%
Some criteria were not achieved due to technical issues which required
hiring a systems analysts as the project was being executed, leading to an
increase in overall project costs.
The employee time management function will be achieved at a future date?
The project manager [author] is responsible?
4.3 Milestone and Deliverables Performance
Milestones and Deliverables Performance
Confidential Page 9 9/6/2024
Document Page
Project Closure Report
Most deliverables were achieved within the stipulated time frame; the
deliverable that was not achieved was employee time attendance but the
client accepted the project none the less
The time attendance system required the purchase f additional supporting
hardware systems that were outside the initial budget and were raised when
the project objectives and user requirements had been set. It was then
agreed that it can be incorporated at a later date into the developed system
The achievement is anticipated at a later date when the second upgraded
version of the system is developed
4.4 Schedule Performance
Schedule Performance
Confidential Page 10 9/6/2024
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Project Closure Report
Project Schedule Overview: The project schedule performance is accordance
with the schedule baseline as the project was completed within time although
some tasks took longer than expected and so had to be compensated through
compression of other tasks, using more resources, and over time work
Project Schedule Control Process: The schedule was controlled through regular
performance reviews, future project parts adjusted to handle delays, and
change and control processes used
Project Schedule Corrective Actions: Compression and adjustment of future
activities and tasks, resource leveling to distribute work, variances measured
against the schedule baseline, and remaining tasks and components of the
project Re- estimated (Butler, 2019).
Project Schedule Integration with Managing Project: Involved making trade offs
in competing alternatives and objectives to meet client objectives. This was
achieved by developing a project plan, executing the project plan, and
integrating change control and risk management into the project execution as
per Westland (2019).
4.5 Budget Performance
Budget Performance
Project Budget Overview: The budget was exceeded by 23% (13% above the
allocated contingency of 10%)
Project Budget Corrective Actions: Better planning for resources (labor),
incorporating contingency amounts into the budget and eliminated unwanted
extra effort (Milošević and Martinelli, 2016) (the analysts work was stopped after
realizing it would not add value to the project progress and could instead to be
incorporated [ employee time attendance] at a later date)
Confidential Page 11 9/6/2024
Document Page
Project Closure Report
4.6 Metrics Performance Recommendations
Metrics Performance Recommendations
The project scope and objectives as well as deliverables will be better defined at
the start of the project and strict scope management used to avoid scope creep
as happened with the hiring of a system analysts and the need to incorporate
employee attendance management system. Detailed user requirements will be
elicited before project commencement (Haughey, 2019)
Confidential Page 12 9/6/2024
chevron_up_icon
1 out of 23
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]