Takeaway System Project Management

TAKEAWAY SYSTEM PROJECT MANAGEMENT
Student Name
Class Name
Professor Name
Date
TOC \o "1-3" \h \z \u 1Project Overview PAGEREF _Toc67496266 \h 31.1Purpose, Scope and Objectives, and Business Case PAGEREF _Toc67496267 \h 31.1.1Scope PAGEREF _Toc67496268 \h 31.1.2Statement of Work (SOW) PAGEREF _Toc67496269 \h 31.1.3Business Case PAGEREF _Toc67496270 \h 41.2Project Deliverables PAGEREF _Toc67496271 \h 61.3Project Organization PAGEREF _Toc67496272 \h 61.4Work Breakdown Structure (WBS) PAGEREF _Toc67496273 \h 71.4.1Task Description Documentation PAGEREF _Toc67496274 \h 91.4.2Organisation Breakdown Structure (OBS) PAGEREF _Toc67496275 \h 101.5Responsibility Assignment Matrix (RAM)101.6Work Authorisation PAGEREF _Toc67496277 \h 111.7Project Charter PAGEREF _Toc67496278 \h 112Risk Assessment PAGEREF _Toc67496279 \h 132.1Risk Identification PAGEREF _Toc67496280 \h 132.2Assessment of Probability and Consequence (Qualitative) PAGEREF _Toc67496281 \h 142.3Assessment of Probability and Consequence (Quantitative) PAGEREF _Toc67496282 \h 142.4Mitigation Strategies PAGEREF _Toc67496283 \h 153Project Schedule PAGEREF _Toc67496284 \h 173.1Activity Duration Estimates PAGEREF _Toc67496285 \h 173.2Gantt Chart PAGEREF _Toc67496286 \h 183.3Activity Network PAGEREF _Toc67496287 \h 184Project Budget PAGEREF _Toc67496288 \h 194.1Project Resources PAGEREF _Toc67496289 \h 194.2Other Costs PAGEREF _Toc67496290 \h 194.3Cost Estimates PAGEREF _Toc67496291 \h 194.4Time-Phased Budget PAGEREF _Toc67496292 \h 225Communications Management PAGEREF _Toc67496293 \h 236Tracking and Status PAGEREF _Toc67496294 \h 256.1Tracking Method PAGEREF _Toc67496295 \h 256.2Notification record PAGEREF _Toc67496296 \h 256.3Control Systems PAGEREF _Toc67496297 \h 257Project Close Out PAGEREF _Toc67496298 \h 26
Project Overview
Purpose, Scope and Objectives, and Business Case
Scope
The scope of the takeaway ordering system emphasizes the possible opportunity and issues faced by customers; the system evaluates the task performance, availability of different foods, and project occurrence cost. The system will ensure an effective food takeaway delivery in the minimum possible time. Customers have to wait for a more extended period after the order; however, installing the takeaway system will minimize their order placing and receiving time, enhancing customer satisfaction. The system will reduce the human resource cost. The customers will get notifications of any menu update in the design.
Further, the takeaway system will allow the business to take feedback from customers on the services. The project will develop a food order website and application to track food products, one-stop food shopping, convenient sales orders to customers, and timely sales tracking for salespeople. The document’s objective is to analyze website design and application needs and strengthen the online food ordering system.
Statement of Work (SOW)
Key Milestone: The project would be completed expectedly in 16 weeks. There are 12 activities from the project start to the acceptance test conducted. Some activities are dependent on others, and some can be started isolated. Project start is the first activity on which other activities are dependent.
Table 1: Key Milestone
Explain

Weeks Required

Requirement Analysis

1

Redesign Existing Parts

6

New Part of Design

3

Interface Design

1

Add New Code

6

Development as a Whole

2

Modify Existing Code

5

Complete Unit Test

1

Update Document

2

Prepare for Overall Test

1

Perform overall test

1

Completion of acceptance tests

1

Resource Requirements: The resources required are stakeholders and the staff. The staff would be based on the project manager, two system engineers, and two programmers. The hardware required would be at least 16GB RAM and 512 GB Hard disk. The operating system would be Windows 13, 128 GB Processor, iCloud and Google Drive as backup, Lucidchart as diagram tools, and 11th generation Rocket Core desktop (Bob and Mike, 2011). The other costs would be associated with the salary payment, wages, utilities, and miscellaneous expenditures that had to be paid in cash or via bank transfer. The estimated cost of the system would be $50,000.
Risks: The possible chances are that the investors and customers might not like the idea; the system processing and implementation would be too costly, and deadlines might not be met. The business needs to update the system regularly, another financial burden on investors. The employees might lack the experience in successfully implementing the project. The software might not achieve the ultimate objectives of speed, cost tracking, and customers’ response. The project stakeholders are investors, clients, and end-users within the project team. These stakeholders have different objectives which need to be catered based on the customers’ demands. These stakeholders have their goals which lead to serious conflict among stakeholders. The stakeholders need to be managed by assessing the environment and identifying the project goals. Based on it, solutions are developed, and solutions are refined.
Acceptance Criteria: The acceptance criteria are based on the customers’ satisfaction level with the system, and no compromise on the quality and food packaging is made. Employees are well-trained in using the system, improving their working efficiencies. The business earns a considerable amount of profit and return on investment compared to the previous years when the system was not implemented.
Business Case
In the contemporary world of globalization and abrupt change in technology, food businesses now focus on setting goals of speed delivery of food orders. The takeaway system is designed to provide quick food services to customers’ demands where the clients can book food items and access the services with no additional charges (Boehm and Ross, 1989). For this purpose, the business will allow customers to scroll a long list of food items, tables available, customer delivery addresses, and feedback options. The system will be dependent on the application program and reduce the manual work of receiving the order and delivering to customers’ demands. It ultimately will lead to better efficiency and working performance of food items and their delivery, emphasizing that the quality is not compromised. Table 2 presents the stages of the business case of our project.
Effective leadership is crucial to managing the situation and leading by example. The visionary and good communicator leads to strengthening the organizational capabilities. The project managers would require necessary resources and have a vision and fight fires. The purpose is to communicate the idea from the top management to all employees involved in the project. The projects teams would be based on a clear sense of mission, cohesiveness, enthusiasm, and result-orientation.
Table 2: Business Case
Stages

Description

Problem Identification

Food businesses now focus on setting goals of speed delivery of food orders due to abrupt changes in technology. Companies with poor capacity to adopt the modern changes lag from their competitors.

Solution

The takeaway system would be beneficial for clients to provide quick food services to customers’ demands where the clients can book food items and access the services with no additional charges.

Approach

The new system will allow the customers to scroll a long list of food items, tables available, customer delivery addresses, and feedback options. The system will be dependent on the application program and reduce the manual work of receiving the order and delivering to customers’ demands.

Risk Analysis

The business needs to update the system regularly, another financial burden on investors. The employees might lack the experience in successfully implementing the project. The possible risks are poor support from employees during the project implementation and poor customer support after the project completion. The project risks could be a delay in the project deliverables and high cost associated.

Value Analysis

The project would be of great value because it ultimately will lead to better efficiency and working performance of food items and their delivery, emphasizing that the quality is not compromised.

Benefits of the System

The orders management would be convenient; further, managing profiles and addresses would lead to a better notification configuration.

Resource Specifications

Systems to develop applications and websites, human capital, and financial resources

Project Deliverables
Project deliverables are presented in Table 3:
Table 3: Project Deliverables
Activities

Deliverables and Description

Requirement Analysis

The phase links to project planning and project scope and links to the initiation of the project plan.

Redesign Existing Parts

It links to the design document and system architecture.

New Part of Design

It is linked with the development and configuration of the new systems.

Interface Design

Here, the interface design is made to make the system user-friendly.

Add New Code

New codes are added to stimulate the system.

Development as a Whole

Overall, the system would be developed as a whole which will be acceptable.

Modify Existing Code

Any issues in the existing codes would be modified.

Complete Unit Test

The system would be tested to check the compatibility with users’ acceptance.

Update Document

Any issues would be removed.

Prepare for Overall Test

The tests tools would be prepared for testing.

Perform overall test

Complete system testing will be conducted.

Completion of acceptance tests

The phase ensures that the project is completed on time and provides the project’s final output.

Project Organization
The project organization is presented in Figure 1, where the project manager, in assistance with the CEO, will look over the project activities. The project staff would be based on two system engineers and two programmers. A total of five people would be working on the project. These stakeholders will be highly experienced and have in-depth knowledge of the system, demands, programming, and customers’ awareness. These persons would collaborate, discuss ideas and analyze the trends to prepare a highly efficient takeaway system (Perrier et al., 2019).
The project organization is crucial to set a clear sense of mission and degree of team members management leading to a project cohesiveness. It will allow the CEO and the project member to acquire an enthusiastic and result-oriented team that focuses on achieving the needs. Another objective of effective team management is to manage the virtual employees working from the destination. The organization will be based on an established code of conduct so that conflicts would be minimum. All team members would be equally treated, so all stakeholders are in the communication loop and process to address conflict. Different conflicts might emerge, which can be managed with a practical organizational chart. The disputes could be both corporate and interpersonal, which needs to be addressed during a project’s life; otherwise, different discrepancies might lead to unsuccessful project completion (Amusan et al., 2018). The conflicts would be managed through efficient resource allocation and joining all team members in one place, so their competition on project issues is minimal.
Figure 1: Project Organization Chart
Work Breakdown Structure (WBS)
The WBS of the takeaway ordering system is shown below. The front page would deliver the user management, use evaluation, food inquiry, shopping cart management, and order management. The takeaway order system would have three major components, i.e., dish query, order management, and store management. These steps would be followed for the successful implementation of the project. The user management would require a change password, login, and other customers’ information. The user evaluation would need information on dish reviews and dish evaluation. The food inquiry will be based on viewing dishes category, according to the store, and viewed dishes. The shopping cart management would be based on adding, deleting, modifying, and shopping cart. The order management would have the information of the order and confirmed receipt.
Figure 2: Front page WBS
left12954100
145732534734500Figure 3: Take-Away Ordering System
Task Description Documentation
The task description documentation is in Table 4:
Table 4: Task Description
Activity

Explain

Duration (weeks)

A

Requirement Analysis

1

B

Redesign Existing Parts

6

C

New Part of Design

3

D

Interface Design

1

E

Add New Code

6

F

Development as a Whole

2

G

Modify Existing Code

5

H

Complete Unit Test

1

J

Update Document

2

K

Prepare for Overall Test

1

L

Perform overall test

1

M

Completion of Acceptance Tests

1

The project manager would take one week to analyze requirements, set strategies, objectives, and other planning in completing the project. The next stage is redesigning existing parts, which will take almost six weeks. The new designs of the parts will take at least three weeks. The following activities would include adding new codes, developing and modifying existing regulations, completing unit tests, and updating documents. The activities would be organized to start the dependent tasks immediately after completing the top job, and independent studies could be formed in isolation. In this way, the project completion time would be minimal, and resources can be secured for better evaluation and cost-saving (Sangaiah et al., 2018). The tests would be conducted to see whether the project has been successfully implemented and customers can conveniently track the website. The website needs to be maximum user-friendly.
Organization Breakdown Structure (OBS)
The organization breakdown structure is presented in Figure 4:
Figure 4: OBS
Responsibility Assignment Matrix (RAM)
Table 5 presents the task dedication of the staff involved in the project. Task responsibility matrix is based on task decomposition, assigning work to relevant personnel, using a matrix-shaped table to indicate the division of labor and responsibilities of the task (Roger, 2011). As can be seen from the table, the hierarchical relationship between job responsibilities and functions is evident.
Table 5: Task Responsibility Matrix
Number

Work division

Manager Mr. Liu

System Engineer Mr. Mike

System Engineer Mr. Wang

Programmer Mr. Zhang

Programmer Mr. Li

1


Approve





1

1.1

Collect information


Review

Design

Implement



1.2

Processing information



Review




1.2

1.2.1

Statistics


Design



Implement



1.2.2

Calculate


Design



Implement


1.3

Print Report


Review

Design

Implement


Work Authorization
The work authorization of the Takeaway System would be between the project manager and its customers. The company will offer food delivery services from the restaurant to end customers in less time. The term of the agreement would be effective since the system is formulated and implemented (Jalote, 2005). The benefits would be provided 24/7, and all payments would be collected from customers immediately, assisting the business in on-time payments to suppliers.
Project Charter
Table 6: Project Charter
PROJECT GOALS

The scope of the takeaway ordering system emphasizes the possible opportunity and issues faced by customers; the system evaluates the task performance, availability of different foods, and project occurrence cost.

DELIVERABLES

ActivitiesDeliverables and DescriptionRequirement AnalysisThe phase links to project planning and project scope and links to the initiation of the project plan.Redesign Existing PartsIt links to the design document and system architectureNew Part of DesignIt is linked with the development and configuration of the new systems.Interface DesignThe interface design is made to make the system user-friendly.Add New CodeNew codes are added to stimulate the system.Development as a WholeOverall the system would be developed as a whole which will be acceptable. Modify Existing CodeAny issues in the existing codes would be modified.Complete Unit TestThe system would be tested to check the compatibility with users’ acceptance.Update DocumentAny issues would be removed.Prepare for Overall TestThe tests tools would be prepared for testing.Perform overall testComplete system testing will be conducted.Completion of acceptance testsThe phase ensures that the project is completed on time and provides the project’s final output.

PROJECT MILESTONES

The project would be completed expected in 16 weeks. There are 12 activities from the project start to the acceptance test conducted. Some activities are dependent on others, and some can be started isolated. Project start is the first activity on which other activities are dependent.

RISKS

The possible risks are that the investors and customers might not like the idea; the system processing and implementation would be too costly, and deadlines might not be met. The business needs to update the system regularly, another financial burden on investors.

Project Organizational Structure


PROJECT AUTHORIZATION

Approved by:

Business Manager

Date




Approved by:

Project Manager

Date

Risk Assessment
Take this from your set exercise on the topic.
Risk Identification
The possible risks are:
* End users resist the system: They might resist it because they believe they could not get the desired products through the online takeaway system.
* During the project period, the investor could hesitate: The investor could be hesitant to invest a considerable amount in the project, as they could believe that they could not get better profitability on the investment. Many takeout ordering systems and investors may often ask to change their requirements after browsing.
* Customer requirements specification: The customers might not like the end product due to poor features, inflexibility, and a lack of user-friendliness.
* Contractual Limitations: The contractual requirements are not effectively met, and the final project might not deliver accurate results. The restriction brought by the contract has a tight schedule requirement and limited contract amount.
* Tight Deadline: The deadline could be too fast, and the project team could not deliver the project on the deadline.
* Historical Project Information: The historical project performance information is not available, and the project could operate at a high cost and low profitability. The project manager might not have previously researched the data, leading to poor strategic development and implementation.
* The Personnel is Inexperienced: As some employees in the project are newly recruited, they may lack experience. Their lack of knowledge or poor involvement in the project could cause a severe threat to efficient project completion and delivery.
* The number of users exceeds the plan: The site may sell special takeout, resulting in a surge in visits. The increase in visits may cause massive traffic to the system that people might quit visiting the website.
* The technology cannot achieve the expected effect: The technology is not well-versed in achieving desired results of profitability, efficiency, and improvement in business operations. In the end, the client might give negative feedback about the system. There are also chances that the competitors might replicate the idea quickly, resulting in a low number of visitors than expected.
Assessment of Probability and Consequence (Qualitative)
Table 6: Qualitative Risk Analysis
Sort

Risks

Risk Event

Probability

Influence

Risk Value

1

End users resist the system

Investors may dislike the whole system due to a specific problem.

80%

70%

40%

2

During the project period, the investor hesitated

Many takeout ordering systems and investors may often ask to change their requirements after browsing.

60%

70%

40%

3

Customer requirements specification

The demand is unclear, increasing the demand and leading to the required diffusion.

70%

50%

35%

4

Contractual
Limitations

The restriction brought by the contract has a tight schedule requirement and limited contract
amount.

30%

50%

15%

5

The personnel are
inexperienced.

As some employees in the project are newly recruited, they may lack experience.

15%

30%

10%

6

The technology cannot achieve the expected
effect.

Some technologies may not achieve the expected effect and cannot satisfy the demander, such as access speed and special effects.

10%

10%

10%

Assessment of Probability and Consequence (Quantitative)
Table 7: Qualitative Risk Analysis
Sort

Risks

Risk Event

Probability

influence

Risk Value

1

Tight
delivery deadlines.

The demander may tighten the delivery period. Resulting in
tight project.

20%

60%

10%

2

Historical project information.

Mobility of developers.

20%

65%

10%

3

The number of users exceeds
the plan.

The site may sell special takeout,
resulting in a surge in visits.

20%

20%

20%

Mitigation Strategies
Table 8: Risk Response Measures
Input

Risk Response Measures

End users resist the system.

* Try to meet the needs of users, i.e., what they demand and what capabilities the business has to meet those demands.
* The interface shall be...