Group Project

PROJECT PLAN DOCUMENT

COFFEE MANAGEMENT SYSTEM

Mentor: MSc Huy Nguyen Dang Quang

Team Members: Thong Le Huu

Than Le Van

Giap Tran Hoang

Dat Tran Tien

Da Nang, 2024

PROJECT INFORMATION
 Project Plan Version 1.5 | PMS

Project Acronym CMS

Project Title Coffee Management System

Start Date Sep 24, 2024 End Date Dec 31, 2024
Faculty of Vietnamese - American Software Engineering (CMU),
Lead Institution
Duy Tan University
Project Mentor MSc Huy Nguyen Dang Quang

MSc Huy Nguyen Dang Quang

Project Manager
& Contact Details Email: huyndq@duytan.edu.vn
Phone: 0935525354

Le Huu Thong bass030196@gmail.com 0768463655

thanle03102005@gmail.co
Le Van Than 0779400395
m
Members
ngoctran.190570@gmail.co
Tran Hoang Giap 0349473284
m

Tran Tien Dat dattientran265@gmail.com 0945096008

Page 2 of 64
 Project Plan Version 1.5 | PMS

PROJECT PLAN DOCUMENT

Document Title Project Plan Document

Reporting Period Sep 2024

Author(s) Le Huu Thong

Coffee shop
Date Sep 27, 2024 Filename
management.docx
Access Project and FIT program

DOCUMENT HISTORY

Version Person Date Description

Thong Le Huu
Than Le Van
1.0 Sep 24, 2024 Draft
Dat Tran Tien
Giap Tran Hoang

Thong Le Huu Update Information

team, Introduction
1.1 Than Le Van Sep 26, 2024
and Proposal
Giap Tran Hoang Solution

Update Project
1.2 Dat Tran Tien Sep 27, 2024
Overview

Page 3 of 64
 Project Plan Version 1.5 | PMS

SIGNATURE

Document Approvals: The following signatures are required for approval of this
document.

MSc Huy Nguyen Dang Quang

Date
Mentor

Thong Le Huu
Date
Scrum Master

Than Le Van
Date
Member

Giap Tran Hoang

Date
Member

Dat Tran Tien

Date
Member

Page 4 of 64
 Project Plan Version 1.5 | PMS

Table of Contents
I. Introduction...................................................................................................................6
1. Purpose......................................................................................................................7
2. Scope.........................................................................................................................7
3. References.................................................................................................................7
4. Definitions, Acronyms and Abbreviations................................................................7
II. Team organization........................................................................................................7
1. Scrum Team Information...........................................................................................7
2. Role and responsibility..............................................................................................8
3. Communication Methodology...................................................................................9
4. Communication and Report.......................................................................................9
III. Project Overview.....................................................................................................10
1. Project Name...........................................................................................................10
2. Project Duration.......................................................................................................10
3. Project Goal.............................................................................................................11
4. Project vision...........................................................................................................11
5. Project Scope...........................................................................................................11
IV. Schedule and Cost...................................................................................................12
1. Work Breakdown Structure.....................................................................................12
2. Detailed Schedule....................................................................................................12
3. Cost..........................................................................................................................59
V. Development Process..................................................................................................60
1. Reason for selecting process....................................................................................60
2. Description Scrum...................................................................................................60
VI. Project’s Risk...........................................................................................................64
VII. Deliverable...............................................................................................................66
VIII. Configuration Management.....................................................................................67

Page 5 of 64
 Project Plan Version 1.5 | PMS

Table
Table 1: References.............................................................................................................7
Table 2: Definitions, Acronyms and Abbreviations............................................................7
Table 3: Scrum Team Information......................................................................................8
Table 4: Role and responsibility..........................................................................................8
Table 5: Communication Methodology...............................................................................9
Table 6: Communication and Report.................................................................................10
Table 7: Detailed Schedule................................................................................................59
Table 8: Detailed Cost.......................................................................................................60
Table 9: Project’s Risk.......................................................................................................64
Table 10: Detailed Risk.....................................................................................................66
Table 11: Detailed Deliverable..........................................................................................67

Figure
Figure 1: Work Breakdown Structure................................................................................12
Figure 2: Stages in Scrum..................................................................................................61
Figure 3: Scrum team members.........................................................................................62

Page 6 of 64
 Project Plan Version 1.5 | PMS

I. Introduction
1. Purpose
This document provides a summary of the project's objectives, division of work, the
major milestones, required resources, time and overall schedule and budget allocation
used and based on the document proposal to build an expense management application on
time, at the request and plan.

2. Scope
 This document provides an overview about product, process, and team in project.
 This is just a general plan then details plan will be updated throughout the life
cycle of the project.

3. References
No. References
1 Project Plan Template
2 Proposal Document

Table 1: References
4. Definitions, Acronyms and Abbreviations
No. Term Definition or Description
1 API Application Programming Interface
2 UI User Interface
3 AWS Amazon Web Service
4 S3 Simple Storage Service (Cloud Storage)

Table 2: Definitions, Acronyms and Abbreviations

II. Team organization

1. Scrum Team Information
Full Name Position Phone Email

Nguyễn Hữu Thông Leader 0768463655 bass030196@gmail.com

Page 7 of 64
 Project Plan Version 1.5 | PMS

Team
Trần Tiến Đạt 0945096008 dattientran265@gmail.com
member

Team
Lê Văn Thân 0779400395 thanle03102005@gmail.com
member

Team
Trần Hoàng Giáp 0349473284 ngoctran.190570@gmail.com
member

Table 3: Scrum Team Information

2. Role and Responsibility
Role Responsibility Participant(s)
● Responsible for increasing productivity.
● Using the Scrum framework.
Scrum master Nguyễn Hữu Thông
● Facilitates and Coaches the team.
● Owns the impediment Backlog.
● Responsible for the ROI.
MSc Nguyen Dang
Product Owner ● Responsible for the product.
Quang Huy
● Owns the Product backlog.
● Responsible for quality.
● Responsible for delivering the potentially
shippable product of the Application each Trần Tiến Đạt
Team members sprint. Lê Văn Thân
● Report progress based on remaining time. Trần Hoàng Giáp
● Self-organized.
● Owns the Sprint backlog.

Table 4: Role and responsibility

3. Communication Methodology
Audience/
Topic/ Deliverable Frequency Method
Attendees
Manager, Mentor Project Progress
Weekly Meeting, Phone
and Team member Review

Page 8 of 64
 Project Plan Version 1.5 | PMS

Meeting,
Customer, Manager Project Progress
Weekly Conference
and Scrum master Review
Meeting
Customer, Manager Explicit
When needed Meeting
and Scrum master Requirement
Project Progress
Scrum master and
Review and Daily Daily Meeting, Facebook
Team Member
Meeting

Table 5: Communication Methodology

4. Communication and Report

Type of Methods, Frequenc

Information People
communication tools y

Communication among in group

Informed about what was

done in the last 24 hours,
working on plans for
Face to Face Project
Daily Meetings Daily today, the difficulties
or Facebook team
encountered and the
solutions required, just
meeting 10-15 minutes.

Task Planning Meet face to Weekly All members in team Project

Meeting face together to analyze the team,
requirements, functions, Product
working on the sprint Owner
going to do, planning and
Page 9 of 64
 Project Plan Version 1.5 | PMS

design for the sprint.

Complete documentation.
For each stage, sharing
Meet face to materials, given the Project
Task Review face, Skype, strengths and weaknesses team,
15-20 days
Meeting Email for each. Period for each Product
member and the solution Owner
calculated measurement
project.

External communication and reporting

A web based on task

Google
Task tracking system. To Project
Drive, Every day
Management manage or divide task, team
Trello
report bugs/issues.

Table 6: Communication and Report

III. Project Overview

1. Project Name
The project name is: Coffee management system

2. Project Duration
 Project will be started on Sep 24, 2024
 Project will be finished on Dec 31, 2024

3. Project Goal
Build a coffee shop management system that optimizes in-store operations and enhances
efficiency for both customers and staff.
Page 10 of 64
 Project Plan Version 1.5 | PMS

Customers will interact directly with the system through terminals or tablets available at
the coffee shop. They can browse the menu, select items, and place orders on these
devices, reducing wait times and simplifying the ordering process.
The cashier has a dedicated terminal that displays all customer orders in real-time. This
allows cashiers to view, modify, and process payments for orders quickly and accurately.
Once a customer places an order through the system, it is automatically sent to the
kitchen stations for preparation, ensuring faster service and reducing errors in
communication.
By allowing customers to place orders directly through the system and automating order
transmission to the kitchen, the coffee shop can provide quicker and more efficient
service.
The system will provide detailed daily reports summarizing total revenue, itemized by
each beverage and rental item. It will track all transactions, including deposits for rented
items and refunds, giving an accurate view of financial activity. The owner can view
sales trends over specific time periods (daily, weekly, monthly), helping with menu
decisions, inventory management, and long-term planning. This reporting ensures precise
financial tracking and operational transparency.
4. Project Vision
 Create a coffee management system with full feature focus on the instant, quickly
and useful for customer and management.
 Create trust and become long-term partners with recent user and others.

5. Project Scope
 Application running on native platform.
 Admin dashboard running on web platform.

Page 11 of 64
 Project Plan Version 1.5 | PMS

IV. Schedule and Cost

1. Work Breakdown Structure

Figure 1: Work Breakdown Structure

Page 12 of 64
 Project Plan Version 1.5 | PMS

2. Detailed Schedule

Starting Ending
No. Task Duration Person Total Hour
Day Day

Sep 24, Oct 6,

1 Start Up 13 days Team
2024 2020

Gathering Sep 24, Sep 25,

1.1 2 days Team 5
Requirement 2024 2024

Create Proposal Sep 26, Oct 1,

1.2 6 day Team 32
Document 2024 2024

Project Kick-off Oct 1, Oct 2,

1.3 1 days Team 2
Meeting 2024 2024

Make Project Oct 3, Oct 5,

1.4 3 day Team 8
Plan Document 2024 2020

Review Oct 5, Oct 6,

1.5 1 day Thong 1
Document 2024 2020

Oct 6, Nov 22,

2 Development 49 days Team
2024 2024

Oct 6, Oct 16,

2.1 Sprint 1 10 days Team 300
2024 2024

2.1.1 Sprint plan 1 day Oct 17, Oct 17, Team 16

Page 13 of 64
 Project Plan Version 1.5 | PMS

meeting 2024 2024

Create Test Plan Oct 18, Oct 18,

2.1.2 1 day Team 8
Document 2024 2024

Oct 19, Oct 19,

2.1.3 Design Database 1 day Dat 4
2024 2024

Mar 06, Mar 06,

2.1.4 Release Sprint 1 1 day Team 32
2020 2020

Mar 09, Mar 20,

2.2 Sprint 2
2020 2020

Sprint plan Mar 09, Mar 09,

2.2.1 1 day Team 16
meeting 2020 2020

Create Sprint 2
Mar 09, Mar 09,
2.2.2 Backlog 1 day Tai 4
2020 2020
Document

Create Test Plan Mar 10, Mar 10,

2.2.3 1 day Thao 4
Document 2020 2020

Mar 09, Mar 09,

2.2.4 Design Database 1 day Duong 4
2020 2020

2.2.8 Coding

Page 14 of 64
 Project Plan Version 1.5 | PMS

Set up front-end
Mar 11, Mar 12,
develop 2 days Hao 6
2020 2020
environment

Set up back-end
Mar 12, Mar 12,
develop 1 day Tai 2
2020 2020
environment

Code UI “Kid’s
Mar 16, Mar 16,
Face 1 day Thao 8
2020 2020
Management”

Code UI “Add Mar 17, Mar 17,

1 day Thao 4
Image for Kid” 2020 2020

Code UI and
Consume API of Mar 12, Mar 13,
2 days Hao 8
“Recognition 2020 2020
Attendance”

Code UI and
Consume API of Mar 13, Mar 13,
1 day Hao 4
“List Checked in 2020 2020
Kid”

Code UI and 2 days Mar 13, Mar 14, Hao 4

Consume API of 2020 2020
“List Checked

Page 15 of 64
 Project Plan Version 1.5 | PMS

Out Kid”

Code UI and
Consume API of Mar 16, Mar 16,
1 day Hao 4
“Menu 2020 2020
Attendance”

Code UI and
Consume API of Mar 16, Mar 16,
1 day Hao 4
“Analysis 2020 2020
Attendance”

Code UI and
Mar 17, Mar 17,
Consume API of 1 day Hao 8
2020 2020
“Camera”

Code UI and
Consume API of Mar 17, Mar 17,
1 day
“Detail Attended 2020 2020 Thao 4
Kid”

Code UI and
Consume API of Mar 18, Mar 18,
1 day Hao 4
“List Kid without 2020 2020
Attendance”

Configure AWS Mar 12, Mar 12,

1 day Tai 4
S3 2020 2020

Page 16 of 64
 Project Plan Version 1.5 | PMS

Configure AWS Mar 13, Mar 13,

1 day Tai 8
Rekognition 2020 2020

Code API “List Mar 12, Mar 12,

1 day Duong 4
Attendance” 2020 2020

Code API “Post Mar 16, Mar 16,

1 day Tai 4
new Attendance” 2020 2020

Code API “List

Mar 13, Mar 13,
Attendance by 1 day Duong 4
2020 2020
Type”

Code API “Get

Mar 13, Mar 13,
Item Attendance 1 day Duong 4
2020 2020
by Id”

Code API “Delete Mar 13, Mar 13,

1 day Duong 4
Item Attendance” 2020 2020

Code API “List

Mar 16, Mar 16,
Attendance by 1 day Duong 4
2020 2020
Date and Type”

Code API “List

Mar 16, Mar 16,
Attendance for 1 day Duong 4
2020 2020
Class”

Page 17 of 64
 Project Plan Version 1.5 | PMS

Code API “List

Mar 17, Mar 17,
Attendance for 1 day Duong 4
2020 2020
Teacher”

Code API “List

Mar 17, Mar 17,
Kid without 1 day Duong 4
2020 2020
Attendance”

Code API “List Mar 16, Mar 16,

1 day Tai 2
Face Collection” 2020 2020

Code API “Create Mar 16, Mar 16,

1 day Tai 2
Face Collection” 2020 2020

Code API “Get

Mar 17, Mar 17,
Face Collection 1 day Tai 2
2020 2020
by Id”

Code API “Delete Mar 17, Mar 17,

1 day Tai 2
Face Collection” 2020 2020

Code API “Add

Mar 17, Mar 17,
Image from S3 to 1 day Tai 2
2020 2020
Face Collection”

Code API “Add 1 day Mar 17, Mar 17, Tai 2

Image from 2020 2020
Base64 to Face

Page 18 of 64
 Project Plan Version 1.5 | PMS

Collection”

Code API “Add

Faces from Mar 18, Mar 18,
1 day Tai 2
Base64 to Face 2020 2020
Collection”

2.2.9 Testing Team

Test feature
Mar 18, Mar 18, Hao,
“Kid’s Face 1 day 2
2020 2020 Duong
Management”

Test feature “Add Mar 18, Mar 18, Hao,

1 day 2
Image for Kid” 2020 2020 Duong

Test feature
Mar 18, Mar 18, Thao,
“Recognition 1 day 2
2020 2020 Tai
Attendance”

Test feature “List Mar 18, Mar 18, Thao,

1 day 2
Checked in Kid” 2020 2020 Tai

Test feature “List Mar 18, Mar 18, Hao,

1 day 2
Checked Out Kid” 2020 2020 Duong

Page 19 of 64
 Project Plan Version 1.5 | PMS

Test feature
Mar 18, Mar 18, Hao,
“Menu 1 day 2
2020 2020 Duong
Attendance”

Test feature
Mar 18, Mar 18, Hao,
“Analysis 1 day 2
2020 2020 Duong
Attendance”

Test feature Mar 18, Mar 18, Thao,

1 day 2
“Camera” 2020 2020 Tai

Test feature
Mar 18, Mar 18, Thao,
“Detail Attended 1 day 2
2020 2020 Tai
Kid”

Test feature “List

Mar 18, Mar 18, Thao,
Kid without 1 day 2
2020 2020 Tai
Attendance”

2.2.10 Fix bug

Fix bug “Kid’s

Mar 18, Mar 18, Thao,
Face 1 day 2
2020 2020 Tai
Management”

Fix bug feature

Mar 18, Mar 18, Thao,
“Add Image for 1 day 2
2020 2020 Tai
Kid”

Page 20 of 64
 Project Plan Version 1.5 | PMS

Fix bug feature

Mar 19, Mar 19, Thao,
“Recognition 1 day 2
2020 2020 Tai
Attendance”

Fix bug feature

Mar 19, Mar 19, Thao,
“List Checked in 1 day 2
2020 2020 Tai
Kid”

Fix bug feature

Mar 19, Mar 19, Hao,
“List Checked 1 day 2
2020 2020 Duong
Out Kid”

Fix bug feature

Mar 19, Mar 19, Hao,
“Menu 1 day 2
2020 2020 Duong
Attendance”

Fix bug feature

Mar 19, Mar 19, Hao,
“Analysis 1 day 2
2020 2020 Duong
Attendance”

Fix bug feature Mar 19, Mar 19, Hao,

1 day 2
“Camera” 2020 2020 Duong

Fix bug feature

Mar 19, Mar 19, Hao,
“Detail Attended 1 day 2
2020 2020 Duong
Kid”

Fix bug feature 1 day Mar 19, Mar 19, Hao, 2

Page 21 of 64
 Project Plan Version 1.5 | PMS

“List Kid without

2020 2020 Duong
Attendance”

2.2.11 Re-Testing

Re-test feature
Mar 19, Mar 19, Hao,
“Kid’s Face 1 day 2
2020 2020 Duong
Management”

Re-test feature
Mar 19, Mar 19, Hao,
“Add Image for 1 day 2
2020 2020 Duong
Kid”

Re-test feature
Mar 19, Mar 19, Thao,
“Recognition 1 day 2
2020 2020 Tai
Attendance”

Re-test feature
Mar 19, Mar 19, Thao,
“List Checked in 1 day 2
2020 2020 Tai
Kid”

Re-test feature
Mar 20, Mar 20, Hao,
“List Checked 1 day 2
2020 2020 Duong
Out Kid”

Re-test feature
Mar 20, Mar 20, Hao,
“Menu 1 day 2
2020 2020 Duong
Attendance”

Page 22 of 64
 Project Plan Version 1.5 | PMS

Re-test feature
Mar 20, Mar 20, Hao,
“Analysis 1 day 2
2020 2020 Duong
Attendance”

Re-test feature Mar 20, Mar 20, Hao,

1 day 2
“Camera” 2020 2020 Duong

Re-test feature
Mar 19, Mar 19, Thao,
“Detail Attended 1 day 2
2020 2020 Tai
Kid”

Re-test feature
Mar 19, Mar 19, Thao,
“List Kid without 1 day 2
2020 2020 Tai
Attendance”

Mar 20, Mar 20, Thao,

2.2.12 Release Sprint 2 1 day 16
2020 2020 Tai

Mar 23, Apr 03,

2.3 Sprint 3 10 days Team
2020 2020

Sprint plan Mar 23, Mar 23,

2.3.1 1 day Team 16
meeting 2020 2020

Create Sprint
Mar 23, Mar 23,
2.3.2 Backlog 1 day Tai 2
2020 2020
Document

2.3.3 Create Test Plan 1 day Mar 23, Mar 23, Hao 2

Page 23 of 64
 Project Plan Version 1.5 | PMS

Document 2020 2020

Mar 23, Mar 23,

2.3.4 Update Database 1 day Duong 4
2020 2020

2.3.5 Design UI

Design UI of
Mar 23, Mar 23,
“Create Absent 1 day Thao 2
2020 2020
Form”

Design UI of Mar 23, Mar 23,

1 day Hao 2
“Confirm Absent” 2020 2020

Design UI of “List Mar 24, Mar 24,

1 day Thao 2
Absent for Kid” 2020 2020

Design UI of “List
Mar 25, Mar 25,
Absent for 1 day Thao 2
2020 2020
Parent”

Design UI of “List
Mar 24, Mar 24,
Absent for 1 day Hao 2
2020 2020
Teacher”

Design UI of
Mar 25, Mar 25,
“Create Activity 1 day Thao 2
2020 2020
Report”

Page 24 of 64
 Project Plan Version 1.5 | PMS

Design UI of
Mar 25, Mar 25,
“Update Activity 1 day Thao 2
2020 2020
Report”

Design UI of
Mar 24, Mar 24,
“Delete Activity 1 day Hao 2
2020 2020
Report”

Design UI of
Mar 24, Mar 24,
“Create Meal 1 day Hao 2
2020 2020
Report”

Design UI of
Mar 24, Mar 24,
“Update Meal 1 day Hao 2
2020 2020
Report”

Design UI of Mar 25, Mar 25,

1 day Hao 2
“Notification” 2020 2020

Design UI of
Mar 25, Mar 25,
“Detailed 1 day Hao 2
2020 2020
Notification”

Design UI of “Kid Mar 25, Mar 25,

1 day Thao 2
Management” 2020 2020

Design UI of “Kid Mar 26, Mar 26,

1 day Thao 2
Information” 2020 2020

Page 25 of 64
 Project Plan Version 1.5 | PMS

Design UI of
Mar 26, Mar 26,
“Update Kid 1 day Thao 2
2020 2020
Information”

2.3.6 Design Test Case

Design test case

Mar 24, Mar 24, Hao,
for feature 1 day 4
2020 2020 Duong
“Create Absent”

Design test case

Mar 24, Mar 24, Hao,
for feature 1 day 4
2020 2020 Duong
“Confirm Absent”

Design test case

Mar 25, Mar 25, Hao,
for feature “List 1 day 2
2020 2020 Duong
Absent for Kid”

Design test case

for feature “List Mar 25, Mar 25, Hao,
1 day 2
Absent for 2020 2020 Duong
Parent”

Design test case

for feature “List Mar 25, Mar 25, Hao,
1 day 2
Absent for 2020 2020 Duong
Teacher”

Page 26 of 64
 Project Plan Version 1.5 | PMS

Design test case

for feature Mar 23, Mar 23, Thao,
1 day 2
“Create Activity 2020 2020 Tai
Report”

Design test case

for feature Mar 23, Mar 23, Thao,
1 day 2
“Update Activity 2020 2020 Tai
Report”

Design test case

for feature Mar 24, Mar 24, Thao,
1 day 2
“Delete Activity 2020 2020 Tai
Report”

Design test case

for feature Mar 24, Mar 24, Thao,
1 day 2
“Create Meal 2020 2020 Tai
Report”

Design test case

for feature Mar 24, Mar 24, Thao,
1 day 2
“Update Meal 2020 2020 Tai
Report”

Page 27 of 64
 Project Plan Version 1.5 | PMS

Design test case

Mar 25, Mar 25, Hao,
for feature 1 day 2
2020 2020 Duong
“Notification”

Design test case

for feature Mar 25, Mar 25, Hao,
1 day 2
“Detailed 2020 2020 Duong
Notification”

Design test case

Mar 24, Mar 24, Thao,
for feature “Kid 1 day 2
2020 2020 Tai
Management”

Design test case

Mar 24, Mar 24, Thao,
for feature “Kid 1 day 2
2020 2020 Tai
Information”

Design test case

for feature Mar 24, Mar 24, Thao,
1 day 2
“Update Kid 2020 2020 Tai
Information”

2.3.7 Design API

Design API of Mar 24, Mar 24,

1 day Tai 1
“Create Absent” 2020 2020

Design API of 1 day Mar 24, Mar 24, Tai 1

Page 28 of 64
 Project Plan Version 1.5 | PMS

“Confirm Absent” 2020 2020

Design API of
Mar 25, Mar 25,
“List Absent for 1 day Tai 1
2020 2020
Kid”

Design API of
Mar 25, Mar 25,
“List Absent for 1 day Tai 1
2020 2020
Parent”

Design API of
Mar 25, Mar 25,
“List Absent for 1 day Tai 1
2020 2020
Teacher”

Design API of
Mar 25, Mar 25,
“Create Activity 1 day Duong 2
2020 2020
Report”

Design API of
Mar 25, Mar 25,
“Update Activity 1 day Duong 2
2020 2020
Report”

Design API of
Mar 25, Mar 25,
“Delete Activity 1 day Duong 2
2020 2020
Report”

Design API of 1 day Mar 26, Mar 26, Duong 2

“Create Meal 2020 2020

Page 29 of 64
 Project Plan Version 1.5 | PMS

Report”

Design API of
Mar 26, Mar 26,
“Update Meal 1 day Duong 2
2020 2020
Report”

Design API of Mar 25, Mar 25,

1 day Tai 1
“Notification” 2020 2020

Design API of
Mar 25, Mar 25,
“Detailed 1 day Tai 1
2020 2020
Notification”

Design API of
Mar 26, Mar 26,
“Kid 1 day Duong 2
2020 2020
Management”

Design API of Mar 26, Mar 26,

1 day Duong 2
“Kid Information” 2020 2020

Design API of
Mar 26, Mar 26,
“Update Kid 1 day Duong 2
2020 2020
Information”

2.3.8 Coding

Page 30 of 64
 Project Plan Version 1.5 | PMS

Code UI of
Mar 26, Mar 26,
“Create Absent 1 day Thao 4
2020 2020
Form”

Code UI of Mar 26, Mar 26,

1 day Hao 4
“Confirm Absent” 2020 2020

Code UI of “List Mar 27, Mar 27,

1 day Thao 4
Absent for Kid” 2020 2020

Code UI of “List
Apr 01, Apr 01,
Absent for 1 day Thao 4
2020 2020
Parent”

Code UI of “List
Mar 26, Mar 27,
Absent for 2 days Hao 4
2020 2020
Teacher”

Code UI of
Mar 27, Mar 28,
“Create Activity 2 days Hao 6
2020 2020
Report”

Code UI of
Mar 28, Mar 28,
“Update Activity 1 day Hao 6
2020 2020
Report”

Code UI of 1 day Mar 29, Mar 29, Hao 4

“Delete Activity 2020 2020

Page 31 of 64
 Project Plan Version 1.5 | PMS

Report”

Code UI of
Mar 29, Mar 29,
“Create Meal 1 day Hao 4
2020 2020
Report”

Code UI of
Mar 30, Mar 30,
“Update Meal 1 day Hao 4
2020 2020
Report”

Code UI of Mar 30, Mar 30,

1 day Hao 4
“Notification” 2020 2020

Code UI of
Mar 31, Mar 31,
“Detailed 1 day Hao 4
2020 2020
Notification”

Code UI of “Kid Apr 02, Apr 02,

1 day Thao 6
Management” 2020 2020

Code UI of “Kid Apr 02, Apr 02,

1 day Thao 2
Information” 2020 2020

Code UI of
Apr 03, Apr 03,
“Update Kid 1 day Thao 6
2020 2020
Information”

Code API of 1 day Mar 25, Mar 25, Tai 2

Page 32 of 64
 Project Plan Version 1.5 | PMS

“Create Absent” 2020 2020

Code API of Mar 25, Mar 26,

2 days Tai 2
“Confirm Absent” 2020 2020

Code API of “List Mar 26, Mar 26,

1 day Tai 2
Absent for Kid” 2020 2020

Code API of “List

Mar 26, Mar 26,
Absent for 1 day Tai 2
2020 2020
Parent”

Code API of “List

Mar 26, Mar 26,
Absent for 1 day Tai 2
2020 2020
Teacher”

Code API of
Mar 25, Mar 25,
“Create Activity 1 day Duong 2
2020 2020
Report”

Code API of
Mar 25, Mar 25,
“Update Activity 1 day Duong 2
2020 2020
Report”

Code API of
Mar 25, Mar 25,
“Delete Activity 1 day Duong 2
2020 2020
Report”

Page 33 of 64
 Project Plan Version 1.5 | PMS

Mar 26, Mar 26,

Code API of
2020 2020
“Create Meal 1 day Duong 2
Report”

Code API of
Mar 26, Mar 26,
“Update Meal 1 day Duong 2
2020 2020
Report”

Code API of Mar 27, Mar 27,

1 day Tai 2
“Notification” 2020 2020

Code API of
Mar 27, Mar 27,
“Detailed 1 day Tai 2
2020 2020
Notification”

Code API of “Kid Mar 30, Mar 30,

1 day Duong 4
Management” 2020 2020

Code API of “Kid Mar 30, Mar 30,

1 day Duong 4
Information” 2020 2020

Code API of
Mar 30, Mar 30,
“Update Kid 1 day Duong 4
2020 2020
Information”

2.3.9 Testing

Page 34 of 64
 Project Plan Version 1.5 | PMS

Test feature Mar 31, Mar 31, Hao,

1 day 4
“Create Absent” 2020 2020 Duong

Test feature Mar 31, Mar 31, Hao,

1 day 4
“Confirm Absent” 2020 2020 Duong

Test feature “List Mar 31, Mar 31, Hao,

1 day 4
Absent for Kid” 2020 2020 Duong

Test feature “List

Mar 31, Mar 31, Hao,
Absent for 1 day 4
2020 2020 Duong
Parent”

Test feature “List

Apr 1, Apr 1, Hao,
Absent for 1 day 2
2020 2020 Duong
Teacher”

Test feature
Mar 27, Mar 27, Thao,
“Create Activity 1 day 2
2020 2020 Tai
Report”

Test feature
Mar 27, Mar 27, Thao,
“Update Activity 1 day 2
2020 2020 Tai
Report”

Test feature
Mar 30, Mar 30, Thao,
“Delete Activity 1 day 2
2020 2020 Tai
Report”

Page 35 of 64
 Project Plan Version 1.5 | PMS

Test feature
Mar 30, Mar 30, Thao,
“Create Meal 1 day 2
2020 2020 Tai
Report”

Test feature
Mar 30, Mar 30, Thao,
“Update Meal 1 day 2
2020 2020 Tai
Report”

Test feature Apr 1, Apr 1, Hao,

1 day 2
“Notification” 2020 2020 Duong

Test feature
Apr 1, Apr 1, Hao,
“Detailed 1 day 2
2020 2020 Duong
Notification”

Test feature “Kid Mar 30, Mar 30, Thao,

1 day 2
Management” 2020 2020 Tai

Test feature “Kid Mar 30, Mar 30, Thao,

1 day 2
Information” 2020 2020 Tai

Test feature
Mar 30, Mar 30, Thao,
“Update Kid 1 day 2
2020 2020 Tai
Information”

2.3.10 Fix bug

Fix bug feature 1 day Mar 30, Mar 30, Thao, 2

Page 36 of 64
 Project Plan Version 1.5 | PMS

“Create Absent” 2020 2020 Tai

Fix bug feature Mar 30, Mar 30, Thao,

1 day 2
“Confirm Absent” 2020 2020 Tai

Fix bug feature

Mar 30, Mar 30, Thao,
“List Absent for 1 day 2
2020 2020 Tai
Kid”

Fix bug feature

Mar 31, Mar 31, Thao,
“List Absent for 1 day 2
2020 2020 Tai
Parent”

Fix bug feature

Mar 31, Mar 31, Thao,
“List Absent for 1 day 2
2020 2020 Tai
Teacher”

Fix bug feature

Apr 01, Apr 01, Hao,
“Create Activity 1 day 2
2020 2020 Duong
Report”

Fix bug feature

Apr 01, Apr 01, Hao,
“Update Activity 1 day 2
2020 2020 Duong
Report”

Fix bug feature

Apr 01, Apr 01, Hao,
“Delete Activity 1 day 2
2020 2020 Duong
Report”

Page 37 of 64
 Project Plan Version 1.5 | PMS

Fix bug feature

Apr 01, Apr 01, Hao,
“Create Meal 1 day 2
2020 2020 Duong
Report”

Fix bug feature

Apr 01, Apr 01, Hao,
“Update Meal 1 day 2
2020 2020 Duong
Report”

Fix bug feature Mar 31, Mar 31, Thao,

1 day 2
“Notification” 2020 2020 Tai

Fix bug feature

Mar 31, Mar 31, Thao,
“Detailed 1 day 2
2020 2020 Tai
Notification”

Fix bug feature

Apr 02, Apr 02, Hao,
“Kid 1 day 2
2020 2020 Duong
Management”

Fix bug feature Apr 02, Apr 02, Hao,

1 day 2
“Kid Information” 2020 2020 Duong

Fix bug feature

Apr 02, Apr 02, Hao,
“Update Kid 1 day 2
2020 2020 Duong
Information”

2.3.11 Re-test

Page 38 of 64
 Project Plan Version 1.5 | PMS

Re-test feature Apr 02, Apr 02, Hao,

1 day 2
“Create Absent” 2020 2020 Duong

Re-test feature Apr 02, Apr 02, Hao,

1 day 2
“Confirm Absent” 2020 2020 Duong

Re-test feature
Apr 02, Apr 02, Hao,
“List Absent for 1 day 2
2020 2020 Duong
Kid”

Re-test feature
Apr 02, Apr 02, Hao,
“List Absent for 1 day 2
2020 2020 Duong
Parent”

Re-test feature
Apr 02, Apr 02, Hao,
“List Absent for 1 day 2
2020 2020 Duong
Teacher”

Re-test feature
Mar 31, Mar 31, Thao,
“Create Activity 1 day 2
2020 2020 Tai
Report”

Re-test feature
Mar 31, Mar 31, Thao,
“Update Activity 1 day 2
2020 2020 Tai
Report”

Re-test feature 1 day Mar 31, Mar 31, Thao, 2

“Delete Activity 2020 2020 Tai

Page 39 of 64
 Project Plan Version 1.5 | PMS

Report”

Re-test feature
Mar 31, Mar 31, Thao,
“Create Meal 1 day 2
2020 2020 Tai
Report”

Re-test feature
Apr 03, Apr 03, Thao,
“Update Meal 1 day 2
2020 2020 Tai
Report”

Re-test feature Apr 03, Apr 03, Hao,

1 day 2
“Notification” 2020 2020 Duong

Re-test feature
Apr 03, Apr 03, Hao,
“Detailed 1 day 2
2020 2020 Duong
Notification”

Re-test feature
Apr 01, Apr 01, Thao,
“Kid 1 day 2
2020 2020 Tai
Management”

Re-test feature Apr 01, Apr 01, Thao,

1 day 2
“Kid Information” 2020 2020 Tai

Re-test feature
Apr 01, Apr 01, Thao,
“Update Kid 1 day 2
2020 2020 Tai
Information”

2.3.12 Release Sprint 3 1 day Apr 03, Apr 03, Team 16

Page 40 of 64
 Project Plan Version 1.5 | PMS

2020 2020

Apr 06, Apr 17,

2.4 Sprint 4 Team
2020 2020

Sprint plan Apr 06, Apr 06,

2.4.1 1 day Team 16
meeting 2020 2020

Create Sprint
Apr 06, Apr 06,
2.4.2 Backlog 1 day Hao 2
2020 2020
Document

Create Test Plan Apr 06, Apr 06,

2.4.3 1 day Thao 2
Document 2020 2020

Apr 07, Apr 07,

2.4.4 Design Database 1 day Tai 4
2020 2020

2.4.5 Design UI

Design UI of
Apr 06, Apr 06,
“Details absent 1 day Hao 2
2020 2020
notification”

Design UI of
Apr 07, Apr 07,
“Attendance 1 day Hao 2
2020 2020
statistics”

Page 41 of 64
 Project Plan Version 1.5 | PMS

Design UI of
“Attendance Apr 07, Apr 07,
1 day Hao 2
without face 2020 2020
recognition”

Design UI of
“Auto attendance Apr 07, Apr 07,
1 day Hao 2
with face 2020 2020
recognition”

Design UI of
Apr 07, Apr 07,
“View list of 1 day Hao 2
2020 2020
notifications”

Design UI of
Apr 06, Apr 06,
“View activities 1 day Thao 2
2020 2020
of kid for parent”

Design UI of
“Update the Apr 07, Apr 07,
1 day Thao 2
notification when 2020 2020
It has a new one”

Design UI of
Apr 07, Apr 07,
“Children's daily 1 day Thao 2
2020 2020
status for parent”

Design UI of 1 day Apr 07, Apr 07, Thao 2

Page 42 of 64
 Project Plan Version 1.5 | PMS

“Health report for

2020 2020
parent”

Design UI of
“Children's tuition Apr 07, Apr 07,
1 day Thao 2
fee report for 2020 2020
teacher”

Design UI of
“Children's tuition Apr 08, Apr 08,
1 day Thao 2
fee report for 2020 2020
parent”

Design UI of
Apr 08, Apr 08,
“Multiple 1 day Hao 2
2020 2020
language”

Design UI of Apr 08, Apr 08,

1 day Thao 2
“News feed” 2020 2020

2.4.6 Design Test Case

Design test case

Apr 08, Apr 08, Thao,
of “Details absent 1 day 2
2020 2020 Tai
notification”

Design test case 1 day Apr 08, Apr 08, Thao, 2

of “Attendance 2020 2020 Tai

Page 43 of 64
 Project Plan Version 1.5 | PMS

statistics”

Design test case

of “Attendance Apr 08, Apr 08, Thao,
1 day 2
without face 2020 2020 Tai
recognition”

Design test case

of “Auto Apr 08, Apr 08, Thao,
1 day 2
attendance with 2020 2020 Tai
face recognition”

Design test case

Apr 09, Apr 09, Thao,
of “View list of 1 day 2
2020 2020 Tai
notifications”

Design test case

of “View Apr 08, Apr 08, Thao,
1 day 2
activities of kid 2020 2020 Tai
for parent”

Design test case

of “Update the Apr 06, Apr 06, Hao,
1 day 2
notification when 2020 2020 Duong
It has a new one”

Design test case 1 day Apr 06, Apr 06, Hao, 2

of “Children's 2020 2020 Duong

Page 44 of 64
 Project Plan Version 1.5 | PMS

daily status for

parent”

Design test case

Apr 07, Apr 07, Hao,
of “Health report 1 day 2
2020 2020 Duong
for parent”

Design test case

of “Children's Apr 07, Apr 07, Hao,
1 day 2
tuition fee report 2020 2020 Duong
for teacher”

Design test case

of “Children's Apr 07, Apr 07, Hao,
1 day 2
tuition fee report 2020 2020 Duong
for parent”

Design test case

Apr 07, Apr 07, Hao,
of “Multiple 1 day 2
2020 2020 Duong
language”

Design test case Apr 07, Apr 07, Hao,

1 day 2
of “News feed” 2020 2020 Duong

2.4.7 Design API

Design API of 1 day Apr 09, Apr 09, Duong 2

“Create Fee 2020 2020

Page 45 of 64
 Project Plan Version 1.5 | PMS

Report”

Design API of
Apr 09, Apr 09,
“Update Fee 1 day Duong 2
2020 2020
Report”

Design API of
Apr 09, Apr 09,
“Delete Fee 1 day Duong 2
2020 2020
Report”

Design API of Apr 10, Apr 10,

1 day Duong 2
“List Fee Report” 2020 2020

Design API of
Apr 10, Apr 10,
“Create Healthy 1 day Duong 2
2020 2020
Report”

Design API of
Apr 09, Apr 09,
“Update Healthy 1 day Tai 2
2020 2020
Report”

Design API of
Apr 09, Apr 09,
“Delete Healthy 1 day Tai 2
2020 2020
Report”

Design API of
Apr 09, Apr 09,
“List Healthy 1 day Tai 2
2020 2020
Report”

Page 46 of 64
 Project Plan Version 1.5 | PMS

Design API of
Apr 10, Apr 10,
“Attendance 1 day Tai 2
2020 2020
statistics”

Design API of Apr 10, Apr 10,

1 day Tai 2
“News feed” 2020 2020

Design API of
Apr 10, Apr 10,
"View absent 1 day Tai 2
2020 2020
notification"

2.4.7 Coding

Code UI and
consume API of Apr 09, Apr 09,
1 day Hao 6
“Details absent 2020 2020
notification”

Code UI and
consume API of Apr 10, Apr 11,
2 days Hao 6
“Attendance 2020 2020
statistics”

Code UI and
consume API of
Apr 11, Apr 12,
“Attendance 2 days Hao 6
2020 2020
without face
recognition”

Page 47 of 64
 Project Plan Version 1.5 | PMS

Code UI and
consume API of
Apr 12, Apr 13,
“Auto attendance 2 days Hao 6
2020 2020
with face
recognition”

Code UI and
consume API of Apr 13, Apr 13,
2 days Hao 6
“View list of 2020 2020
notifications”

Code UI and
consume API of Apr 09, Apr 09,
1 day Thao 6
“View activities 2020 2020
of kid for parent”

Code UI and
consume API of
Apr 10, Apr 10,
“Update the 1 day Thao 6
2020 2020
notification when
It has a new one”

Code UI and
consume API of Apr 10, Apr 11,
2 days Thao 6
“Children's daily 2020 2020
status for parent”

Page 48 of 64
 Project Plan Version 1.5 | PMS

Code UI and
consume API of Apr 11, Apr 13,
3 days Thao 6
“Health report for 2020 2020
parent”

Code UI and
consume API of
Apr 13, Apr 13,
“Children's tuition 1 day Thao 4
2020 2020
fee report for
teacher”

Code UI and
consume API of
Apr 13, Apr 14,
“Children's tuition 2 days Thao 4
2020 2020
fee report for
parent”

Code UI and
consume API of Apr 14, Apr 14,
1 day Hao 8
“Multiple 2020 2020
language”

Code UI and
Apr 14, Apr 14,
consume API of 1 day Thao 6
2020 2020
“News feed”

Code API of 1 day Apr 10, Apr 10, Duong 1

“Create Fee

Page 49 of 64
 Project Plan Version 1.5 | PMS

Report” 2020 2020

Code API of
Apr 10, Apr 10,
“Update Fee 1 day Duong 1
2020 2020
Report”

Code API of
Apr 12, Apr 12,
“Delete Fee 1 day Duong 1
2020 2020
Report”

Code API of “List Apr 12, Apr 12,

1 day Duong 1
Fee Report” 2020 2020

Code API of
Apr 12, Apr 12,
“Create Healthy 1 day Duong 1
2020 2020
Report”

Code API of
Apr 11, Apr 11,
“Update Healthy 1 day Tai 4
2020 2020
Report”

Code API of
Apr 11, Apr 11,
“Delete Healthy 1 day Tai 4
2020 2020
Report”

Code API of “List Apr 13, Apr 13,

1 day Tai 4
Healthy Report” 2020 2020

Page 50 of 64
 Project Plan Version 1.5 | PMS

Code API of Apr 13, Apr 13,

1 day Tai 4
“News feed” 2020 2020

Code API of
Apr 14, Apr 14,
“Attendance 1 day Tai 4
2020 2020
statistics”

Code API of
Apr 14, Apr 14,
“View absent 1 day Tai 4
2020 2020
notification”

2.4.8 Testing

Test feature “Fee Apr 15, Apr 15, Thao,

1 day 2
Report” 2020 2020 Tai

Test feature Apr 15, Apr 15, Thao,

1 day 2
“Healthy Report” 2020 2020 Tai

Test feature
Apr 15, Apr 15, Thao,
“Attendance 1 day 2
2020 2020 Tai
statistics”

Test feature
Apr 15, Apr 15, Thao,
“View absent 1 day 2
2020 2020 Tai
notification”

Test feature 1 day Apr 15, Apr 15, Thao, 2

Page 51 of 64
 Project Plan Version 1.5 | PMS

“News feed” 2020 2020 Tai

Test feature “Auto

Apr 15, Apr 15, Hao,
attendance with 1 day 2
2020 2020 Duong
face recognition”

Test feature
“Attendance Apr 15, Apr 15, Hao,
1 day 2
without face 2020 2020 Duong
recognition”

Test feature
Apr 15, Apr 15, Hao,
“Details absent 1 day 2
2020 2020 Duong
notification”

Test feature
Apr 15, Apr 15, Hao,
“View activities 1 day 2
2020 2020 Duong
of kid for parent”

Test feature
“Update the Apr 15, Apr 15, Hao,
1 day 2
notification when 2020 2020 Duong
It has a new one”

2.4.9 Fix bugs

Fix bug feature Apr 15, Apr 15, Thao,

1 day 2
“Fee Report” 2020 2020 Tai

Page 52 of 64
 Project Plan Version 1.5 | PMS

Fix bug feature Apr 15, Apr 15, Thao,

1 day 2
“Healthy Report” 2020 2020 Tai

Fix bug feature

Apr 15, Apr 15, Thao,
“Attendance 1 day 2
2020 2020 Tai
statistics”

Fix bug feature

Apr 16, Apr 16, Thao,
“View absent 1 day 2
2020 2020 Tai
notification”

Fix bug feature Apr 16, Apr 16, Thao,

1 day 2
“News feed” 2020 2020 Tai

Fix bug feature

“Auto attendance Apr 15, Apr 15, Hao,
1 day 2
with face 2020 2020 Duong
recognition”

Fix bug feature

“Attendance Apr 15, Apr 15, Hao,
1 day 2
without face 2020 2020 Duong
recognition”

Fix bug feature

Apr 15, Apr 15, Hao,
“Details absent 1 day 2
2020 2020 Duong
notification”

Page 53 of 64
 Project Plan Version 1.5 | PMS

Fix bug feature

Apr 16, Apr 16, Hao,
“View activities 1 day 2
2020 2020 Duong
of kid for parent”

Fix bug feature

“Update the Apr 16, Apr 16, Hao,
1 day 2
notification when 2020 2020 Duong
It has a new one”

2.4.9 Re-test

Re-test feature Apr 16, Apr 16, Thao,

1 day 2
“Fee Report” 2020 2020 Tai

Re-test feature Apr 17, Apr 17, Thao,

1 day 2
“Healthy Report” 2020 2020 Tai

Re-test feature
Apr 17, Apr 17, Thao,
“Attendance 1 day 2
2020 2020 Tai
statistics”

Re-test feature
Apr 17, Apr 17, Thao,
“View absent 1 day 2
2020 2020 Tai
notification”

Re-test feature Apr 17, Apr 17, Thao,

1 day 2
“News feed” 2020 2020 Tai

Page 54 of 64
 Project Plan Version 1.5 | PMS

Re-test feature
“Auto attendance Apr 16, Apr 16, Hao,
1 day 2
with face 2020 2020 Duong
recognition”

Re-test feature
“Attendance Apr 17, Apr 17, Hao,
1 day 2
without face 2020 2020 Duong
recognition”

Re-test feature
Apr 17, Apr 17, Hao,
“Details absent 1 day 2
2020 2020 Duong
notification”

Re-test feature
Apr 17, Apr 17, Hao,
“View activities 1 day 2
2020 2020 Duong
of kid for parent”

Re-test feature
“Update the Apr 17, Apr 17, Hao,
1 day 2
notification when 2020 2020 Duong
It has a new one”

Apr 17, Apr 17,

2.4.10 Release sprint 4 1 day Team 16
2020 2020

Project’s
3
Meeting

Page 55 of 64
 Project Plan Version 1.5 | PMS

4 Final release

Table 7: Detailed Schedule

3. Cost

Category Detailed Description

Start date Feb 03, 2020 The start date of project.

End date Apr 22, 2020 The end date of project.

Duration (1) 58 Total day of project.

Working time (2) 8 hours/ day In one day and for one
member.
Total effort (3) = (1) * 1856 hours For four team members and
(2) * 4 entire project.
Labor cost (4) = (3) * 1. USD $1856 For four team members and
entire project. (USD $1/
h/member)
Total cost USD $1856

Table 8: Detailed Cost

V. Development Process
1. Reason for Selecting Process
We use Scrum to do the project “icoffee management system”. Because Scrum is a
process suitable for small and medium software, implementation time short and easy
change request Scrum is a process popular in present with the advantages and benefits
such as: Timeline Flexibility- can later or earlier than originally planned. Good product
quality and reduce production risk, low-cost. Interoperability between clients and

Page 56 of 64
 Project Plan Version 1.5 | PMS

developers, among the team members are set to high. The growth rate faster, saving time
and errors detected earlier.

2. Description Scrum
PRINCIPLE AND DIFFERENT STAGES

The SCRUM methodology relies on the incremental development of a software

application while maintaining a completely transparent list of upgrade or correction
demands to be implemented (backlog). It involves frequent deliveries, usually every four
weeks, and the client receives a perfectly operational application that includes more and
more features every time. This is why the method relies on iterative developments at a
constant rhythm of 2-4 weeks. Upgrades can therefore be more easily integrated than
when using a V-cycle.

This method requires four types of meetings:

 Daily meetings: the entire team meets for approximately 15 minutes every day in
order to answer the following three questions, usually while standing: what did I
do yesterday? What am I going to do today? Is there a cumbersome impediment
today?
 Planning meetings: the entire team gathers to decide on the features that will make
up the following sprint.
 Work review meetings: during this meeting, every member presents what he has
done during the sprint. They organize a demonstration of the new features or a
presentation of the architecture. This is an informal meeting lasting for
approximately 2 hours which is attended by the entire team.
 Retrospective meetings: at the end of each sprint, the team analyzes both
successful and unsuccessful elements of their activity. During this meeting lasting
between 15 and 30 minutes where everyone is invited and speaks on their own

Page 57 of 64
 Project Plan Version 1.5 | PMS

behalf, a vote of confidence is organized in order to decide on the improvements to

be made.

Figure 2: Stages in Scrum

SCRUM ORGANIZATION

The SCRUM methodology involves the following three main players:

 Product owner: In most projects, the product owner is the leader of the client's
project team. He is the one who will define and prioritize the product features and
choose the date and content of each sprint based on values (workloads) that the
team communicates to him.
 Scrum Master: He is a genuine facilitator on the project as he makes sure that
everyone works at their full potential by eliminating impediments and protecting
the team from exterior interferences. Moreover, he pays particular attention to the
respect of the different SCRUM phases.
 Team: a team is typically made up of 4-10 people and groups together all the IT
specialists who are necessary on a project, i.e. an architect, a designer, a developer,
a tester etc. The team is self-organizing and remains unchanged during an entire
sprint.

Page 58 of 64
 Project Plan Version 1.5 | PMS

Figure 3: Scrum team members

SCRUM ADVANTAGES

Scrum differs from other development methods through its advantages which turn it into
a pragmatic response to product owners' current needs:

Iterative and incremental method: this allows to avoid the "tunnel effect", i.e. the fact of
seeing the result only at the final delivery, and nothing or almost nothing during the entire
development phase, which is so frequent with V-cycle developments.

Maximum adaptability for product and application development: the sequential

composition of the sprint content allows to add a modification or a feature which was not
initially planned. This is precisely what renders this method "agile".

 Participatory method: every team member is asked to express his opinions and can
contribute to all the decisions taken on the project. He is therefore more involved
and motivated.
 Enhancing communication: by working in the same development room or being
connected through different communication means, the team can easily

Page 59 of 64
 Project Plan Version 1.5 | PMS

communicate and exchange opinions on the impediments in order to eliminate

them as early as possible.
 Maximizing cooperation: daily communication between the client and the team
enables them to collaborate more closely.
 Increasing productivity: as it removes certain "constraints" of the classical
methods, such as documentation or exaggerated formalization, SCRUM allows to
increase team productivity. By adding to this the qualification of each module
which allows to determine an estimation, everyone can compare their performance
to the average team productivity.

Page 60 of 64
 Project Plan Version 1.5 | PMS

VI. Project’s Risk

In this part of document, it contains several risks that could happen to development team
in the future. It also includes probability, severity and mitigation strategy for each risk.

Rating for Probability Rating for Severity

L Rarely happened. L Low damaged.

M Sometime happened. M Medium damaged.

H Usually happened. H Serious damaged.

Table 9: Project’s Risk

Severit
Risk Definition Probability Mitigation Strategy
y

Not enough
Programing knowledge to Spend more time for
H M
experiences complete a few learning and training.
features.

That members have Discuss together to

Disagreemen
many ideas lead to M L select the most
t
inconsistency. appropriate ideas.

All members must

All member can
calm down, explain
conflict with each
Confliction H L the ideals again from
other while we discuss
beginning, asked
something.
mentor for solution.

Page 61 of 64
 Project Plan Version 1.5 | PMS

The standard Analysis of

procedure cannot meet requirements and
the requirements of processes to ensure
specific solutions. The appropriate levels. If
Technical new process may be the new process is
L L
processes required. The process needed, we need to
can be improved and evaluate this
more efficient. response has
improved over the
old process.

The old equipment can Replacement of old

lead to malfunctioning equipment with new
or being attacked by equipment and try to
Equipment virus. L L keep our equipment
safe and upload data
to cloud store
services.

During the develop, Increased working

members leave the hours.
Behind
project or have a H H
schedule
trouble leading to
project is delayed.

Over budget Due to incorrect H M Reduce salary.

estimates or extend Increase hour-
schedule, so the cost to working. Reducing
develop the higher hardware, machine

Page 62 of 64
 Project Plan Version 1.5 | PMS

than expected. cost.

Block by Limited Upgrade

Network Bandwidth. H L transmission line
network.

Table 10: Detailed Risk

VII. Deliverable

No. Document File name

1 Proposal Document KidsLand_Proposal_Version_1.2.docx

2 Project Plan Document KidsLand_Project-Plant_Version_1.5.docx

3 User Story Document KidsLand_User-Story_Version_1.1.docx

4 Product Backlog Document KidsLand_Product-Backlog_Version_1.1.docx

5 Sprint Backlog Document KidsLand_Sprint-Backlog_Version_1.0.xlsx

6 Database Design Document KidsLand_Database_Version_1.1.docx

7 Test Plan Document KidsLand_Test-Plan_Version_1.1.docx

KidsLand_Test-Case_Sprint 1.xlsx

KidsLand_Test-Case_Sprint 2.xlsx
8 Test Case
KidsLand_Test-Case_Sprint 3.xlsx

KidsLand_Test-Case_Sprint 4.xlsx

9 Interface Design Document KidsLand_User-Interface_Version_1.0.docx

10 Architecture Design Document KidsLand_Architecture_Version_1.0.docx

Table 11: Detailed Deliverable

Page 63 of 64
 Project Plan Version 1.5 | PMS

VIII. Configuration Management

 We will use Time log and Commit on GitLab to tracking member. After
each day working, each member must report and uploads their works to Git
remote and Scrum Master will check them all.
 We will hold a meeting every week to assign task to each member. If
there are some emergencies but we cannot sit together.
 We will hold the daily meeting face to face or Skype call.
 We will meet face to face or Skype call on Saturday weekly to discussion
about the issues, as well as make plan for next week.
 In addition, we also use Facebook in order to connect stakeholder’s project
together.
 All meeting must be documented and pictured.

Page 64 of 64