PROJECT MANAGEMENT DOCUMENT

FOR
LUXCAFE MANAGEMENT SYSTEM

Version 1.0 approved

Prepared by

Đỗ Quốc Tuấn – 20211775

DC.IT.12.10

11/09/2024

– Hanoi, September 2024 –

Table of Contents

Page 1
I. PROJECT MANAGEMENT PLAN...........................................................................................................3
1.1. Project Process............................................................................................................................3
1.2 Scope & Estimation......................................................................................................................3
1.3 Project Risks.................................................................................................................................4
1.4 Quality Management...................................................................................................................5
1.5 Responsibility Assignments..........................................................................................................6
1.6. Project Communications.............................................................................................................7
1.7 Tools & Infrastructures.................................................................................................................8
II. PROJECT MONITORING AND CONTROL..............................................................................................8
2.1. Analyze the Critical Path.............................................................................................................8
2.2. Calculate and analyze project costs..........................................................................................10

Page 2
I. PROJECT MANAGEMENT PLAN
1.1. Project Process
[Draw and describe the software development process model that the team would apply into the
project implementation] (Solution for question 1, grade: 1.5 points)

The Agile model is appropriate for the LuxCafe project due to its adaptability and iterative nature. It
allows for regular feedback and adjustments, which is crucial in a project with evolving requirements
such as menu management and integration with delivery services. Agile's sprints will facilitate the
delivery of functional components within the 4-month timeline, ensuring that the system meets user
needs effectively.

1.2 Scope & Estimation

[Create/Provide the list of software product following the table template as below. In this table, we
categorize each software function/use case into three levels of complexity (Simple, Medium,
Complex). For example, Simple: ≤ 3 transactions; Medium: 4-7 transactions, Complex: >7
transactions] (Solution for question 2, grade: 1.5 points)

# WBS Item Complexity Est. Effort

(man-days)

1 Customer Management

1.1 Register customer account Simple 10

1.2 Login customer Medium 25

1.3 Update password Simple 10

2 Menu Management

2.1 Add/Update/Delete Menu Item Complex 45

2.2 Manage item availability Simple 15

3 Order and Sales Management

3.1 Receive order Medium 20

3.2 Process payment Medium 35

3.3 Manage sales revenue Medium 20

4 Payment Management

4.1 In-store payment processing Medium 20

4.2 Mobile app payment processing Medium 20

4.3 Pre-payment support Simple 10

5 Gift Service Support

Page 3
 5.1 Select gift Simple 15

5.2 Place gift order Simple 15

5.3 Process gift payment Simple 10

6 Automatic Ordering

6.1 Set up automatic order Medium 20

6.2 Manage order intervals Medium 20

6.3 Notify customer Medium 20

7 Integration with Delivery Services

7.1 Integrate Giao hàng nhanh Medium 25

7.2 Integrate Grab Medium 25

7.3 Integrate Shopee Express Medium 25

8 Reporting and Statistics

8.1 Sales performance reports Medium 20

8.2 Customer preferences analysis Simple 15

8.3 Operational metrics tracking Simple 15

Total Estimated Effort (man-days) 98

1.3 Project Risks

[List 5 risks detailing the project risks in the table below] (Solution for question 2, grade: 0.5 points)

Risk Description Impact Possibility Response Plans

1 Technical High Medium Conduct early technical feasibility studies to

challenges in identify potential integration issues with
integration delivery services and payment systems.
Regularly review integration progress and
have contingency plans in place.

2 Staff turnover Mediu Medium Implement knowledge transfer processes,

m including documentation and training
sessions for new staff. Establish a supportive
work environment to improve retention and
encourage team stability.

3 Scope creep High High Establish strict change management

processes. Clearly define project scope and
objectives from the outset, and ensure all
stakeholders understand the implications of
changes. Regularly review project scope in

Page 4
 meetings to maintain focus.

4 Compliance issues High Medium Consult legal experts during the planning
with payment phase to ensure compliance with financial
systems regulations and standards. Conduct regular
audits of payment processes to identify and
address compliance issues promptly.

5 Low user adoption Mediu Medium Conduct training sessions for staff and
m customers to familiarize them with the
system. Gather feedback through surveys
and focus groups to understand user
concerns and improve the system based on
their input. Implement marketing strategies
to promote the app and its features.

1.4 Quality Management

[Provide the approach you would apply to improve the project quality (e.g Process Quality,
Documentation Quality, Source Code Quality, test plan, test scope), reach the project quality
objectives] (Solution for question 4, grade: 1.0 point)

To ensure high quality throughout the LuxCafe project, a comprehensive quality management
approach will be implemented. This will encompass various aspects including process quality,
documentation quality, source code quality, and a detailed testing plan.

1. Process Quality

 Establish Clear Processes:

 Define and document processes for each stage of development (requirements

gathering, design, development, testing, deployment).

 Implement Agile methodologies to enable iterative development and continuous

feedback.

 Schedule regular project review meetings to assess progress and address any
process-related issues.

2. Documentation Quality

 Comprehensive Documentation:

 Maintain detailed documentation for all project phases, including:

 Requirements specification

 Design documents

 User manuals and training materials

 Meeting notes and decision logs

Page 5
  Use collaborative tools (e.g., Confluence, Google Docs) to ensure documentation is
accessible and up-to-date.

 Implement version control for documentation to track changes and maintain

historical context.

3. Source Code Quality

 Regular Code Reviews:

 Schedule peer code review sessions to facilitate knowledge sharing and ensure
adherence to coding standards.

 Use static analysis tools (e.g., SonarQube, ESLint) to automatically identify potential
issues in the codebase.

 Establish coding guidelines and best practices to enhance readability and

maintainability.

4. Testing Plan

 Comprehensive Testing Strategy:

 Implement a multi-level testing approach to ensure thorough validation of the

system.

Test Level
Type of Tests Unit Integratio System Acceptance
n

Functional testing (Black box) X

White box testing X X

Retesting

Regression testing X X

Security testing X X

UI/UX testing X

Portable testing X

API testing X X

Performance testing X

1.5 Responsibility Assignments

[Provide the project organization structure and describe the main responsibilities in your project (to
complete the outputs as defined in the above section), in the format as the sample below] (Solution
for question 5, grade: 1.0 point)

Page 6
 D~Do; R~Review; S~Support; I~Informed; <blank>- Omitted
Responsibility P D Q U S
M e A I t
v V / a
A U k
N X e
h
C o
l
d
e
r
s

Project Planning & Tracking D R I

Prepare Project Introduction Document S S D R I

Prepare SRS Document (Overview Part) R D S S R

Prepare SRS Document (User Requirements) D R S S R

Design System Architecture R D I

Develop Application Features I D I

Conduct Code Reviews D R

Perform Unit Testing D R

Integration Testing R D I

System Testing D I

UI/UX Design and Prototyping D R

User Acceptance Testing (UAT) D S R

Prepare User Documentation S D R I

Maintenance and Support D R S I

1.6. Project Communications

[Provide communication objects, communication channels (tool, method), communication schedules,
communication content and communication purposes,..] (Solution for question 6, grade: 1.0 point)

Communication Item Who/ Target Purpose When, Type, Tool,

Frequency Method(s)

Daily Stand-ups Team Discuss daily progress Daily In-person/

Google

Page 7
 Meet

Weekly Progress Team + PM Review milestones and Weekly Google

Review issues Meet

Monthly Stakeholder Stakeholders Inform about project Monthly Email/ In-

Updates status person

QA and Testing Team + PM Review testing progress, Weekly Jira

Updates defects, and fixes during
testing
phase

Project Closure Stakeholders Wrap up project, Once at Google

Meeting , Team discuss next steps for project Meet / In-
maintenance completio person
n

1.7 Tools & Infrastructures

[Provide information about tools or infrastructure for project management, project communication,
storage, documentation, installation, testing or deployment,...] (Solution for question 7, grade: 0.5
points)

Category/Purpose of use Tools / Infrastructure

Weekly Progress Review Jira, Trello

Communication Slack, Google Meet

Documentation Google Docs, Confluence

Testing Selenium, Postman

Deployment AWS, Docker

Storage & Backup Google Drive, Dropbox, AWS S3

Code Repository & Version GitHub, GitLab

Control

II. PROJECT MONITORING AND CONTROL

2.1. Analyze the Critical Path
[Fill in the estimated duration for high-level activities by entering values in the last column
of the table below.](Solution for question 8, grade: 1.5 points)
Assume you have determined and estimated the project schedule with high-level activities as
follows:

Activity Predecessor Duration (Weeks)

Page 8
 Start 0

A: Menu Management Start 2

B: Customer Management Start 2

C: Order and Sales Management A, B 3

D: Payment Management C 2

E: Gift Service Support C 2

F: Automatic Ordering C 1

G: Integration with Delivery Services D 2

H: Reporting and Statistics C, D, E, F, G 2

End H 0

a) Critical Path calculation:

● Path 1: Start → A → C → D → G → H
● Path 2: Start → B → C → D → G → H
● ….

The critical Path: Path 1

Minimum time to complete the project = 12 weeks

b) Assume during the execution of [Activity C: Order and Sales Management], you discover
that you need to accelerate the project schedule to compensate for a delay of 2 weeks.
Propose 2 solutions with explanations and assumptions to achieve this (how the solutions will
help and the difficulties/impact on the project). [fill in the square brackets]

Solution 1: Add Resources to Activity C

 Explanation: Allocate additional development resources to Activity C to speed up the

completion. This could involve hiring temporary developers or reallocating existing
team members from less critical tasks.

 Assumptions:

 Additional resources can be trained quickly and are available.

 The quality of work will not be compromised with the added resources.

 Impact:

Page 9
  Benefits: This should reduce the duration of Activity C from 3 weeks to 2
weeks, allowing the project to stay on schedule.

 Difficulties: There may be a learning curve for the new resources, and
coordination among team members could become more complex, potentially
leading to miscommunication.

Solution 2: Overlap Activities D and G

 Explanation: Start Activity D: Payment Management and Activity G: Integration

with Delivery Services simultaneously instead of sequentially. This means integrating
delivery services while payment management is still ongoing.

 Assumptions:

 There are no dependencies that require D to be fully completed before starting

G.

 The integration tasks can be managed concurrently without increasing risks or

complications.

 Impact:

 Benefits: This could save 2 weeks as both activities can be completed in

parallel instead of one after the other.

 Difficulties: Overlapping activities may lead to increased complexity in

project management and coordination, as both tasks require attention and may
introduce risks of integration issues if not managed carefully.

2.2. Calculate and analyze project costs

[You must provide values of C1, C2, C3 and then calculate] (Solution for question 9, grade: 1.5
points)

a) Calculate the following indicators:

Assumed values:

● Cost of work completed (C1) = 100 million VND

● Cost incurred to date (C2) = 120 million VND
● Budget for scheduled work (C3) = 150 million VND

Calculations:

● Cost Performance Index (CPI): C1 / C2 = 100 / 120 = 0.83

● Schedule Performance Index (SPI): C1 / C3 = 100 / 150 = 0.67

Page 10
 ● Estimate at Completion (EAC): Total Budget / CPI = 400 / 0.83 ≈ 482 million VND
● Variance at Completion (VAC): Total Budget - EAC = 400 - 482 = -82 million VND

b) Provide an assessment of the current status of the project based on CPI and SPI and
provide some management recommendations

Assessment of Current Project Status:

● CPI < 1: Indicates cost overruns.

● SPI < 1: Suggests delays in schedule.

Recommendations:

● Reassess budget allocations and timelines.

● Increase monitoring freaquency to identify isues early.
● Engage stakeholders for potential additional funding resources

Page 11