MINISTRY OF EDUCATION AND

TRAINING

FPT UNIVERSITY

Capstone Project Report

Report 2 - Project Management Plan
HighschoolQuest- Interactive Role-Playing Game

Group GFA23SE35
Nguyễn Minh Quân – SE151005
Trần Khắc Đại – SE150681
Group Members
Nguyễn Minh Phúc – SE150984
Trịnh Tâm – SE151037
Supervisor Mr. Lâm Hữu Khánh Phương

Capstone Project code FA23SE035

- Ho Chi Minh City, 06/09/2023-

Project Management Plan

1. Overview
1.1. Scope & Estimation
WBS Item Complexi Est. Effort
#
ty (man-days)
1 Feature 1 21

1.1 Function 1.1 Simple 4

1.2 Function 1.2 Medium 7

1.3 Function 1. N Complex 10

1.2. Project Objective

Testing Stage Test Coverage No. of Defects % of Defect Not

Reviewing

Unit Test

Integration Test

System Test

Acceptance Test

1.3. Project Risk

Risk Description Possibili Impact Response Plans

#
ty
1 Missing Medium High Meet the mentor each week to confirm the
requirement flow and the logic of the project.
2 Team member Medium High By communicating regularly with your team
leaving members, you can ensure that everyone is
on the same page and that any issues or
concerns are addressed promptly.
3 Low productivity Medium Medium Creating a well-paced project plan to lower
stress and avoid burnout, communicating
effectively about project details and
problems.
4 Technical Error High High Create clear and succinct code, Test code
frequently, and resolve bugs and logical
errors when they’re found.
5 Project out of Medium Medium Communicate to team members to clearly
scope define project requirements and goals to
 make sure everyone understands the
process.

2. Management Approach
2.1. Project Process

Figure 1: Scrum Sprints [The Top 8 Benefits of Choosing Scrum Software (rezaid.co.uk)]

We use the Scrum of Agile Software Development Model in developing MSQuest

because it brings some benefits:
● Developing the project in sprints, Scrum provides more opportunities to test,
sort out problems, and solve them.
● Defines and elaborates on the project requirements in a timely manner to
develop a relevant, high-quality product.
● Scrum development teams can control project performance and make
amendments as every sprint provides a number of opportunities to the entire
project team.
● While developing Scrum software, each team member has the opportunity to
know how the project is progressing. This allows the team to correctly
identify any potential issues and track how things are going. Transparency at
each stage helps in organizing, planning, and improving the project.
 2.2. Quality Management
Our team has implemented a comprehensive approach to guarantee that the project
adheres to the necessary standards. The approach consists of a series of tests,
namely: unit test, integration test, and system test. Should any errors, bugs be
detected during the testing phase, our team of developers will promptly resolve
them. To ensure the system's integrity, we conduct acceptance testing.

2.3. Training Plan

Participants When, Duration Waiver

Training Area
Criteria
Blender Minh Quân Start at 06/09/2023 Mandator
y
Unity flow Khắc Đại, Minh Phúc Start at 20/09/2023 Mandator
y
Test All members Start at 30/10/2023 Mandator
y

3. Project Deliverables
ID Deliverable Predecessor
1 Phase 1
1.1 Milestone: Initiating
1.1.1 Create Project charter
1.1.2 Get the project charter approval 1.1.1 FS
1.1.3 Kick-off meeting 1.1.2 FS
1.1.4 Create stakeholder register 1.1.3SS
2 Phase 2
2.1 Milestone 2: Planning
2.1.1 Create Scope management plan
2.1.2 Create Time management plan 2.1.1 SS
2.1.3 Create Cost management plan 2.1.1SS
2.1.4 Create Risk management plan 2.1.1SS
2.1.5 Meeting with the team to discuss about plan
2.1.6 Deliver project management plan
3 Phase 3
3.1 Milestone 3: Executing
3.1.1 Iteration 1
3.1.1.1 Analysis
a. Create feasibility report
b. Create use-case diagram and use-case description
c. Create SRS documentation
3.1.1.2 Design
a. Create design for wireframe
b. Create UI / UX design
c. Create mock-up screen
 3.1.1.3 Implementing
a. Implement coding for authentication feature
b. Implement coding for user management controller
3.1.1.4 Testing
a. Perform unit testing
b. Perform integration testing
c. Perform part of system testing
3.1.2 Iteration 2
3.1.2.1 Analysis
a. Update feasibility report
b. Update use-case diagram and use-case description
c. Update SRS docs
3.1.2.2 Design
a. Update design for wireframe
b. Update UI/UX design
c. Update mock-up screen design
3.1.2.3 Implementing
a. Implement coding for ban user feature
b. Implement coding for admin role
3.1.2.4 Testing
a. Perform unit testing
b. Perform integration testing
c. Perform part of system testing
3.1.3 Iteration 3
3.1.3.1 Analysis
a. Update feasibility report
b. Update use-case diagram and use-case description
c. Update SRS docs
3.1.3.2 Design
a. Update design for wireframe
b. Update UI/UX design
c. Update mock-up screen design
3.1.3.3 Implementing
a. Implement coding for creating admin feature
b. Implement coding for learning path management
controller
3.1.3.4 Testing
a. Perform unit testing
b. Perform integration testing
c. Perform part of system testing
3.1.4 Iteration 4
3.1.3.1 Analysis
a. Update feasibility report
b. Update use-case diagram and use-case description
c. Update SRS docs
3.1.3.4 Design
a. Update design for wireframe
b. Update UI/UX design
c. Update mock-up screen design
3.1.3.5 Implementing
a. Implement coding for creating character feature
 b. Implement coding for guiding feature
3.1.3.4 Testing
a. Perform unit testing
b. Perform integration testing
c. Perform system testing
d. Perform acceptance testing
4 Phase 4
4.1 Milestone: Monitoring and controlling
4.1.1 Control scope
4.1.2 Track progress 4.1.1SS
4.1.3 Perform cost control 4.1.2SS
4.1.4 Monitor and control risk 4.1.3SS
5 Phase 5
5.1 Milestone: Closing
5.1.1 Summarize feedback and draw on experience
5.1.2 Create project final report
5.1.3 Giving project development directions in the future
5.1.3 Delivering the product and ending the project

4. Responsibility Assignment
Responsibility daitkse150681 quannmse151005 phucnmse150984 tamtse151037

Project Planning & R D S S

Tracking

Setting up front-end code R R D S

Setting up back-end code R R D S

Create ERD Diagram S D S S

Write Project Document - D R R R

Project Introduction
(Report 1)

Write Project Document - D R R R

Project Management Plan
(Report 2)

Write SRS Document D S S S

Release package & user R D S D

guild

Game Application S D R R
Develop

Create use case diagram D S R R

Write SDD Document D S S S

Create final document D R R R

Web Application Develop R R D D

5. Project Communication
Communication Who/ Target Purpose When, Type, Tool, Method(s)
Item Frequency
Daily Texting All team Check individual tasks Everyday Discord, Messenger
members and troubleshooting.
Weekly All team Review tasks, assign new Every Discord
meeting members tasks, confirm meeting Week
times with mentor,
discuss solutions, and
plan for the development
process.
Mentor All team Mentor reviews project Every Offline at FPT
meeting members, features, functions, Week University HCM or
mentor database, and code flow. Student Culture
Give suggestions for the House in HCM city.
team to improve project
quality

6. Configuration Management
6.1. Document Management
We use Google Drive to store all project documents, including text documents,
spreadsheets, and presentations. We make use of Google Docs and Google Sheets to
edit and modify these documents. The individual responsible for preparing the
project documents will share them with team members, granting them permission
to edit and contribute. This allows us to collaborate effectively and efficiently on
projects, regardless of our physical location. Google Drive also provides a secure and
reliable way to store our project documents, ensuring that they are always
accessible when we need them.

6.2. Source Code Management

Our team uses GitHub as our platform for source code management. A chosen
representative will create the GitHub Repository and oversee the code’s
management. Each team member, based on their role (e.g., front-end, back-end),
will establish their branch for coding. This allows team members to work on their
respective parts of the project without interfering with each other’s work.
 Once all branches are complete, they will be reviewed and verified by the manager.
The manager will then merge them into the main branch. This ensures that all code
is thoroughly reviewed and tested before it is merged into the main branch.
GitHub provides a secure and reliable way to manage source code, allowing team
members to collaborate effectively and efficiently on projects, regardless of their
physical location. It also provides a range of tools and features that can help
streamline the development process, such as version control, issue tracking, and pull
requests.

6.3. Tools & Infrastructures

Category Tools / Infrastructure

Technology Angular, Typescripts, HTML CSS (FrontEnd), Unity (Game),

ASP.NET (BackEnd)

Database SQL Server Management Studio ( SSMS )

IDEs/Editors Visual Studio Code, Visual Studio 2022, Unity, Blender

Diagramming Lucidchart, DrawIO

Documentation MS Office, Google Docs/Sheets/Slides, Canva

Version Control GitHub (Source Codes), Google Drive (Documents)

Deployment server Swagger

Project management ProjectLibre (Schedule), GitLab (Tasks, Defects)