CAPSTONE PROJECT REPORT

Report 2 – Project Management Plan

– DaNang, August 2022–

1
Table of Contents
I. Record of Changes 3
II. Project Management Plan 4
1. Overview 4
1.1 Scope & Estimation 4
1.2 Project Objectives 4
1.3 Project Risks 4
2. Management Approach 4
2.1 Project Process 5
2.2 Quality Management 5
2.3 Training Plan 5
3. Project Deliverables 6
4. Responsibility Assignments 6
4.1 Team & Structures 6
4.2 Roles & Responsibilities 6
5. Project Communications 7
6. Configuration Management 7
6.1 Document Management 7
6.2 Source Code Management 8
6.3 Tools & Infrastructures 9

2
I. Record of Changes
Date A* In Change Description
M, D charge
07/06/2022 A All First Version of Project Management Plan

*A - Added M - Modified D - Deleted

3
II. Project Management Plan
1. Overview
1.1 Scope & Estimation
Work Breakdown Structure (WBS) contains the project scope carried out by the project team,
as well as the amount of effort required to achieve the deliverable. The WBS.xlsx is attached
with Report2_Project Management Plan
1.2 Project Objectives
The Project’s Objective revolves around main goals:

- Pass the Capstone Project

- Enhance project development and management as well as communication skills
- Learn technical skills and new technologies to build a good foundation for future work
- Learn how to manage source code through Git and GitLab

1.3 Project Risks

# Risk Description Impact Possibility Response Plans
Not familiar with High High Self-study and meet to explain each
1
new technologies Impact Possibility other
Inexperience in
High High Communicate and learn from
2 running a real
Impact Possibility experienced people
project
Difficulty in
Regular meetings, Daily Stand-up
project
High High to evaluate the situation
3 management
Impact Possibility Divide the complicated tasks into
time between
different parts
members

2. Management Approach
In this project, we apply Waterfall combined with daily report, weekly meetings.

4
 2.1 Project Process

2.2 Quality Management

Approach Description
1 Unit Testing Process unit test each function
2 Integration Testing Process testing each future
3 System Testing Process testing after combine api and interface
4 Reviewing Cross view and group review
2.3 Training Plan
Training Area Participants When, Duration Waiver Criteria

Java Spring Boot All members 19/05/2022 Mandatory

Git, Github All members 01/06/2022 Mandatory

ReactJS,Bootstrap All members 16/05/2022 Mandatory

Setup code structure All members 01/06/2022 Mandatory

Azure All members 21/05/2022 Mandatory

Docker All members 27/05/2022 Mandatory

WEB RTC All members 02/06/2022 Mandatory

FireBase All members 06/06/2022 Mandatory

Mysql All members 07/06/2022 Mandatory

VN Pay API All members 08/06/2022 Mandatory

5
3. Project Deliverables
# Deliverable Due Date Notes
Project
1 Introduction 13/06/2022 Report 1 – Project Introduction
Report

Project Report 2 – Project Management Plan, WBS,

2 23/06/2022
Management Plan Project Schedule

Report 4 – System Design, Database Design,

3 Software Design 12/08/2022
Detailed Design
4 Code Package 10/08/2022 Code, Test Cases and Test, Documentation

Software
User requirements, Functional Requirements,
5 Requirement 11/08/2022
Use case, Wireframe
Specification

Software User
6 12/08/2022 Release Packet & User Guide
Guides
7 Final Package 14/08/2022 Full code, final reports & documents

4. Responsibility Assignments
4.1 Team & Structures

6
4.2 Roles & Responsibilities
Role Description
Mentor Monitoring project
Planning, executing, monitoring, controlling and
Project Manager
closing project
Translating and synthesising each member's reports
Document Leader
into a complete document
Write the report document that the leader has
Document Member
proposed
Responsibility for design system architecture,
Development Leader
technology, coding
Development Member Responsibility to develop a project
Testing Leader Making test decisions to ensure product quality
Testing Member Create test cases, test documents and test

5. Project Communications
Communication Type, Tool,
Who/ Target Purpose When, Frequency
Item Method(s)
Report daily work, new 22:00
Daily Stand-up All members In school
task, and issues Everyday
All member + 17:30
Weekly meeting Track team progress In school
mentor Every Thursday

6. Configuration Management
6.1 Document Management
Document workplace: use GoogleDrive to work

Source Storage: use GitLab to manage the project all document of the project

Baseline: This is the own the documented has been all the per testers

Management Document: This is the place where the team's revenue and expenditure documents are
stored during the project's work

References: This is where references from various sources are stored

WIP: This is where documents are in progress or only partially completed

7
6.2 Source Code Management
In the project, we use GitLab to work and manage the source code. Gitlab is a powerful tool for
source code management, conflict avoidance, and easy tracking.

8
Team uses GitFlow to let members follow when using Git. In the case where many developers are
involved in the development of the project for a long time, but if the operating rules are not agreed
upon and decided upon, it is normal to have conflicts or omissions when merging. Therefore, to
minimise omissions when using Git, it is necessary to take care of Git Flow.

+ In this project, we have the main branch of the project as master và the developer branch as
developer branch as develop which is managed by Leader.
+ When there is a new feature to build, it will create a feature branch from the develop branch
for development and when it needs to fix a bug, it will create a branch named fix bug +
feature name.
+ When all is done it will be pushed and the Leader will check and merge the code into the
master. Code from the develop branch will be merged into master when the product from
the develop branch does not have any bugs.
+ In case the error is discovered after use, it will create a branch named hot fix with an error
name to fix the error and after completion, it will merge into master and develop.
+ When new members join, they will take the code from the develop branch to develop.

Watch Full:: Here

6.3 Tools & Infrastructures
Category Tools / Infrastructure

9
Technology ReactJS (FrontEnd), Java/SpringBoot (BackEnd)
Database MySQL, FireBase
IDEs/Editors Visual Studio Code
Diagramming DrawIO
Design Figma, Photoshop
Documentation Google Docs/Sheets/Slides
Version Control GitLab (Source Codes), Google Drive (Documents)
Deployment Server Azure
Project Management Google Sheets(Schedule, Defects)

10