International School

Capstone Project 2
CMU-SE 451

Project Plan
Version 1.0
Date: 12/12/2024

Pool Auto
Submitted by
Dung, Nguyen Dang
Cong, Dinh Minh
Nghia, Nguyen Duy
Huy, Ta Hoang
Khoa, Mai Phuoc
Approved by
Hoang, Nguyen Thai

Proposal Review Panel Representative:

Name Signature Date

_________________________ 12-Sep-2024
Capstone Project 1 - Mentor:
Name Signature Date

Hoang, Nguyen Thai _________________________ 21-Dec-2024

 Project Information
Project acronym Pool Auto
Project Title Pool Auto
Start Date 12th Sep 2024 End Date 21th Dec 2024
Lead Institution International School, Duy Tan University
Project Mentor Mr. Hoang, Nguyen Thai
Project Manager Dung, Nguyen Dang
& contact details Email: nguyendangdung240804@[Link]
Tel: 0815706195
Partner
Duy Tan University
Organization
Project Web
URL
Team members Name Email Tel
28211150061 Dung, Nguyen Dang nguyendangdung240804@[Link] 0815706195
28211153070 Cong, Dinh Minh dinhminhcong678@[Link] 0969258866
28219027463 Nghia, Nguyen Duy Kingwinlata@[Link] 0965008659
28219029061 Huy, Ta Hoang huyta152@[Link] 0902327458
28211303276 Khoa, Mai Phuoc phuockhoamai@[Link] 0903532097
 Proposal Document
Document Title Project Plan

Reporting Period

Author(s) & project Dung, Nguyen Dang

Cong, Dinh Minh Member

Role Nghia, Nguyen Duy Member

Huy, Ta Hoang Member

Khoa, Mai Phuoc Menber

Date Sep 12th 2024 Filename ProjectPlan_v1.0

URL

Access Project and CMU Program

Version Date Comments Author Approval
1.0 12/12/2024 Initial Release All members
 TABLE OF CONTENTS
1. Project Overview..........................................................................................................6
1.1 Project Description.......................................................................................................6
1.2 Purpose and Scope.......................................................................................................6
1.2.1 Purpose.................................................................................................................6
1.2.2 Scope....................................................................................................................6
1.3 Assumptions and Constraints.......................................................................................6
1.4 Project Objectives........................................................................................................7
1.4.1 Standard Objectives..............................................................................................7
1.4.2 Specific Objectives...............................................................................................8
1.5 Critical Dependencies...................................................................................................8
1.6 Project Risk..................................................................................................................9
2 Project Development Approach...................................................................................9
2.1 Technical Process.........................................................................................................9
2.1.1 Reasons for selecting............................................................................................9
2.1.2 Agile Methodology.............................................................................................10
2.2 Quality Management..................................................................................................12
2.3 Unit Testing Strategy.................................................................................................14
2.4 Integration Testing Strategy.......................................................................................15
2.5 System Testing Strategy.............................................................................................15
3 Estimation...................................................................................................................16
3.1 Size.............................................................................................................................16
3.3 Schedule.....................................................................................................................17
3.3 Resource.....................................................................................................................31
3.4 Infrastructure..............................................................................................................31
3.5 Training Plan..............................................................................................................32
3.6 Finance.......................................................................................................................33
4 Project Organization...................................................................................................33
4.1 Organization Structure...............................................................................................33
4.2 Project Team..............................................................................................................34
5 Communication & Reporting.....................................................................................35
6 Configuration Management........................................................................................35
7 Security Aspects.........................................................................................................35
REFERENCES.................................................................................................................36
 Project Plan v1.0 - IIJF

1. Project Overview
1.1 Project Description

Project code Pool Auto Contract type Fixed price

Customer 2nd Customer

Project Level Group Project rank A

Group 5T Division

Project Manager/ Dung, Nguyen

Project Type External
Scrum master Dang

Project Category Development Business domain

Application type Commercial Product

1.2 Purpose and Scope
1.2.1 Purpose
To build an intelligent online billiards table booking application with features for
managing reservations and user information. This application will develop a system
that connects customers with billiards venues.
Provide solutions to meet the demand for quick, convenient billiard table bookings,
saving time for players and billiard hall owners.
Build a chatbot system that helps customers find tables that suit their preferences,
provides information about billiard venues of interest, and supports customers in
using features such as booking tables, making online payments, or saving booking
details.
Identify resources, timeline, budget, implement the actual project, and ensure
completion on schedule and within the planned budget.

1.2.2 Scope
Provide a comprehensive solution for online billiard table bookings, enabling customers
to easily reserve tables at their preferred venues. This application will allow billiard hall
owners to post available tables and manage bookings efficiently.
Facilitate matching between customers and venues to ensure a smooth and optimized
booking experience.
An integrated chatbot will serve as a valuable resource for both players and venue
owners, answering user questions, guiding them through the platform, and even
personalizing recommendations. By incorporating this AI assistant, the application will
streamline the user experience and improve overall satisfaction.
1.3 Assumptions and Constraints
Page | 6
 Project Plan v1.0 - IIJF

No Description Note
Assumptions
1 Nodejs version v18.8.0 (or above) and lower version not
Scope
supported.
Customer reviewers will get seven days to approve a
External
2 milestone document. If no comments are received within
Interfaces
this time period, it will be considered as approved.
Constraints
1 The project is developed within 24 weeks and quarterly
Schedule
deployed on the market.
2 The project shall conform to security requirements
Security
specified by the customer
3 The product operates at a high level of performance and
Quality
has a page load of no more than 5 seconds.
4 The project will be implemented by a team including 4
Resources
members
5 The financial estimation for the project is at a budget limit
Budget
of $5000

1.4 Project Objectives

1.4.1 Standard Objectives

Metrics Unit Committed Note

Start Date dd-mmm-yy

End Date dd-mmm-yy
Duration days 100 days
Maximum Team Size Person 4 Person
Billable Effort Person-day 21,5 days
Number of work hours per day
Person-hour 4 hours
for one engineer

Target Basic for setting

Metrics Unit
LSL Average USL Goals

Quality
Customer Point 8.5 9 9.5 Refer to Gx Target

Page | 7
 Project Plan v1.0 - IIJF

in the year 2020,

5% higher than
Satisfaction
previous project (A
project)
Leakage Wdef/UCP

Process
NC/Ob
Compliance

Cost
Effort Efficiency % 70 80 90
Correction Cost % 60 65 70
Delivery
Timeliness % 85 90 95
Requirement
% 80 85 90
Completeness
1.4.2 Specific Objectives
Based on human resources, time, and budget, we will build an online billiard table
booking system that uses intelligent algorithms to match customers with available
tables and venues. The system will operate with high performance and ensure user
safety.
User data will be encrypted and securely stored to prevent data loss.
The project team will implement the system with a focus on minimizing errors and
effectively controlling risks.
1.5 Critical Dependencies

No Dependency Expected delivery date Note

1 Pool Auto 2024 Legacy system
2 VNPay system 2024 External System
3 Firebase storage Cloud 2024 External System
4 Mapbox 2024 External System
5 Google 2024 External System
6 Facebook 2024 External System
7 RASA Chatbot 2024 External System

Page | 8
 Project Plan v1.0 - IIJF

Page | 9
 Project Plan v1.0 - IIJF
1.6 Project Risk

Risk Description Probability Impact I * P Mitigation Strategy

Developing the Discuss and

Incorrect product which does communicate
4 5 20
requirements not accord with the frequently with
requirements Stakeholders
Actual working time Review old tasks and
is not enough to evaluations to
Estimate finish a task estimate for the new
3 5 15
working time compared to the task.
estimated previous Replan for each
time sprint.
Notify the scrum
master (or ask a
Team member who colleague to help
People is ill, has health 3 3 9 you)
problems, or busy Complete the
assigned tasks when
possible
Detect harmful
content in the video
Lack of is a difficult Spend a lot of time
technical technique that all 2 4 8 for learning and
experiences members need to training
research and
develop.
Team members can
conflict with each Conduct a meeting to
Team other while share knowledge,
4 2 8
Communication discussing experience and
something related to learning methods
the project
2 Project Development Approach
2.1 Technical Process
2.1.1 Reasons for selecting.
To keep up with rapidly changing technology trends, we need a flexible and

Page | 10
 Project Plan v1.0 - IIJF
adaptable project development model. Our online billiard table booking project
will continue to expand with new features in the future. We will regularly update
and incorporate new technologies to enhance the appeal and intelligence of the
application.
Currently, our team is small and has limited experience in project development,
which means we may encounter challenges during the software development
stages, and requirements may need to be adjusted for better suitability. Traditional
models, which require high management skills and precision, may not be suitable
for our team.
Adopting the Agile Scrum model will help us address these challenges, provide
valuable experience, and achieve the best possible performance for the project.
2.1.2 Agile Methodology
Pool Auto refers to a set of gameplay features based on continuous development,
where the game modes and solutions evolve through collaboration between
players and the system.
Pool Auto is more than just selecting game types like 8-ball, 9-ball, or straight
pool. It’s not just about features like multiplayer matches, ranked play, or practice
sessions.
Pool Auto is an umbrella term for a set of systems and features based on values
and principles such as fair play, skill improvement, and strategy. When playing in
Pool Auto, players should follow these values and adapt them to make the right
decisions based on the context of the game.

Page | 11
 Project Plan v1.0 - IIJF
2.1.3 Scrum Process

Figure 1: Agile Methodology

About Pool Auto:
Pool Auto is a subset of agile principles applied to online pool gaming. It is a streamlined
process framework designed to enhance the player experience, and it's one of the most
widely adopted methods for improving gameplay and system interaction.
Pool Auto is often used to manage complex gaming features and system updates, utilizing
iterative and incremental practices. This approach significantly boosts player satisfaction
and reduces the time it takes to implement new features compared to traditional methods.
Pool Auto processes allow the platform to smoothly adapt to rapidly evolving user needs
and ensure a game experience that aligns with changing preferences.
A Pool Auto approach benefits the platform and its players by helping to:
 Improve the quality of game features and overall experience.
 Adapt quickly to player feedback and evolving preferences.
 Provide more accurate predictions and updates with less time spent on preparation.
 Maintain better control over game features, schedules, and updates.

Page | 12
 Project Plan v1.0 - IIJF

2.2 Quality Management

2.2.1 Estimates of Defects to be
detected Pre-release review defects:
Process Planned found by review Actual found by review
Requirement 13 10
Design 10 0
Coding 50 25
Other 10 5
Total 83 40
Pre-release test defects:
Process Planned found by review Actual found by review
2.2.2
Requirement 13 10
Design 10 0
Coding 50 25
Other 10 5
Total 73 40
Strategy for Meeting Quality Objectives

Strategy Expected Benefits

Defect prevention using standard guidelines 15-25% reduction in defect
for coding in JavaScript injection rate and about 5%
improvement in overall
productivity. By ensuring
clean and maintainable
code, you'll reduce bugs,
enhance app stability, and
improve performance.
Group review of program specifications for Improvement in quality due to
initial or complex features (e.g., multiplayer early detection of potential defects
mechanics, game physics). in game logic and mechanics. This
ensures smoother gameplay and
reduces issues related to
multiplayer connectivity or game
synchronization.
Group review of design documents and first- Improvement in overall defect
Page | 13
 Project Plan v1.0 - IIJF

time generated code, including participation removal efficiency, leading to

from project leader, developer, and a higher user satisfaction as early
consultant with expertise in gaming bugs are addressed. This also
applications. contributes to productivity gains as
fewer major bugs will emerge later
in the development cycle.
Introduction of agile methodologies like A 5% reduction in defect injection
RUP (Rational Unified Process) to rate, with an additional 1%
implement the project in iterations, with improvement in overall
milestone analysis and defect prevention productivity. Iterative
exercises after each iteration. development will help identify
issues early, especially in complex
features like AI behavior,
multiplayer synchronization, and
UI/UX design, which are critical
for an online billiard game.

Page | 14
 Project Plan v1.0 - IIJF
2.2.3 Quality Control

Review Item Type of Review Reviewer When

Hoang, Nguyen Thai
Dung, Nguyen Dang
Cong, Dinh Minh
Proposal Group review Initial
Nghia, Nguyen Duy
Huy, Ta Hoang
Khoa, Mai Phuoc
Hoang, Nguyen Thai
Dung, Nguyen Dang
Project plan Project Group review Cong, Dinh Minh End of Initiation
schedule One-person Nghia, Nguyen Duy stage
Test Plan review
Huy, Ta Hoang
Khoa, Mai Phuoc
Hoang, Nguyen Thai
Business analysis Dung, Nguyen Dang
and requirements
Cong, Dinh Minh End of 90%
specification Group review
Nghia, Nguyen Duy requirements
document, Use Case
catalog Huy, Ta Hoang
Khoa, Mai Phuoc
Hoang, Nguyen Thai
Dung, Nguyen Dang
Design document, Cong, Dinh Minh End of 90%
Group review
object model Nghia, Nguyen Duy design
Huy, Ta Hoang
Khoa, Mai Phuoc
Hoang, Nguyen Thai
Dung, Nguyen Dang
One-person Cong, Dinh Minh Beginning of
Stage plans
review Nghia, Nguyen Duy each stage
Huy, Ta Hoang
Khoa, Mai Phuoc
Complex/first Group review Hoang, Nguyen Thai End of detailed

Page | 15
 Project Plan v1.0 - IIJF

Dung, Nguyen Dang

specsincl diagrams Cong, Dinh Minh
time test Generaed
Nghia, Nguyen Duy design
cases program
interactive Huy, Ta Hoang
Khoa, Mai Phuoc
Hoang, Nguyen Thai
Dung, Nguyen Dang
After coding for
Cong, Dinh Minh
Code Group review first few
Nghia, Nguyen Duy
programs
Huy, Ta Hoang
Khoa, Mai Phuoc
2.2.4 Measurements Program
Data to be
Purpose Responsible When
collected
Size: No. of
Early estimate project cost PM/SM At the end of stages
KLOC/ FP
Effort: No. Calculate project effort for Team
Daily
person-day scheduling members
Quality: No. Early evaluate product quality
Reviewer, Right after the
defects and the feasibility of the
Tester review/test
detected project
Divide work and allocate
resources properly, ensure the Weekly and at the
Schedule PM/SM
project is completed on time end of stages
and on budget
2.3 Unit Testing Strategy
Grey Box Testing for the Online Billiard Application:
- Combination of Black Box and White Box Testing: Grey box testing allows for
partial knowledge of the system's internal workings. In the case of your online
billiard app, the tester might be aware of how core game mechanics like physics,
scoring, and multiplayer interactions are structured, but not the intricate details of
the code. This enables testing both the user experience and some internal logic, such
as ensuring that the ball movements are accurate or the scoring system works as
intended.
- Writing Test Cases Before Fixing Defects:
+ Behavioral Test Cases: Write test cases to verify key features like
user input (e.g., correct cue ball movement when a player swipes or clicks),
Page | 16
 Project Plan v1.0 - IIJF
the scoring system (ensuring points are accurately awarded based on game
rules), and game progression (e.g., correctly identifying the winner after all
balls are pocketed).
+ Performance Test Cases: Write test cases to ensure that the app
performs well under heavy load, such as multiple players joining a game without
significant lag or delays in rendering the game.
- Continuous and Frequent Test Execution:
+ Regular Testing: Test game features like AI behavior, multiplayer
synchronization, and UI rendering frequently, especially as new features are
added or bugs are fixed. This ensures the game remains stable and performs
well across different devices and browsers.
- Using Jest for Unit Testing:
+ Unit Testing in [Link]: Jest is a great choice for writing unit tests in
a [Link] environment. You can use it to isolate game logic, such as player
score calculations, the physics engine for ball movement, or the random
number generation for cue ball placement, ensuring each function works
correctly in isolation before integrating it into the larger game flow.
- Isolating Code for Rigorous Testing:
+ Isolate Functions for Better Testing: Functions like ball movement,
collision detection, player actions, or game state transitions (e.g., player turn,
game end) should be isolated to ensure they work independently. For
instance, you might test the ball's behavior when it collides with a wall or
other balls, or test how the server handles simultaneous actions from multiple
players in real-time.
+ Automated Unit Testing: This will be particularly useful for
regularly testing critical features like multiplayer mechanics, leaderboards, and
match flow, ensuring consistency in behavior as new features are added.

Page | 17
 Project Plan v1.0 - IIJF

2.4 Integration Testing Strategy

Bottom up Strategy:

- Component Integration from Bottom to Top:

+ In the context of your online billiard app, the lowest-level components (such
as individual game mechanics, ball physics, scoring system, and user
authentication) would be developed first. These components are then integrated
progressively with higher-level components, like the multiplayer system, real-
time communication (using sockets), and the user interface (UI).

+ Drive Components: If a higher-level component (like the multiplayer lobby

or matchmaking system) is not ready, you can use a Driver component (e.g., a
mock or stub) to simulate its behavior, allowing for testing of lower-level
features such as the physics engine and scoring system.

+ Testing Before Completion: As each product backlog item (e.g., game

physics, multiplayer functionality) is completed, you test it in isolation and in
integration with other components. For example, after developing the ball
movement logic, you would integrate and test it with other components like
collision detection and AI-controlled player behavior.

Bigbang Strategy:

- Simultaneous Integration: All components (game mechanics, multiplayer,

UI, backend) are integrated at the same time, typically near the end of the
development.

- End-to-End Testing: Test the whole application together—gameplay,

multiplayer synchronization, UI/UX, and backend functionality.

- Challenges: Debugging can be difficult as it’s hard to pinpoint which

component causes issues. Performance bottlenecks and compatibility problems
may also arise.

- Best Practice: Ensure each component is tested individually before integration

to minimize issues when using the Big Bang approach.

2.5 System Testing Strategy

Page | 18
 Project Plan v1.0 - IIJF
Automation strategy:
- Automation Testing:
Use automated testing tools to run test case suites efficiently. This helps verify
core game mechanics (like ball physics and multiplayer synchronization), UI
elements (like buttons and game status updates), and backend services (like
player profiles and score tracking) without manual intervention.
- Test Automation Tools:
Katalon Studio can be used to automate UI and functional testing of your online
billiard app. It can simulate user interactions like logging in, starting a game,
interacting with the game interface, and checking the multiplayer experience.
- Process:
Automated Test Data Entry: Katalon Studio can enter test data (e.g., player
names, game configurations) and simulate various gameplay actions to test the
app.
Comparison of Expected and Actual Results: It will compare expected
outcomes (e.g., ball movement, score updates, player turn) with the actual results
to identify discrepancies or bugs.
Test Reports: After executing the test cases, Katalon Studio can generate
detailed reports highlighting passed and failed tests, which helps in tracking
progress and debugging issues.
- Considerations:
Cost and Resources: Automated testing requires an initial investment in tools
and setting up the test environment. It may also require ongoing maintenance to
keep tests updated as the app evolves.
Customer testing(Beta testing) strategy:

- Beta Testing: Release a nearly finished version of the app on the Google Play
Store for a group of target users to test in real-world conditions.

- Feedback Collection: Gather feedback on gameplay, performance, and UI/UX.

- Improvement: Use the feedback to fix bugs, optimize performance, and

improve the overall user experience before the official release.

3 Estimation
3.1 Size
(1 point = 2 hours)
All of the Functions Point

Page | 19
 Project Plan v1.0 - IIJF

Authentication (Candidate, Employer, Admin) 18

Dashboard View (Admin, Employer) 16
Manage Job (Employer, Admin) 18
Manage Candidate (Admin, Employer) 18
Manage Employer (Admin) 16
Manage Category Job (Admin) 16
Analysis CV and Recommendation (Employer) 30
Contact Message (Candidate, Employer) 18
Search, Filter, and View Job(Candidate) 16
Apply Job (Candidate) 16
Write CV Online (Candidate) 30
Job Recommendation (Candidate) 30

3.2 Effort
The Effort estimation
Total
% Sprint 1 Sprint 2 Sprint 3 Sprint 4
Total
budget budget
Activity /Process ed ed
Effort
Effort USD % USD % USD % USD %
Usage
Usage (%)
(USD)

Requirement 315.7$ 5 80.68 2 78.57 1 78.16 1 78.38 1

Design 358.3$ 10 90.38 3 90.27 3 89.35 2 89.38 2

1276.5 25 320.5 7 310.6 5 322.1 6 323.1 7

Coding
$
Testing 695$ 18 137.77 5 171.67 4 173.87 4 175.77 5

Deployment 419.1$ 12 104.7 3 104.7 3 104.7 3 104.7 3

Support for
Acceptance 328.8$ 5 81.2 1 81.2 1 84.2 2 82.2 1
Test
Project 301.7$ 5 74.43 1 74.59 1 77.43 2 75.33 1
Planning
Project 227.6$ 5 56.69 1 56.23 1 56.57 1 58.12 2
monitoring

Page | 20
 Project Plan v1.0 - IIJF

Quality 457.2$ 7 102.3 1 118.3 2 118.3 2 118.1 2

Asurance
Training 220.1$ 8 55.05 2 55.02 2 55.02 2 55.02 2

Total 4600$ 100 1139 26 1141 23 1159 25 1160 26

3.3 Schedule
3.3.1 Project Milestone & Deliverable

No Milestone Time Product

The proposal

User Story

User Interface

1 Initial 12/09/2024 Database Document

Product Backlog

Project Plan

Architecture Document

2 Development 27/09/2024 Database Design

2.1 Sprint 1 27/09/2024 Test Plan

2.2 Sprint 2 20/10/2024 Test Case

2.3 Sprint 3 16/11/2024 Sprint Backlog

2.4 Sprint 4 10/12/2024 Product Backlog

3 Project Meeting 20/12/2024 Meeting Document

4 Final Release 21/12 /2024 Reflection Document

3.3.2 Work Breakdown Structure

Page | 21
 Project Plan v1.0 - IIJF

Page | 22
 Project Plan v1.0 - IIJF

3.1.3 Detailed Schedule

Duration
No. Task Name Start Finish Assign to
(Days)
I. Initial 3 12/09/2024 14/09/2024 All Member

1. Discuss project ideal 1 12/09/2024 12/09/2024 All Member

Gathering
2. 1 13/092024 13/09/2024 All Member
Requirement

Create Proposal
3. 1 14/09/2024 14/09/2024 All Member
Document

II. Start Up 12 15/09/2024 26/09/2024 All Member

Project Kick Off

1. 1 15/09/2024 15/09/2024 All Member
Meeting

Create Document for

2. 10 16/09/2024 25/09/202 All Member
project

Create Project Plan

2.1. 2 17/09/2024 18/09/2024 All Member
document

Create Product
2.2. 1 19/09/2024 19/09/2024
Backlog document

Create User Story

2.3. 1 19/09/2024 19/09/2024
document

Create Database
2.4. 2 20/02/2024 22/09/2024
document

Create User Interface

2.5. 1 23/09/2024 23/09/2024
document

Create Architecture
2.6. 2 24/09/2024 25/09/2024
document

2.7. Pre-study 1 26/09/2023 26/09/2024 All Member

Page | 23
 Project Plan v1.0 - IIJF

Project kick off

2.8. 1 26/09/2024 26/09/2024 All Member
meeting

III. Development 83 27/09/2024 18/12/2024 All Member

1. Sprint 1 23 27/09/2024 19/12/2024 All Member

Sprint Planning
1.1 1 27/09/2024 27/09/2024
Meeting

Create Sprint
1.2 1 28/09/2024 28/09/2024
Backlog for Sprint 1

Create Test Plan

1.3 1 29/09/2024 29/09/2024
document for Sprint 1

1.4 Design UI 2 30/09/2024 01/10/2024 All Member

Design UI Chat with

1.4.1 Chatbot on the web 1 30/09/2024 30/09/2024
application [Admin]

Design UI Dashboard
1.4.2 1 30/09/2024 30/09/2024
view [Admin]

Design UI Interact
with the chatbot to
1.4.3 1 30/09/2024 30/09/2024
receive approriate
suggestions

Design UI Create
1.4.4 RASA Chatbot 1 30/09/2024 30/09/2024
Dashboard [Admin]

Design UI Rules
1.4.5 1 30/09/2024 30/09/2024
Management

1.4.6 Design UI Stories 1 01/10/2024 01/10/2024

Page | 24
 Project Plan v1.0 - IIJF
Management

Design UI Respones
1.4.7 1 01/10/2024 01/10/2024
Management

Design UI Intents
1.4.8 1 01/10/2024 01/10/2024
Management

1.5 Code 14 01/10/2024 14/10/2024 All Member

[Front End] Chat

with Chatbot on the
1.5.1 4 01/10/2024 04/10/2024
web application
[Admin]

[Front End]
1.5.2 Dashboard view 2 01/10/2024 02/10/2024
[Admin]

[Front End] Interact

with the chatbot to
1.5.3 2 02/10/2024 03/10/2024
receive approriate
suggestions

[Front End] Create

1.5.4 POOL Chatbot 2 04/10/2024 05/10/2024
Dashboard [Admin]

[Front End] Rules

1.5.5 2 06/10/2024 07/10/2024
Management

[Front End] Stories

1.5.6 2 08/10/2024 09/10/2024
Management

[Front End] Respones

1.5.7 1 10/10/2024 10/10/2024
Management

[Front End] Intents

1.5.8 1 11/10/2024 11/10/2024
Management
Page | 25
 Project Plan v1.0 - IIJF
[Back End] Chat with
1.5.9 Chatbot on the web 4 01/10/2024 04/10/2024
application [Admin]

[Back End]
1.5.10 Dashboard view 3 01/10/2024 03/10/2024
[Admin]

[Back End] Interact

with the chatbot to
1.5.11 2 04/03/2024 05/03/2024
receive approriate
suggestions

[Back End] Create

1.5.12 RASA Chatbot 2 06/10/2024 07/10/2024
Dashboard [Admin]

[Back End] Rules

1.5.13 2 08/10/2024 09/10/2024
Management

[Back End] Stories

1.5.14 2 10/10/2024 11/10/2024
Management

[Back End] Respones

1.5.15 2 12/10/2024 13/10/2024
Management

[Back End] Intents

1.5.16 2 13/10/2024 14/10/2024
Management

1.6 Testing & Fix Bug 2 15/10/2024 16/10/2024 All Member

1.7 Release Sprint 1 2 17/10/2024 18/10/2024 All Member

Sprint 1 Review
1.7.1 1 19/10/2024 19/10/2024 All Member
Meeting

1.7.2 Sprint 1 1 19/10/2024 19/10/2024 All Member

Retrospective

Page | 26
 Project Plan v1.0 - IIJF
2 Sprint 2 20 20/10/2024 15/11/2024 All Member

Sprint Planning
2.1 1 21/10/2024 21/10/2024
Meeting

Create Sprint
2.2 1 22/10/2024 22/10/2024
Backlog for Sprint 2

Create Test Plan

2.3 1 23/10/2024 23/10/2024
document for Sprint 2

2.4 Design UI 2 24/10/2024 25/10/2024 All Member

Design UI for Job

2.4.1 1 26/10/2024 26/10/2024
posting Page

Design UI for
2.4.2 Employer 1 27/10/2024 27/10/2024
management

Design UI for
2.4.3 Candidate 1 28/10/2024 28/10/2024
management

Design UI for Job

2.4.4 application 1 29/10/2024 29/10/2024
management

Design UI for Job

2.4.5 1 30/10/2024 30/10/2024
Apply Page

Design UI Message
2.4.6 Page [Employer] 1 31/10/2024 31/10/2024

Design UI Message
2.4.7 1 01/11/2024 01/11/2024
Page [Candidate]

2.5 Code 10 02/11/2024 11/11/2024 All Member

Page | 27
 Project Plan v1.0 - IIJF
[Front End] for Job
2.5.1 3 02/11/2024 05/11/2024
posting Page

[Front End] for

2.5.2 Employer 4 02/11/2024 05/11/2024
management

[Front End] for

2.5.3 Candidate 4 05/04/2024 09/04/2024
management

[Front End] for Job

2.5.4 application 3 03/11/2024 05/11/2024
management

[Front End] for Job

2.5.5 3 06/11/2024 08/11/2024
Apply Page

[Front End] Message

2.5.6 3 09/11/2024 11/11/2024
Page

[Back End] for Job

2.5.7 3 02/11/2024 04/11/2024
posting Page

[Back End] for

2.5.8 Employer 4 02/04/2024 05/11/2024
management

[Back End] for

2.5.9 Candidate 3 06/11/2024 08/11/2024
management

[Back End] for Job

2.5.10 application 3 06/11/2024 08/11/2024
management

[Back End] for Job

2.5.11 3 09/11/2024 11/11/2024
Apply Page

Page | 28
 Project Plan v1.0 - IIJF
[Back End] Message
2.5.12 3 09/11/2024 11/11/2024
Page

2.6 Testing & Fix Bug 2 12/11/2024 13/11/2024 All Member

2.7 Release Sprint 2 2 13/11/2024 14/11/2024 All Member

Sprint 2 Review
2.7.2 1 15/11/2024 15/11/2024 All Member
Meeting

Sprint 2
2.7.3 1 15/11/2024 15/11/2024 All Member
Retrospective

3. Sprint 3 24 16/11/2024 09/12/2024 All Member

Sprint Planning
3.1 1 16/12/2024 16/12/2024
Meeting

Create Sprint
3.2 1 17/12/2024 17/12/2024
Backlog for Sprint 3

Create Test Plan

3.3 1 18/12/2024 18/12/2024
document for Sprint 3

3.4 Design UI 2 19/12/2024 20/12/2024 All Member

Design UI for
3.4.1 1 19/12/2024 19/12/2024
Decoration Company

Design UI for
3.4.2 1 19/12/2024 19/12/2024
Comment

Design UI for Forum

3.4.3 1 20/12/2024 20/12/2024
Page

Design UI for
Category
3.4.4 1 20/12/2024 20/12/2024
management Page
[Admin]

Page | 29
 Project Plan v1.0 - IIJF
Design UI for Test
3.4.5 1 21/12/2024 21/12/2024
Quizz Page

Design UI for Chat

with Chatbot on the
3.4.6 1 22/12/2024 22/12/2024
web application
[Candidate]

3.5 Code 13 23/11/2024 05/12/2024 All Member

[Front End] for

3.5.1 2 23/11/2024 24/11/2024
Decoration Company

[Front End] for

3.5.2 2 25/04/2024 26/04/2024
Comment

[Front End] for

3.5.3 2 25/04/2024 26/04/2024
Forum

[Front End] for

Category
3.5.4 5 27/04/2024 01/12/2024
management Page
[Admin]

[Front End] for Test

3.5.5 5 28/11/2024 02/12/2024
Quizz Page

[Front End] for Chat

with Chatbot on the
3.5.6 3 03/12/2024 05/12/2024
web application
[Candidate]

[Back End] for

3.5.7 3 23/11/2024 25/11/2024
Decoration Company

[Back End] for

3.5.8 3 23/04/2024 25/11/2024
Comment

Page | 30
 Project Plan v1.0 - IIJF
[Back End] for
3.5.9 3 26/11/2024 28/11/2024
Forum

[Back End] for

Category
3.5.10 3 26/11/2024 28/11/2024
management Page
[Admin]

[Back End] for Test

3.5.11 4 29/04/2024 02/12/2024
Quizz Page

[Back End] for Chat

with Chatbot on the
3.5.12 4 02/12/2024 05/12/2024
web application
[Candidate]

3.6 Testing & Fix Bug 2 06/12/2024 07/12/2024 All Member

3.7 Release Sprint 3 2 08/12/2024 09/12/2024 All Member

Sprint 3 Review
3.7.1 1 09/12/2024 09/12/2024 All Member
Meeting

Sprint 3
3.7.2 1 09/12/2024 09/12/2024 All Member
Retrospective

4 Sprint 4 10 10/12/2024 19/12/2024 All Member

Sprint Planning
4.1 1 10/12/2024 10/12/2024 All Member
Meeting

Create Sprint
4.2 1 10/12/2024 10/12/2024
Backlog for Sprint 4

Create Test Plan

4.3 1 10/12/2024 10/12/2024
document for Sprint 4

4.4 Design UI 2 11/12/2024 12/12/2024 All Member

4.4.1 Design UI for 1 11/12/2024 11/12/2024

Page | 31
 Project Plan v1.0 - IIJF
Employer registration
Page

Design UI for
4.4.2 Dashboard view Page 1 11/12/2024 11/12/2024
[Employer]

Design UI for
Manage CV and
4.4.3 1 12/12/2024 12/12/2024
Candidate Page
[Employer]

Design UI for
4.4.4 Interview Schedule 2 12/12/2024 12/12/2024
[Candidate]

4.5 Code 5 13/12/2024 17/12/2024 All Member

[Front End] for

4.5.1 Employer registration 1 13/12/2024 13/12/2024
Page

[Front End] for

4.5.2 Dashboard view Page 1 13/12/2024 13/12/2024
[Employer]

[Front End] for

Manage CV and
4.5.3 2 14/12/2024 15/12/2024
Candidate Page
[Employer]

[Front End] for

4.5.4 Interview Schedule 2 16/12/2024 17/12/2024
[Candidate]

4.5.5 [Back End] for 1 13/12/2024 13/12/2024

Employer registration

Page | 32
 Project Plan v1.0 - IIJF
Page

[Back End] for

4.5.6 Dashboard view Page 1 13/12/2024 13/12/2024
[Employer]

[Back End] for

Manage CV and
4.5.7 2 14/12/2024 15/12/2024
Candidate Page
[Employer]

[Back End] for

4.5.8 Interview Schedule 6 16/12/2024 17/12/2024
[Candidate]

4.6 Testing & Fix Bug 1 18/12/2024 18/12/2024 All Member

4.7 Release Sprint 4 1 19/12/2024 19/12/2024 All Member

Sprint 4 Review
4.7.1 1 19/12/2024 19/12/2024 All Member
Meeting

Sprint 4
4.7.2 1 19/12/2024 19/12/2024 All Member
Retrospective
IV. Project's Meeting 1 20/12/2024 20/12/2024 All Member
V. Final Release 1 21/12/2024 21/12/2024 All Member
3.1.4
Project Schedule
The detailed project schedule is available here The Project Schedule is weekly
updated by the Project Manager.
No. Activity Start date Responsible Note
Defect Prevention
1 Sprint 1 27/09/2024 All members
2 Sprint 2 20/10/2024 All members
3 Sprint 3 16/11/2024 All members
4 Sprint 4 09/12/2024 All members

Page | 33
 Project Plan v1.0 - IIJF
Quality Control
1 Review: Work Product 1 Mentor - Team members
2 Review: Work Product 2 Mentor - Team members
3 Review: Work Product 3 Mentor - Team members
4 Review: Work Product 4 Mentor - Team members
Project Tracking
1 Sprint Plan Meeting Mentor - Team members

2 Sprint 1 Review Meeting Mentor - Team members

3 Sprint Plan Meeting Mentor - Team members

4 Sprint 2 Review Meeting Mentor - Team members

5 Sprint Plan Meeting Mentor - Team members

6 Sprint 3 Review Meeting Mentor - Team members

7 Sprint Plan Meeting Mentor - Team members

8 Sprint 4 Review Meeting Mentor - Team members

9 Final Plan Meeting Mentor - Team members

10 Final Release Meeting Mentor - Team members

QA

1 Deliverable 1 Mentor - Team members

2 Deliverable 2 Mentor - Team members

3 Deliverable 3 Mentor - Team members

4 Deliverable 4 Mentor - Team members

5 Baseline audit: Startup Mentor - Team members

6 Baseline audit: Wrap-up Mentor - Team members
3.3 Resource
Specified as in the section Project Team
3.4 Infrastructure

Expected
Work/Product Purpose Note
Availability
Development Environment
Window 10, 11 Operating System Initiation stage
Page | 34
 Project Plan v1.0 - IIJF
Visual Studio Code Source code editor Initiation stage
MongoDB DBMS Initiation stage
Development language
JavaScript Initiation stage
for Web interface
Development language
JavaScript Initiation stage
for Restful API
Development language
Python Initiation stage
for bulding Chatbot
Hardware & Software
4 Personal Laptop Design, Develop and
Initiation stage
Emulate
Other Tools
Git, Github Source version control Definition stage
Postman API Testing Construction stage
Figma UI/UX Design Definition stage
[Link] Diagramming Initiation stage
Jira Task tracking Initiation stage

3.5 Training Plan

Training Area Participants Duration Waiver Criteria

Technical
JavaScript Language All members 7 days If already trained
Detect harmful
All members 10 hrs If already trained
contents
ReactJS All members 10 days If already trained
NodeJS All members 10 days If already trained
Python All members 7 days If already trained
Business domain
Banking All members 2 days
Process
Quality system All members 3 hrs If already trained
Configuration All members 2 hrs If already trained for
Page | 35
 Project Plan v1.0 - IIJF
management (Git and CC. For others, on-the- job
bit bucket tool) training
Group review All members 4 hrs If already trained
Defect prevention All members 4.5 hrs Mandatory
Jira tool All members 1 day If already trained
Agile Scrum All members 2 hrs Mandatory

Page | 36
 Project Plan v1.0 - IIJF

3.6 Finance

No. Criteria Price (USD) Amount Total (USD)

1 Working hour $2 2300 $ 4600
$ 4600

Description Amount Unit

Number of members 4 Person
Number of working per day 4 Hours
Number of workdays per week 5 Days
The cost per member per week 20 USD
The number of working days 100 Days

Explain: Amount of working hours = 4 member * 4 hours * 100 days

4 Project Organization
4.1 Organization Structure
Role Responsibility Name

Scrum Master - Communicate the value of Scrum. Dung,Nguyen

- Teach the organization on Scrum to Dang
maximize business value.
- Preserve the integrity and spirit of the
Scrum framework.
- Serve as a coach and mentor to members of
the Team.
- Respectfully hold the Team, Product
Owners and Stakeholders accountable for
their commitments.
- ContinuAll Membery work with the Team
and business to find and implement
improvements.
- As a timekeeper
- Helping the team agree on what they can
achieve during each development sprint (or
Page | 37
 Project Plan v1.0 - IIJF
another period of time).
- Helping the team continuously make
progress on the project by making sure
each person is working on the right tasks,
helping to remove any obstacles to the team
member’s progress, and protecting the team
from distractions.
- A spokesperson for the customer and needs
to represent them.
- Gathers manages and prioritizes the
product backlog.
Product Cong,Dinh
Owner - Has technical product knowledge or Minh
specific domain expertise.
- Tracks progress towards the release of the
product.
- Responsible for quality
- Responsible for delivering the potential
Membery shippable product of the
Application each sprint.
Developer - Report progress based on the remaining All Member

time.
- Self-organized
- Owns the Sprint backlog
- Guide on the process.
- Monitoring All Member activities of the
Team.
Hoang, Nguyen
Mentor - Help with anything. Thai
- Reviews project documents
- Reviews product

4.2 Project Team

Page | 38
 Project Plan v1.0 - IIJF
Full Name Position
Hoang, Nguyen Thai Mentor
Dung, Nguyen Dang Scrum Master, Dev-team
Cong, Dinh Minh Product Owner, Dev-team
Nghia, Nguyen Duy Dev-team
Huy, Ta Hoang Dev-team

Khoa, Mai Phuoc Dev-team

5 Communication & Reporting

Topic /
Audience / Attendees Frequency Method
Deliverable
Face to Face /
Scrum Master, Zoom Meeting /
Daily meeting Daily
Members
Zalo Chat
Scrum Master, Sprint Planning When starting a
Zoom Meeting
Members Meeting sprint
Scrum Master, Sprint Review When finishing a Face to face, Zoom
Members, Mentor Meeting sprint Meeting
Scrum Master, Sprint When the sprint
Face to Face
Members Retrospective review finish
Face to Face,
Scrum Master, Zoom Meeting,
Individual Meeting When need
Members
Message
Scrum Master, Working report,
Once a week Face to face
Members, Mentor review problems
6 Configuration Management
<Refer to the CM plan or insert here the contents of the CM plan as appropriated>
7 Security Aspects
- The credential data is carefully secured by multi-layer encryption and data
integrity is ensured. Regularly back up system data.
- Research on network attack prevention solutions to ensure data security, avoid
being exploited and stolen data by hackers.
- Deploy project architecture with a high priority in security. Optimized
architectural solutions enable the deployment of data security with 99%
reliability.
Page | 39
 Project Plan v1.0 - IIJF
- Social media, sharing and use of data must be approved by the end user and
verified by the organization's management.
REFERENCES

No Reference item Issued Date Source Note

[Link]
[Link]
resources/w hat-is-agile-what-
is-scrum/
1 Agile Scrum 04-Apr-21
[Link]
agile10 1/
The Scrum Framework by
International Scrum Institute
[Link]
hrl/de velopers_docs/General_So
ftware_Standards.pdf
2 Software Standards 05-Apr-21
[Link]
standard/12 [Link]
[Link]

Page | 40