CMU-SE450 Capstone Project I

PRODUCT BACKLOG DOCUMENT

TASK MONITORING ON SMARTPHONE

Submitted by

Thien, Ngo Ngoc

Tin, Tran Trong
Huy, Nguyen Quang
Thinh, Nguyen Huu
Vi, Pham Ha

Approved by
Trinh, Tran Thi Thuy M.Sc.

Proposal Review Panel Representative:

Name Signature Date

Capstone Project 1- Mentor:

Name Signature Date

TMOS(Reminder) Product Back Log Document v1.2

PROJECT INFORMATION

Project
TM
acronym

Project title Task Monitoring on smartphone

01– Sep – 2021 19 – Sep –

Start date End Date
2021

Lead institution International School, Duy Tan University

Trinh, Tran Thi Thuy

Project mentor Email: thuytrinh85@gmail.com

Phone: 0795898823

Partner
Duy Tan University
organization

0705112199
Scrum Master Thien, Ngo Ngoc nnthien.242@gmail.com
0777333794

Product owner Tin, Tran Trong trongtin.tran99@gmail.com 0827342755

Huy, Nguyen Quang quanghuy.f27@gmail.com 0328670814

Team members Thinh, Nguyen Huu nguyenhthinh248@gmail.com 0703496906

Vi, Pham Ha phamhavi255@gmail.com 0326577627

DOCUMENT NAME

Document Title User Story Document

Reminder Team Page 2
TMOS(Reminder) Product Back Log Document v1.2

Vi, Pham Ha
Author(s)
Thinh, Nguyen Huu
Role Product Owner, Team Member, Scrum Master
[TMOS]Product Backlog-
Date November 10th, 2020 File name:
ver1.2.docx
URL
Access Project and CMU Program

REVISION HISTORY

Version Person(s) Date Description

Proceeding to
Vi, Pham Ha
1.1 August 28, 2020 Product Backlog
Thinh, Nguyen Huu
Document
Proceeding to
1.2 Vi, Pham Ha November 12, 2020 Product Backlog
Document

Reminder Team Page 3

TMOS(Reminder) Product Back Log Document v1.2

SIGNATURE
Document Approvals: The following signatures are required for approval of this document.
Signature:
Mentor Trinh, Tran Thi Thuy
Date:

Signature:
Project Leader Thien, Ngo Ngoc
Date:

Signature:
Product Owner Tin, Tran Trong
Date:

Signature:
Huy, Nguyen Quang
Date:

Signature:
Team Member(s) Thinh, Nguyen Huu
Date:

Signature:
Vi, Pham Ha
Date:

Reminder Team Page 4

TMOS(Reminder) Product Back Log Document v1.2

Table of Contents
1. Introduction 6
1.1. Purpose 6
1.2. Scope 6
2. Product backlog 7
2.1. Product Backlog Items Diagram 7
2.2. Product Backlog Specification 7
2.3. Break down into Sprint Backlog 8
3. Constraint 10
4. Stack holders and user descriptions summary 10
5. References 11

Reminder Team Page 5

TMOS(Reminder) Product Back Log Document v1.2

1. Introduction
The agile product backlog in Scrum is a prioritized features list, containing short
descriptions of all function desired in the product. When applying Scrum, it’s not
necessary to start a project with a lengthy, upfront effort to document all requirements.
Typically, a Scrum team and its product owner begin by writing down everything they
can think of for agile backlog prioritization. This agile product backlog is almost always
more than enough for a first sprint. The Scrum product backlog is then allowed to grow
and change as more is learned about the product and its clients.
1.1. Purpose

− Provide a prioritized features list, containing a short description of all functions

desired in the product.

− Lists everything that the product owner and Scrum team feels should be included

in the software they are developing.

1.2. Scope

− List the user’s role.

− Write all the user’s requirements.

− List some main function of system.

− Short description of all the function desired in the product.

− Given the priority of each feature and function of the product.

Reminder Team Page 6

TMOS(Reminder) Product Back Log Document v1.2

2. Product backlog
2.1. Product Backlog Items Diagram

Figure 1. Product Backlog Items Diagram

2.2. Product Backlog Specification
Table 1. Product Backlog Specification
As
ID Theme I want to So that Priority
a/an

AUTHENTICATION
Access to the
I can use the system with
PB01 Login User system by my High
my role
account
Forgot Retrieve my
PB02 User I can access my account. High
Password password
Change Change my
PB03 User I can change my password High
Password Password
PB04 Logout User Log out of the I can stop using the High

Reminder Team Page 7

TMOS(Reminder) Product Back Log Document v1.2

system. I can login after I

system want to use the system
next time.

REGISTER
Register a new
PB05 Register User I can access the system. High
account

CREATE GROUP TASK

Create a I can create a group of the
PB06 User Create a group task High
Group Task tasks to do.

ADD MEMBER
Add Add members to Members can access the
PB07 User High
member the group group with their roles.

MANAGE TASKS
Add tasks that I can add title, description
PB08 Add Tasks User High
should be reminder and time of task.
Edit tasks that I can edit title, description
PB09 Edit Tasks User High
should be reminder and time of task
Delete Delete tasks that I can delete the task that I
PB10 User High
Tasks should be reminder want to delete

Search Search tasks in the

PB11 User I can search the task I need Low
Tasks tasks list

Be Reminder I can receive notification

PB12 Reminder User High
about the task of the task at the time
Comment on the I can give comments on
PB13 Comment User Low
tasks tasks
Set the status of I can set the status for the
PB14 Set State User Low
the tasks task as done or not.

Reminder Team Page 8

TMOS(Reminder) Product Back Log Document v1.2

CHATBOT
I can then chat with the
PB15 Chatbot User Use Chatbot High
members

SETTING
I can set font size,
PB16 Setting User Setting the system notification sound, dark Medium
and light mode.

NOTIFICATION
Get notified about I can receive notifications
PB17 Notification User activities in the when actions affect the High
board tasks in the board.

VIEW APPLICATION INFORMATION

I can view the privacy
View the View the
policy and the terms &
PB17 application User application Low
conditions of the
information information
application

Table 2: Priority impact description

Impact Description
1 Very high Must have
2 High Should have
3 Medium Could have
4 Low Won’t have

2.3. Break down into Sprint Backlog

Table 3. Breakdown into Sprint Backlog

No Task Name Time Duration Start

1 Initial 300 12 10/08/2020

Reminder Team Page 9

TMOS(Reminder) Product Back Log Document v1.2

1 Gathering Requirement 125 5 19/08/2020

1.1 Create Proposal Document 175 7 12/08/2020

2 Start Up 400 16 24/08/2020

2.1 Create documents for project 375 15 24/08/2020

2.1 Project’s Kick-off Meeting 25 1 28/08/2020

3 Development 1925 77 10/09/2020

3.1 Sprint 1 700 28 10/09/2020

3.2 Sprint 2 700 28 12/10/2020

3.3 Sprint 3 525 21 13/11/2020

4 Project’s Retrospective Meeting 25 1 04/12/2020

5 Final Release 25 1 05/12/2020

Duration 2675 (hours) 107 (day)

3. Constraint

Table 4. Constraint
Constraint Condition
Project completion time limit in 4 months so time to complete
Time
project be restricted
People constraint 5 people working together to finish the project
The integrated system Must be connected to Internet network to operate
Requirements According to Product owner’s Requirements

4. Stakeholders and user descriptions summary

Reminder Team Page 10

TMOS(Reminder) Product Back Log Document v1.2

Table 5. Stakeholders and User Descriptions Summary

Name Description
The Person who give the
Product Owner Requirement
This is the stakeholder
who leading, manage the
Scrum Master
system development
Team
This is a stakeholder that
works with the Analysts
Requirement to correctly translate
Analyzer requests or needs into
requirements to be used
for design
This is a stakeholder that
Software is primary for leading the
Architect system development
This is a stakeholder that
Coder
programs the software
Role
Provide information to develop the
system. Make the decision to accept and
implement the project, do the unit test
Controlling, managing, monitoring,
make sure the project complete on time,
within budget, according to plan and
according to requirements
Specifies the details of one or more a
part of the system’s functionality by
describing one or the aspects of the
requirements,
This will include functional and non-
functional
Responsible for the software
architecture, which includes the key
technical decisions that constrain the
overall design for the project
Implement the project

5. References

Table 6. References
No Reference Note

Reminder Team Page 11

TMOS(Reminder) Product Back Log Document v1.2

https://www.mountaingoatsoftware.com/agile/scrum/scrumtools/ How to create

1
product-backlog product backlog

https://geekbot.com/blog/project-management-tools-that-everyscrum-
master-should-use/?
k_id=dsa19959388920&adgroup_id=73039967424&campaign_name_
Product Backlog
2 ad=16
Example
97251819&gclid=Cj0KCQjwO35BRDVARIsAJU5mQXZaCllFo0HA
y0caiIZN7odW2A5c2v34l8maRp bTxUrvAWgoOz-
0GEaAhN8EALw_wcB

Reminder Team Page 12