Coursework

COMP 1807 - Agile Development with SCRUM

Table of Content
A. Section 1: Group Report........................................................................................................ 3
1. Product Vision....................................................................................................................3
2. User Stories & Acceptance Criteria....................................................................................4
3. User Stories Prioritisation with MOSCOW (Epics Breakdown) and MVP(Minimum Viable
Product)................................................................................................................................... 15
4. User Stories Estimation Using Planning Poker.................................................................17
5. Sprint One........................................................................................................................ 21
5.1 Sprint Planning.........................................................................................................21
5.2 Sprinting...................................................................................................................25
6. Sprint Two........................................................................................................................37
6.1 Sprint Planning.........................................................................................................37
6.2 Sprinting...................................................................................................................41
7. Sprint Three..................................................................................................................... 48
7.1 Sprint Planning.........................................................................................................48
7.2 Sprinting...................................................................................................................52
B. Section 2: Individual Report.................................................................................................59
1. Course Impact and Learning............................................................................................59
2. Evaluation of the Scrum Process......................................................................................59
3. Group Contribution Confirmation....................................................................................60
Table of Figure
Figure 1: Product Vision.................................................................................................................3
Figure 2: User Stories & Acceptance Criteria...............................................................................14
Figure 3: MVPs............................................................................................................................. 15
Figure 4: MoSCoW table..............................................................................................................16
Figure 5:User stories Estimation Using Planning Poker...............................................................21
Figure 6: Sprint 1 backlog............................................................................................................ 24
Figure 7: Sprint 1 Use Case Diagram............................................................................................25
Figure 8: Sprint 1 SCRUM Board.................................................................................................. 26
Figure 9: Sprint 1 burndown chart...............................................................................................27
Figure 10: Sprint 1 Review........................................................................................................... 29
Figure 11: Sprint 2 Backlog.......................................................................................................... 40
Figure 12: Sprint 2 Use Case Diagram..........................................................................................41
Figure 13: Sprint 2 SCRUM Board................................................................................................ 42
Figure 14: Sprint 2 burndown chart.............................................................................................43
Figure 15: Sprint 2 Review........................................................................................................... 44
Figure 16: Sprint 3 Backlog.......................................................................................................... 52
Figure 17: Sprint 3 Use Case Diagram..........................................................................................52
Figure 18: Sprint 3 SCRUM Board................................................................................................ 53
Figure 19: Sprint 3 burndown chart.............................................................................................54
Figure 20: Sprint 3 Review........................................................................................................... 56
A. Section 1: Group Report
1. Product Vision

Figure 1: Product Vision

2. User Stories & Acceptance Criteria
Figure 2: User Stories & Acceptance Criteria
3. User Stories Prioritisation with MOSCOW (Epics Breakdown) and
MVP(Minimum Viable Product)
a) Minimum Viable Product

Figure 3: MVPs
b) MoSCoW

Figure 4: MoSCoW table

4. User Stories Estimation Using Planning Poker
Figure 5:User stories Estimation Using Planning Poker

5. Sprint One
5.1 Sprint Planning
5.1.1 Sprint Goal
Create a mobile app with core functionalities such as login/register, display & search bar
for products, deals, accounts management, choose packages and deals, place an order,
and settle bills

5.1.2 Sprint “Definition of Done”

● Users can register on the CheapDeals mobile app and create profiles with personal
information.
● Users can browse and search available packages and deals.
● Users can view and choose packages and deals.

● Users can place orders

● Users can view and amend their profile.

● Users can settle bills in real-time.

● Users can choose default packages and deals

5.1.3 Sprint Backlog
Figure 6: Sprint 1 backlog
5.2 Sprinting
5.2.1 Use Case Diagram

Figure 7: Sprint 1 Use Case Diagram

5.2.2 SCRUM Broad

Figure 8: Sprint 1 SCRUM Board

5.2.3 Burndown Chart

Figure 9: Sprint 1 burndown chart

5.2.4 Sprint Review

● Sprint Goals: Implement core functionalities
+ Key result 1: Complete user registration and login functionalities
+ Key result 2: Enable browsing and searching for available packages and deals
+ Key result 3: Allow users to place orders and settle bills in real-time
● Demos:

Demo Feedback

User Registration The team completed the user registration form UI and
backend logic. The registration mechanism was
seamlessly integrated into the app, allowing users to
register using their personal information

Confirmation Email The confirmation email service was implemented and

tested successfully. Following a successful registration
on the CheapDeals mobile app, users receive timely
confirmation emails, providing a smooth onboarding
experience

Login Functionality The login feature was created, allowing users to

authenticate using their registered accounts. Login
functionality was seamlessly integrated into the app,
allowing users to securely access their accounts

Browsing Packages & Deals The browsing functionality for packages and specials was
demonstrated, and it received great praise for its intuitive
design and smooth performance. Users can quickly
explore the possibilities for their next buy

Package Details View Users could examine extensive information on each

product that met the acceptance requirements. Additional
improvements, such as including visual cues for package
characteristics, were suggested for future revisions

Online Order Placement Users were able to simply place orders using the mobile
app. Feedback emphasized the need for a clear
confirmation message after order submission, which will
be included in the next sprint

Phone Order Functionality The feature for placing orders over the phone was
successfully introduced, allowing users to seek
assistance from the Sales department. The team reviewed
potential optimizations for speeding the verification
process, which will be improved in upcoming sprints

Account Details View The team successfully created the functionality that
allows users to view their account information within the
app. The style was straightforward and user-friendly,
allowing consumers to stay updated on their account
status
Account Information Editing Users could update their account information using the
mobile app if they met the specified prerequisites. The
team emphasized the significance of data validation and
error management in guaranteeing data accuracy and
user satisfaction

Real-time Bill Settlement Users could settle invoices in real-time using the
smartphone app. The team explored adding transaction
history features for improved financial tracking. This will
be investigated in future versions

Default Package Selection Users could select from the company's default packages,
which made it easier to choose. Feedback indicated the
need for clearer descriptions of package features, which
will be addressed in the future sprint

Figure 10: Sprint 1 Review

● Complete task:
+ User registration and login functionalities
+ Browse and search packages/deals functionalities.
+ View package details functionality
+ Place order functionalities.
+ View and manage account functionalities.
+ Choose the default package functionality.
● Upcoming:
+ Refine UI elements based on feedback to enhance user experience.
+ Implement additional features such as transaction history and improved package
descriptions.
+ Conduct thorough testing to ensure the robustness and stability of the app
+ Prepare for Sprint Two by prioritizing backlog items and refining sprint planning
strategies.
5.2.5 Sprint Retrospective
5.2.6 Prototype
6. Sprint Two
6.1 Sprint Planning
6.1.1 Sprint Goal
To improve user experience by implementing additional features such as account
management, customer support, and notifications, while ensuring security and
performance enhancements.

6.1.2 Sprint “Definition of Done”

 Users can efficiently manage their accounts, including updating profile information and
resetting passwords.
 Users can customize their packages and save them for future purchase
 Users can log in via social media accounts
 Users receive timely notifications about new deals, order updates, and important
account activities.
 Customer service representatives have access to tools for assisting users effectively and
securely.
 Customer service representatives can profile customers for target marketing
 Strengthen security measures and optimize performance to provide a smoother and
more secure user experience.

6.1.3 Sprint Backlog

Figure 11: Sprint 2 Backlog
6.2Sprinting
6.2.1 Use Case Diagram

Figure 12: Sprint 2 Use Case Diagram

6.2.2 SCRUM Broad

Figure 13: Sprint 2 SCRUM Board

6.2.3 Burndown Chart

Figure 14: Sprint 2 burndown chart

6.2.4 Sprint Review

● Sprint Goals: Enhance User Experience
+ Key result 1: Enable registration via alternative methods (Google, Facebook,
Twitter, etc.) for improved convenience
+ Key result 2: Implement package filtering options to help users narrow down
their choices effectively
+ Key result 3: Introduce bundled deals functionality to offer users discounted
options
● Demos:

Figure 15: Sprint 2 Review

● Complete task:
+ Enabled registration via alternative methods (Google, Facebook, Twitter, etc.) for
improved convenience
+ Implemented package filtering options to help users narrow down their choices
effectively
+ Introduced bundled deals functionality to offer users discounted options
● Upcoming:
+ Proceed with the implementation of additional features such as account management,
customer support, and notifications.
+ Prioritize the customization of packages and deals to further enhance user experience.
+ Address any issues or feedback received during the sprint review to ensure continuous
improvement in subsequent sprints
6.2.5 Sprint Retrospective
6.2.6 Prototype
7. Sprint Three
7.1 Sprint Planning
7.1.1 Sprint Goal
Finalize all remaining features and functionalities, ensuring that they meet user
requirements and are thoroughly tested, while also completing app documentation,
deployment plans, and testing, and receiving timely responses to user inquiries
submitted

7.1.2 Sprint “Definition of Done”

 Customers can redeem special offers by entering offer codes directly into the app or
clicking on links
 Users can send requests for support, ask questions via the support section, or send the
form
 The CSR can help users create, and modify their accounts through phone calls and track
the effectiveness of the promotion campaign

7.1.3 Sprint Backlog

User Story Task Day Estimation
● Design UI for user
1. As a user, I want to have support section
access to a
comprehensive user ● Compile common
support section within questions and
the application, answers
containing answers to 1
● Implement navigation
common questions, so and search
that I can quickly find functionality
solutions to my inquiries
without needing to
contact customer support

● Design UI for online

2. As a user, I want to have support form
the ability to fill out an
online support form ● Implement form
within the application, submission
allowing me to submit functionality
detailed information ● Integrate a form with
about my inquiry or issue 1
the backend for
if I cannot find a solution communication with
in the frequently asked customer support
questions section,
ensuring efficient
communication with
customer support

● Define a process for 1

3. As a CSR, I want to bring retrieving customer
up an existing customer accounts
account if the caller is a
current customer so that ● Implement search
I can assist them functionality for
efficiently. existing customer
accounts

● Design UI for new

4. As a CSR, I want to create account creation
a new account for new
customers who call to ● Implement backend
1
place an order so that logic for account
they can receive creation
personalized service

● Define the verification

5. As a CSR, I want to ensure process for new
that the verification and accounts
account creation process
is conducted efficiently ● Implement 5
and accurately to provide verification steps for
a positive customer new accounts
experience

● Analyze customer
6. As a customer sales profiles and usage
representative, I want to data
identify opportunities for
creating special offers ● Define criteria for
2
based on customer special offer targeting
profiles so that I can ● Identify potential
enhance customer offer opportunities
satisfaction and loyalty

● Design UI for creating 2

7. As a customer sales special offers
representative, I want the
capability to create and ● Implement backend
configure special offers logic for offer
within the CRM system so configuration
that I can customize ● Integrate offer
offers for specific creation functionality
customers into the CRM system
● Design UI for sending
8. As a customer sales offers
representative, I want the
capability to send special ● Implement sending
offers directly to functionality
2
customers via their app
so that I can deliver
personalized promotions
and incentives

● Define metrics for

9. As a customer sales tracking offer
representative, I want to effectiveness
track the effectiveness of
special offers sent to ● Implement tracking
customers based on their functionality
3
response rates and ● Analyze data and
redemption rates so that evaluate offer success
I can evaluate the success
of the offers and optimize
future campaigns

● Define a process for

10. As a customer, I want the recognizing and
app to recognize and applying codes
automatically apply
special offer codes ● Implement code
included in promotional recognition logic
2
links or campaigns, ● Test code recognition
streamlining the and application
redemption process process

11. As a user, I want to ● Define the process for 3

receive timely responses timely responses to
to my inquiries submitted customer inquiries
through the online
support form within 24 ● Implement code
hours, along with a response logic
confirmation email upon
● Test code response
submitting the form,
process
ensuring that my
concerns are addressed
promptly and efficiently

Figure 16: Sprint 3 Backlog

7.2 Sprinting
7.2.1 Use Case Diagram

Figure 17: Sprint 3 Use Case Diagram

7.2.2 SCRUM Broad

Figure 18: Sprint 3 SCRUM Board

7.2.3 Burndown Chart

Figure 19: Sprint 3 burndown chart

7.2.4 Sprint Review

● Sprint Goals: Finalize Remaining Features
+ Key result 1: Implement a comprehensive user support section within the
application
+ Key result 2: Enable users to fill out an online support form for efficient
communication with customer support
+ Key result 3: Ensure customer sales representatives can efficiently assist users
with account-related tasks and track the effectiveness of promotions
● Demos:
Demo Feedback

The team successfully developed a user assistance

User Support Section component within the app, giving users convenient

access to answers to common questions

Users could submit an online support form, allowing for

Online Support Form quicker connection with customer service to resolve

issues

Customer sales agents could easily bring up current

Customer Account Retrieval
customer accounts, allowing for seamless service

CSRs might set up new accounts for new consumers,

improving individualized service delivery

New Account Creation

The verification and account creation processes were

Verification Process completed swiftly and accurately, resulting in a great

client experience
Customer sales representatives could identify

Special Offer Identification opportunities for creating special offers based on

customer profiles

CSRs could create and configure special offers within

Offer Creation & Configuration
the CRM system, enhancing customization capabilities

CSRs could send special offers directly to customers via

Sending Special Offers their app, delivering personalized promotions and

incentives

The team successfully implemented tracking

Tracking Offer Effectiveness functionality to evaluate the effectiveness of special

offers and optimize future campaigns

The app recognized and automatically applied special

Special Offer Code Recognition offer codes included in promotional links or campaigns,

streamlining the redemption process

Users received timely responses to their inquiries

Timely Response to Inquiries submitted through the online support form within 24

hours, ensuring efficient issue resolution

Figure 20: Sprint 3 Review

● Complete task:
+ The team completed all defined tasks for this sprint
● Upcoming:
+ Proceed with final testing and documentation to ensure readiness for deployment
+ Prepare for app deployment by finalizing deployment plans and conducting thorough
testing
+ Address any remaining issues or feedback received during the sprint review to ensure a
polished and user-friendly application
7.2.5 Sprint Retrospective
7.2.6 Prototype
B. Section 2: Individual Report
1. Course Impact and Learning
After finishing the course and the group project, I feel myself getting better at planning, and
outlining a project via Agile and SCRUM. I think Agile is such a helpful method to ease the
planning process, as well as keep tasks on track. SCRUM is a good model to connect everyone’s
point of view, hence greatly enhancing the final product.

2. Evaluation of the Scrum Process

The team learned valuable lessons from the Scrum process, including the importance of
regular communication, adaptability, and resilience. They successfully implemented user
registration and login functionalities and developed a robust backend system for online orders.
However, challenges with user story estimation and sprint planning led to variability in sprint
velocity and potential impacts on meeting sprint goals. The team also learned new technical
skills and approaches for designing and implementing software solutions. They appreciated the
collaborative nature of the Scrum process, gained insights into agile methodologies, and
learned new technical skills. They lacked clarity and consistency in user story estimation and
sprint planning, which could be addressed by improving estimation techniques and refining the
process.
3. Group Contribution Confirmation
Throughout the whole project, I am confident that I have been a responsible team member.
Some tasks involve the whole team effort such as creating user stories, product vision, and
acceptance criteria... I did my best to explain my point of view, as well as critically evaluate
other’s vision. Regarding individual tasks, I set up goals for each sprint, create their definition of
done, make tasks for each user's stories in the sprint backlog, and create the sprint board and
their corresponding burndown chart. Other than these, I gave feedback regarding the
prototype to ensure the outcome would stick with user’s stories.

Group/Team Name: Group 2

Team member name Student ID Individual overall work Signature

contribution (%)

Bui Binh Minh 001284906 19%

Vu Huy Khai 001284205 14%

Nguyen Khanh Nhat 001284929 14%

Tran Van Duc 001284755 19%

Vu Dinh Tuan Minh 001284907 14%

Nguyen Duc Huy 001285666 19%

Nguyen Ky Anh 001285184 1%

Total 100%