AGILE DEVELOPMENT WITH SCRUM

(COMP1807)

Team Members:

Chia Teik Hua (001246861)

Tan Sha'o He'ng (001227082)

Ooi Kai Ze (001234342)

Cheong Yik Liang (001236429)

Intake: January 2022

Lecturer: Ms. Annida Said .

Table of Contents
1. Product Vision ........................................................................................................................... 1
2. List of Requirements................................................................................................................. 2
2.1 Product Backlog .................................................................................................................... 2
2.2 User Stories ............................................................................................................................ 6
3. MoSCoW and Minimum Viable Product ............................................................................. 16
3.1 MoSCoW.............................................................................................................................. 16
3.2 Minimum Viable Product ................................................................................................... 17
4. Planning Poker ........................................................................................................................ 18
5. Sprints ...................................................................................................................................... 23
5.1 Sprint 1................................................................................................................................. 23
5.1.1 Sprint Planning Phase ................................................................................................ 23
5.1.1.1 Sprint Goal .............................................................................................................. 23
5.1.1.2 Definition of Done ................................................................................................... 23
5.1.1.3 Sprint Backlog ......................................................................................................... 24
5.1.2 Sprinting Phase ........................................................................................................... 27
5.1.2.1 Use Case Diagram ................................................................................................... 27
5.1.2.2 Scrum Board............................................................................................................ 28
5.1.2.3 Burndown Chart ..................................................................................................... 30
5.1.3 Sprint Review .............................................................................................................. 31
5.1.4 Sprint Retrospective ................................................................................................... 47
5.2 Sprint 2................................................................................................................................. 48
5.2.1 Sprint Planning Phase ................................................................................................ 48
5.2.1.1 Sprint Goal .............................................................................................................. 48
5.2.1.2 Definition of Done ................................................................................................... 48
5.2.1.3 Sprint Backlog ......................................................................................................... 49
5.2.2 Sprinting Phase ........................................................................................................... 52
5.2.2.1 Use Case Diagram ................................................................................................... 52
5.2.2.2 Scrum Board............................................................................................................ 53
5.2.2.3 Burndown Chart ..................................................................................................... 55
5.2.3 Sprint Review .............................................................................................................. 56
5.2.4 Sprint Retrospective ................................................................................................... 63
5.3 Sprint 3................................................................................................................................. 64
5.3.1 Sprint Planning Phase ................................................................................................ 64
5.3.1.1 Sprint Goal .............................................................................................................. 64
5.3.1.2 Definition of Done ................................................................................................... 64
 5.3.1.3 Sprint Backlog ......................................................................................................... 65
5.3.2 Sprinting Phase ........................................................................................................... 67
5.3.2.1 Use Case Diagram ................................................................................................... 67
5.3.2.2 Scrum Board............................................................................................................ 68
5.3.2.3 Burndown Chart ..................................................................................................... 70
5.3.3 Sprint Review .............................................................................................................. 71
5.3.4 Sprint Retrospective ................................................................................................... 72
6. References ................................................................................................................................ 73
7. Pro-forma................................................................................................................................. 74
1. Product Vision
For Passenger from all walk for life
Who Travelling from place to place with the help of a caring car booking
companies.
Product Name Online Car Booking Service & Mobile Application Car Booking
Service
Product Car booking service
Category
That Is user friendly and easy to reach as well as satisfy customer service
requirement.
Unlike Classic taxi service which is inconvenient to reach and get their service.
Our product Keeps track on loyal customers therefore special offer or promotion will
be given to loyalty customer.

Table 1: Product Vision

Page 1 of 74
2. List of Requirements
2.1 Product Backlog
Index Product Backlog
1. Register and Login
2. Make Enquiry
3. Online Booking
4. Make Payment
5. Review and Feedback
6. Customer Service
7. Access Data from System

Table 2: Product Backlog

Page 2 of 74
Index User Story Estimation Priority
As a customer, I want to register an account with
1. relevant information so that I am able to create a new 3 Must-1
account in order to surf the website or application.
As a customer, I want to get verified by the system so
2. that I am managing to fully experience the services and 2 Must-2
features provided by the website.
As a customer, I want to login into my personal
account by using registered email so that the activity
3. and purchase that the I have made and carried out are 2 Must-3
recorded in the system and I am able to review back
the purchase history.
As a customer, I want to register credit card details
4. with the system so that I can make payment easily with 1 Must-4
a registered credit card in the system.
As a customer, I want to send my enquiry through the
5. system so that my feedback and doubts are able to be 1 Must-5
exposed to the Call Centre Staff.
As a customer, I want to receive the replies from Call
6. Centre Staff so that I can get responses or help from 1 Must-6
Call Centre Staff regarding the enquiry sent before.
As a customer, I want to access main menu after login
7. so that I can browse any service that is provided by the 5 Must-7
site.
As a customer, I want to search for particular service
8. using tools such as search bar so that I can find my 3 Must-8
desired service faster.
As a customer, I want to place booking so that provide
9. personal information for system to record and make a 2 Must-9
booking.
As a customer, I want to receive a confirmation email
10. concerning booking placed so that I can ensure that my 2 Must-10
booking has been successfully placed.

Page 3 of 74
 As a system, I want to inform customer 10 to 15
11. minutes before expected time of arrival so that 8 Must-11
customers can get notified and prepare themselves.
As a customer, I want to amend or cancel the booking
24 hours prior to intended journey so that I can change
12. 8 Should-1
the type of cabs or cancel my booking if there is no
need anymore.
As a customer, I want to get a 15% discount so that I
13. 3 Could-1
can get a cheaper price to pay for selected service.
As a customer, I want view the total amount of the
14. booking fee so that I consent about how much I have 2 Must-12
to pay for that particular service.
As a system, I want to verify the credit card details
15. entered by customer so that the payment will be 2 Must-13
credited by that respective credit card holder.
As a customer, I want to choose any of the payment
16. method from available options so that I can pay with 8 Should-2
my preferred payment method.
As a customer, I want an on-line receipt after payment
17. made so that the on-line receipt can serve as future 2 Must-14
reference for any purposes.
As a system, I want verify the special offer code so that
18. only valid offer code will be accepted and apply ½ Could-2
discount on amount of payment.
As a user, I want leave review after completion of
19. journey so that other users can view the comments for 2 Should-3
that particular service.
As a user, I want leave star rating after completion of
20. journey so that other users can view the star rating for 2 Should-4
that particular service.
As a Call Centre staff, I want to perform identification
21. ½ Should-5
of the person calling so that I am able to identify if the

Page 4 of 74
 person calling is an existing user and provide further
assistance if that person is one of the registered users.
As a Call Centre staff, I want to create a new account
22. for new user so that new users will have a new account 1 Should-6
ready for use after calling us.
As a Call Centre staff, I want to reply the enquiries sent
23. by the users so that the users are able to get answers for ½ Must-15
their seek from us.
As a Call Centre staff, I want to access the list of mini
24. cabs so that I am able to check prices and availability 2 Should-7
accordingly.
As a Call Centre staff, I want to access the list of
25. drivers so that I am able to check prices and availability 2 Should-8
accordingly.
As a system, I want to keep track of different
26. information so that various types of useful information 8 Must-16
can be retrieved and it can be used to produce a report.
As a system, I want to send recommendations
27. regarding special offers so that the users can enjoy 5 Could-3
more offers in placing order while using our platform.

Table 3: User Stories

Page 5 of 74
2.2 User Stories

Story ID: 1 Story Title: Registration of account by email address

User Story: Importance:

As a: Customer

I want: To register an account with relevant information Must-1

So that: I am able to create a new account in order to surf the website or

application.

Estimate:

Type:
Acceptance Criteria:

☒ Register and
And I know I am done when:
Login
a) I am able to view the registration form. ☐ Make Enquiry
b) I am able to fill in the registration form.
☐ Online
c) An error message will prompt me if any of the required fields is Booking
empty. ☐ Make Payment
d) A message prompted me that my registration form has been
☐ Review and
submitted successfully. Feedback
☐ Customer
Service
☐ Access Data
from system

☐ Review and

Page 6 of 74
 Story ID: 3 Story Title: Login by email

User Story: Importance:

As a: Customer

I want: To login into my personal account by using registered email Must-3

So that: The activity and purchase that the I have made and carried out
are recorded in the system and I am able to review back the purchase
history.
Estimate:

Type:
Acceptance Criteria:

☒ Register and
And I know I am done when:
Login
a) I am able to view the login interface. ☐ Make Enquiry
b) I am able to enter all essential details in order to login.
☐ Online
c) An error message will prompt me if any of the required fields is Booking
empty or incorrect. ☐ Make Payment
d) A message prompted me to login successfully.
☐ Review and
Feedback
☐ Customer
Service
☐ Access Data
from system

☐ Review and

Page 7 of 74
 Story ID: 5 Story Title: Send enquiry

User Story: Importance:

As a: Customer

I want: To send my enquiry through the system Must-5

So that: My feedback and doubts are able to be exposed to the Call

Centre Staff.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to view the enquiry form. ☒ Make Enquiry
b) I am able to enter details of enquiry.
☐ Online
c) An error message will prompt me if any of the required fields is Booking
empty. ☐ Make Payment
d) A message prompted me that my enquiry form has been
☐ Review and
submitted successfully. Feedback
☐ Customer
Service
☐ Access Data
from system

☐ Review and

Page 8 of 74
 Story ID: 9 Story Title: Provide essential information upon placing
booking

User Story: Importance:

As a: Customer

I want: To place booking Must-9

So that: Provide personal information for system to record and make a

booking

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to view the form which required all the essential ☐ Make Enquiry
information as mentioned. ☒ Online
b) I am able to fill in the form. Booking
c) An error message will prompt me if any of the required fields is ☐ Make Payment
empty.
☐ Review and
d) A message prompted me that my booking has been placed Feedback
successfully.
☐ Customer
Service
☐ Access Data
from system

☐ Review and

Page 9 of 74
 Story ID: 13 Story Title: 15% of discount for online booking
address

User Story: Importance:

As a: Customer

I want: To get a 15% discount Could-1

So that: I can get a cheaper price to pay for selected service.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to place an on-line booking. ☐ Make Enquiry
b) I am able to get a 15% discount available for online booking. ☐ Online
c) I am able to see my payment get a discount by 15%. Booking
d) I am able to pay for the discounted price. ☒ Make
Payment

☐ Review and
Feedback
☐ Customer
Service
☐ Access Data
from system

Page 10 of 74
 Story ID: 16 Story Title: Accepts other payment methods
address

User Story: Importance:

As a: Customer

I want: To choose any of the payment method from available options Should-2

So that: I can pay with my preferred payment method.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to view the list of available payment methods. ☐ Make Enquiry
b) I am able to choose one of the payment methods provided.
☐ Online
c) I am able to pay by using the chosen payment method. Booking
d) I am able to change the payment method after selecting one in ☒ Make
the list. Payment

☐ Review and
Feedback
☐ Customer
Service
☐ Access Data
from system

Page 11 of 74
 Story ID: 19 Story Title: User leave review after completion of journey
address

User Story: Importance:

As a: User

I want: Leave review after completion of journey Should-3

So that: Other users can view the comments for that particular service.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to choose an order to review. ☐ Make Enquiry
b) I am able to input the content of the review.
☐ Online
c) I am able to submit a review. Booking
d) A message prompted me that my review has been submitted ☐ Make Payment
successfully.
☒ Review and
Feedback
☐ Customer
Service
☐ Access Data
from system

☐ Review and

Page 12 of 74
 Story ID: 22 Story Title: Call Centre Staff create a new account
address for new user

User Story: Importance:

As a: Call Centre staff

I want: To create a new account for new user Should-6

So that: New users will have a new account ready for use after calling
us.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to input the details of registration for creating an ☐ Make Enquiry
account.
☐ Online
b) An error message prompted me if any details were incorrect or Booking
did not obey the rules. ☐ Make Payment
c) I am able to create a new account for new users.
☐ Review and
d) A message prompted me that the new registration of the account Feedback
has been done successfully.
☒ Customer
Service
☐ Access Data
from system

☐ Review and

Page 13 of 74
 Story ID: 23 Story Title: Call Centre Staff reply enquiry of customer
address through email

User Story: Importance:

As a: Call Centre staff

I want: To reply the enquiries sent by the users Must-15

So that: The users are able to get answers for their seek from us.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to view the list of enquiries sent by users. ☐ Make Enquiry
b) I am able to input the content of reply towards particular enquiry.
☐ Online
c) I am able to submit a reply of enquiry to the user. Booking
d) The user receives their reply through email. ☐ Make Payment

☐ Review and
Feedback
☒ Customer
Service
☐ Access Data
from system

☐ Review and

Page 14 of 74
 Story ID: 24 Story Title: Call Centre Staff access all mini cabs
to check address
prices and availability

User Story: Importance:

As a: Call Centre staff

I want: To access the list of mini cabs Should-7

So that: I am able to check prices and availability accordingly.

Estimate:

Type:
Acceptance Criteria:

☐ Register and
And I know I am done when:
Login
a) I am able to view the list of mini cabs. ☐ Make Enquiry
b) I am able to view the name of the mini cab.
☐ Online
c) I am able to view the prices of mini cabs. Booking
d) I am able to view the availability of mini cabs. ☐ Make Payment

☐ Review and
Feedback
☒ Customer
Service
☐ Access Data
from system

☐ Review and

Page 15 of 74
3. MoSCoW and Minimum Viable Product
3.1 MoSCoW

Image 1: MoSCoW

Page 16 of 74
3.2 Minimum Viable Product

Image 2: Minimum Viable Product (MVP)

Page 17 of 74
4. Planning Poker
The screenshots shown below are the evidence of planning poker for “Registration of account
by email address”.

Image 3: Planning Poker for Account Registration (1)

Image 4: Planning Poker for Account Registration (2)

Page 18 of 74
Other than that, the screenshot shown below is the evidence of planning poker for “Send
Enquiry”.

Image 5: Planning Poker for Send Enquiry

Page 19 of 74
Furthermore, the screenshots shown below are the evidence of planning poker for
“Confirmation email of booking placed”.

Image 6: Planning Poker for Confirmation Email of Booking (1)

Image 7: Planning Poker for Confirmation Email of Booking (2)

Page 20 of 74
Moreover, the screenshots shown below are the evidence of planning poker for “Accepts other
payment methods”.

Image 8: Planning Poker for Accepts other Payment Methods (1)

Image 9: Planning Poker for Accepts other Payment Methods (2)

Page 21 of 74
Besides, the screenshots shown below are the evidence of planning poker for “Send
recommendations regarding special offers”.

Image 10: Planning Poker for Send Recommendations (1)

Image 11: Planning Poker for Send Recommendations (2)

Page 22 of 74
5. Sprints
5.1 Sprint 1
5.1.1 Sprint Planning Phase
5.1.1.1 Sprint Goal
Our team is going to implement all the features from Minimum Viable Product (MVP) which
are categorized as a must. There are a total of 16 user stories to be installed in this sprint which
belong to the module of register and login, make enquiry, online booking, make payment,
customer service and access data from system respectively. In other words, there will be
sufficient features to fulfil all the user stories under Minimum Viable Product (MVP) at the
end of the sprint.

5.1.1.2 Definition of Done

The checklist shown below is the acceptance criteria that the developed product at the end of
this sprint must meet all the requirements stated and the sprint can only be considered as
completed with satisfaction.

✓ Minimum Viable Product (MVP) has been installed into the system
✓ All user stories has been completed and fulfilled by the developed features in the system
✓ All team members reviewed the overall functionality of system
✓ All team members agreed to publish the product
✓ Tester satisfied on the developed product as it passed the User Acceptance Testing
(UAT)
✓ Product owner reviewed and approved the product to be rolling out

Page 23 of 74
5.1.1.3 Sprint Backlog
Our team has planned to work on business days only which is from Monday to Friday. We will
work for eight hours excluding the lunch meal and so on. Therefore, we will have 40 working
hours per week to progress on the sprint. A timeframe of 120 hours has been assigned to this
sprint and all the tasks must be completed within the timeframe indicated. This sprint occupied
45.5% of the time used to develop the whole project.

Estimation
Index User Story Task
(Hour)

Produce the wireframe for

1
registration interface

Design and create the actual

1
interface for registration
As a customer, I want to register
an account with relevant Implement the backend coding
1. information so that I am able to for validity verification 4
create a new account in order to concerning input
surf the website or application. Establish connection between
Register function and database 1
table “Customer”
Review and test the overall
process of registration to ensure 1
all works accordingly
Design and produce a template
for confirmation email of 1
As a customer, I want to get registration
verified by the system so that I am
Implement the template of
2. managing to fully experience the 3
email with backend coding
services and features provided by
the website. Review and test the E-mail
function to send confirmation 2
email to new registered user

Page 24 of 74
 Produce the wireframe for login
½
interface

As a customer, I want to login Design and create the actual

½
into my personal account by using interface for login
registered email so that the
Implement the backend coding
activity and purchase that the I
3. for validity verification 3
have made and carried out are
concerning input
recorded in the system and I am
Establish connection between
able to review back the purchase
Login function and database 1
history.
table “Customer”
Review and test the overall
process of login to ensure all 1
works accordingly

Produce the wireframe for add

½
credit card interface

Design and create the actual

½
interface for add credit card
As a customer, I want to register
credit card details with the system Implement the backend coding
4. so that I can make payment easily for validity verification 2
with a registered credit card in the concerning input
system. Establish connection between
Add function and database 1
table “Credit Card”
Review and test the overall
process of adding credit card to 1
ensure all works accordingly
As a customer, I want to send my Produce the wireframe for send
5. ½
enquiry through the system so that enquiry interface

Page 25 of 74
my feedback and doubts are able Design and create the actual
½
to be exposed to the Call Centre interface for send enquiry
Staff. Implement the backend coding
for validity verification 2
concerning input
Establish connection between
Enquiry function and database 1
table “Enquiry”
Review and test the overall
process of sending enquiry to 1
ensure all works accordingly

Table 4: Sprint Backlog for First Sprint

Page 26 of 74
5.1.2 Sprinting Phase
5.1.2.1 Use Case Diagram

Diagram 1: Use Case Diagram for First Sprint

Page 27 of 74
5.1.2.2 Scrum Board
This section will display the status of our scrum board for the first sprint throughout the whole
development of the project.

Image 12: Beginning of First Sprint

Image 13: Middle of First Sprint

Page 28 of 74
Image 14: End of First Sprint

Page 29 of 74
5.1.2.3 Burndown Chart
These images attached under this section are the burndown chart of development throughout
the whole project.

Image 15: Burndown Chart (Eight Days)

Image 16: Burndown Chart (Full Timeframe)

Page 30 of 74
5.1.3 Sprint Review
Our team has designed a landing page for the mobile application. The users will be required to
tap somewhere on the screen in order to proceed into the main menu interface. The landing
page does include the logo and title of the company to show its uniqueness. A message of “Tap
anywhere to continue” is also included on the interface to guide the users.

Image 17: Landing page

Page 31 of 74
The users will be redirected to the main menu interface as shown in the image below regardless
of whether the user has already logged in or not. The main menu consists of a slider which will
display some images of PrivateHire Cars to act like a general introduction to users. The top
navigation bar is set as sticky mode when scrolling up or down as the user can access the
options provided anytime without scrolling to the top section first.

Image 18: Main Menu

Page 32 of 74
Furthermore, the new users can access the “Sign Up” interface with the purpose to create a new
account. There is some required information to be filled up by users such as email address,
password and second confirmation of password in order to submit the registration form. The
users can also proceed to the “Log In” interface if they already have an existing account while
there is also an option for staff to login into their business account.

Image 19: Registration of New Account

Page 33 of 74
After the users have submitted their registration form mentioned above, the system will initiate
the creation of a new account by recording all the information or details provided by users. A
message will prompt when the new account of the user has been created successfully. In
addition, a confirmation email of registration will be sent to the email address of the user to
serve as an extra reference.

Image 20: Confirmation Email of Registration

Page 34 of 74
The users will now be able to login to their personal account after they have created a new
account. The login form will require the user to enter their valid email and password that have
been registered during the sign-up process. An error message will prompt if the details entered
by the user are detected as invalid account after the verification. On the other side, a message
of “You had logged in your account successfully” will be displayed if the details are valid.

Image 21: Login

Page 35 of 74
The side navigation bar will have six options available for users to access and enjoy the features
provided in each of the options. The options are profile, booking, notification, order history,
contact us and settings. These features are also the primary features required by the company
so that their users can experience a convenient mobile application. Some of the features are
still pending for evolving in the next sprint.

Image 22: Side Navigation Bar

Page 36 of 74
Moreover, a “Profile” interface is also provided for users to check on their personal information.
For instance, date of registration, contact method like email and phone number. The users can
also add a new credit card through this interface for future payment purposes. The personal
profile provides the identification of every single customer that exists in the database. That
unique information would help the organization to perform analysis.

Image 23: Personal Profile

Page 37 of 74
The second option will be the booking section. The “Booking” interface will show the order
placed before if there is any. The details of that particular booking will be displayed such as
the date, the specified pick-up location and destination decided by the user. However,
amendments of booking or cancel booking are not available in this sprint as this feature will be
developed in the second sprint of the project.

Image 24: Booking

Page 38 of 74
Other than that, the third option, notifications is designed to send a message that serves as a
soft reminder to the users. The reminder will be sent to the users when the cab they booked is
about to arrive in 10 to 15 minutes to the pick-up location. Thus, the users will be able to
prepare themselves to get into the cab and depart to the selected destination as mentioned
during placing the booking.

Image 25: Notifications

Page 39 of 74
Additionally, an interface is also designed for “Order History”. The users will be able to view
a list of their order history which the order will be arranged from latest to oldest. The sample
order history is shown in Image 21. It does include the name of cab that the user booked and
the total amount of the order. The order history fulfils the purpose of letting users view their
order history as reference.

Image 26: Order History

Page 40 of 74
Next, the following option is “Contact Us”. The “Contact Us” interface does indicate two
contact methods to PrivateHire Cars which are email address and phone number. Thus, the
users can reach the company for any enquiries. In addition, an enquiry form is provided for
users to send their enquiry through mobile application. The users will receive replies through
their personal email address.

Image 27: Contact Us

Page 41 of 74
The next feature will be the searching feature. A searching section will be provided to the user
in order for them to search for available service. This is an alternative way for users to search
for their desired service other than go through the main menu. The users will just have to click
on the magnifier icon and the system will redirect the user to the “Search” interface. Keywords
of service should be entered and relevant service will be listed out.

Image 28: Search for Available Service

Page 42 of 74
The users are required to provide a few essential information upon placing their booking
through the mobile application. The users will still have to enter the necessary information as
shown in the image below such as pick-up location, destination and number of passengers no
matter which type of service has been chosen by the user. This step is a must for users to
perform if they wish to place their order successfully.

Image 29: Provide Essential Information

Page 43 of 74
The users will be redirected to the “Payment” interface after they submit the information list
of their order. The system will calculate the total amount that the users have to pay and show
the available payment method. Only a credit card method is available in this sprint and the
system will verify the validity of the credit card when the users click on the “Check Out” button.
The credit card will be debited automatically after order has been placed successfully.

Image 30: Total Payment and Verification of Credit Card

Page 44 of 74
After the users have placed their order with a valid information list required, their order will be
processed by the system to generate an online receipt and confirmation email of booking. Both
online receipt and confirmation email will be sent to the users through email when the message
shown in the Image 25 has prompted. Therefore, the users will be having the evidence that they
have paid for the particular service.

Image 31: Confirmation Email and Online Receipt

Page 45 of 74
The final feature of the system in the first sprint is it is able to keep track of different
information. This is a user interface which is viewed from the perspective of staff that allows
the staff to see the current status of each cab and customers. There will be two sections in this
interface which one section is for cab and one section is for customers. Two different sections
will convey the information in a clearer way.

Image 32: Keep Track of Different Information

Page 46 of 74
5.1.4 Sprint Retrospective
This is the first sprint of our project and we feel that our performance is great as this is our first
time to handle agile development. Before we initiate the progress of the first sprint, the Scrum
Master did distribute the relevant tasks to every single member including himself based on their
strengths and it is fairly distributed. This action is a smart move as this will surge the efficiency
of work done and quality of product will be higher for sure. Nonetheless, it does not mean that
we are only working on our own tasks without communication at all. We always have
discussions together regardless of which tasks belong to whom and we will just overcome the
obstacles together as a team without leaving a man behind. The member will just update on the
scrum board once any of the allocated tasks has been done. All the objectives have been
achieved and the first sprint can be considered as completed because it does also meet all the
acceptance criteria or definition of done stated above.

Page 47 of 74
5.2 Sprint 2
5.2.1 Sprint Planning Phase
5.2.1.1 Sprint Goal
Our team will proceed to the second sprint in which all the features that fall under Should Have
(MoSCoW) will be implemented into the system. There are a total of eight user stories to be
developed that belong to the module of online booking, make payment, review and feedback,
customer service and access data from the system respectively. We will still continue to work
hard and install the details of the feature in order to satisfy every single user story even though
there are just eight user stories for the second sprint.

5.2.1.2 Definition of Done

The checklist shown below is the acceptance criteria that the developed product at the end of
this sprint must meet all the requirements stated and the sprint can only be considered as
completed with satisfaction.

✓ All features under Should Have (MoSCoW) has been installed into the system
✓ All user stories has been completed and fulfilled by the developed features in the system
✓ All team members reviewed the overall functionality of system
✓ All team members agreed to publish the product
✓ Tester satisfied on the developed product as it passed the User Acceptance Testing
(UAT)
✓ Product owner reviewed and approved the product to be rolling out

Page 48 of 74
5.2.1.3 Sprint Backlog
Our team has planned to work on business days only which is from Monday to Friday. We will
work for eight hours excluding the lunch meal and so on. Therefore, we will have 40 working
hours per week to progress on the sprint. There is a total of 80 hours allocated for this sprint to
develop all the features. It does also occupy 30.3% of the total time frame towards development.

Estimation
Index User Story Task
(Hour)
Produce the wireframe for
interface towards amendment 2
of booking
Design and create the actual
interface for amendment of 2
As a customer, I want to amend or
booking
cancel the booking 24 hours prior
Implement the backend coding
to intended journey so that I can
1. for validity verification 10
change the type of cabs or cancel
concerning input
my booking if there is no need
Establish connection between
anymore.
Amend function and database 3
table “Booking”
Review and test the overall
process of amendment to 3
ensure all works accordingly

Design and produce a template

2
for choosing payment method
As a customer, I want to choose
any of the payment method from Design and create the actual
2. available options so that I can pay interface for choosing payment 2
with my preferred payment method
method. Implement the backend coding
for validity verification 10
concerning input

Page 49 of 74
 Establish connection between
Pay function and respective 3
database table of payment.
Review and test the process of
choose payment method to 3
ensure all works accordingly

Produce the wireframe for

1
review interface

Design and create the actual

1
interface for review
As a user, I want leave review
after completion of journey so Implement the backend coding
3. that other users can view the for validity verification 4
comments for that particular concerning input
service. Establish connection between
Review function and database 1
table “Review”
Review and test the overall
process of leaving review to 1
ensure all works accordingly

Produce the wireframe for

½
identification interface
As a Call Centre staff, I want to
perform identification of the Design and create the actual
½
person calling so that I am able to interface for identification
4. identify if the person calling is an
Implement the backend coding
existing user and provide further
for validity verification 1
assistance if that person is one of
concerning input
the registered users.
Establish connection between
Identify function and database ½
table “Customer”

Page 50 of 74
 Review and test the overall
process of identification to ½
ensure all works accordingly
Produce the wireframe for
½
registration interface
Design and create the actual
½
interface for registration
As a Call Centre staff, I want to Implement the backend coding
create a new account for new user for validity verification 2
5. so that new users will have a new concerning input
account ready for use after calling Establish connection between
us. Register function and database 1
table “Customer”
Review and test the overall
process of registration to ensure 1
all works accordingly

Table 5: Sprint Backlog for Second Sprint

Page 51 of 74
5.2.2 Sprinting Phase
5.2.2.1 Use Case Diagram
Start here…

Diagram 2: Use Case Diagram for Second Sprint

Page 52 of 74
5.2.2.2 Scrum Board
This section will display the status of our scrum board for the second sprint throughout the
whole development of the project.

Image 33: Beginning of Second Sprint

Image 34: Middle of Second Sprint

Page 53 of 74
Image 35: End of Second Sprint

Page 54 of 74
5.2.2.3 Burndown Chart
These images attached under this section are the burndown chart of development throughout
the whole project.

Image 36: Burndown Chart (First Week)

Image 37: Burndown Chart (Full Timeframe)

Page 55 of 74
5.2.3 Sprint Review
Additional features have been implemented for booking which are the amendments and
cancellations of booking. The users can choose to amend their booking by editing the
information list that consists of the essential details of booking or just cancel their booking.
These actions must be performed prior 24 hours to the time of booking.

Image 38: Amendments or Cancellations of Booking

Page 56 of 74
Next, the second evolution of features in this sprint is increasing the number of payment
methods available. The system is now accepting payment from PayPal other than credit card.
The users can switch the payment method by just clicking on the preferred payment method.
The selected payment method will be arranged in front of the list in order to show the users
which payment method is currently selected.

Image 39: Accepts other Payment Methods

Page 57 of 74
The following interface is for customer review towards their order by just choosing their
previous order from the “Order History” interface. The users will be able to leave a star rating
and some comments for that particular order on experience, attitude of driver and so on. The
company will receive the feedback and keep on improving their services. A message will
prompt when the review is submitted successfully.

Image 40: Star Rating and Review

Page 58 of 74
Moreover, the feature that allows the Call Centre staff to identify the identity of the person
calling them has been developed. An account form is attached in the user interface that the staff
are required to fill in if they want to check whether the person calling has an existing account
or not. A message will be prompted to inform the staff if the person has an existing account or
else another message will be prompted in case the person is a new user.

Image 41: Identification Process

Page 59 of 74
The Call Centre staff can now create a new account for new users if any of them need this
service after their calling ends. Therefore, the “New Account” interface is the section where
the staff can make a new registration of an account by filling the information provided by
customers such as email. A message will prompt when the new account has been registered
successfully. The users will receive a confirmation email as well.

Image 42: Create New Account for New User

Page 60 of 74
Furthermore, a list that consists of all the mini cabs will be another option that the Call Centre
staff can access to. As shown in Image 33, the list displays all the details or current status of
all the mini cabs . For example, the name, price and availability of mini cabs. This information
is useful when serving the customers that are calling through hotlines since they need fast
response as this feature can help to achieve that aim.

Image 43: Access List of Mini Cabs

Page 61 of 74
Lastly, the final feature in the second sprint is the list of drivers. The “Drivers” interface will
be available within the side navigation bar from the perspective of Call Centre staff. The staff
will be able to see the details of drivers just like the list of mini cabs mentioned above. The list
will show the name, overall rating and availability of the driver. The driver will be indicated
as occupied when that driver is currently progressing an order.

Image 44: Access List of Drivers

Page 62 of 74
5.2.4 Sprint Retrospective
The first and main step to do in order to kickstart the second sprint is the distribution of
workload from Scrum Master to team members as usual. The experiences from the first sprint
provided much assistance for us to carry on the tasks that have been assigned to us in the second
sprint since we did learn some lessons from our mistakes. The workload is lower compared to
the first sprint because the second sprint has only eight user stories. The progress on the second
sprint is acceptable and the features implemented are satisfied and meet all the requirements of
the user stories respectively. Other than short discussion concerning our tasks, our team did
also have a meeting per week to update on important progress, suggestions or any issue. The
frequency of meetings might increase when the Scrum Master requests to have additional
meetings with the purpose of important announcements such as modification of particular
features and so on. Finally, the second sprint is also completed with contentment as it fulfils
all the definitions of done.

Page 63 of 74
5.3 Sprint 3
5.3.1 Sprint Planning Phase
5.3.1.1 Sprint Goal
Finally, our team will continue to work on the third sprint after the completion of the second
sprint which is also the last sprint that will be developed in this project. There are only three
user stories categorized as Could Have (MoSCoW) which belong to the module of make
payment and access data from the system respectively. All the three user stories will be broken
down into smaller tasks as the previous sprint does in order to allocate appropriate time frames
for each process to be carried out. Therefore, our team will have adequate time to develop those
features with greater implementation.

5.3.1.2 Definition of Done

The checklist shown below is the acceptance criteria that the developed product at the end of
this sprint must meet all the requirements stated and the sprint can only be considered as
completed with satisfaction.

✓ All features under Could Have (MoSCoW) has been installed into the system
✓ All user stories has been completed and fulfilled by the developed features in the system
✓ All team members reviewed the overall functionality of system
✓ All team members agreed to publish the product
✓ Tester satisfied on the developed product as it passed the User Acceptance Testing
(UAT)
✓ Product owner reviewed and approved the product to be rolling out

Page 64 of 74
5.3.1.3 Sprint Backlog
Our team has planned to work on business days only which is from Monday to Friday. We will
work for eight hours excluding the lunch meal and so on. Therefore, we will have 40 working
hours per week to progress on the sprint. Additionally, this sprint will also serve as a hardening
sprint in which our team will perform overall review and testing again on every single feature
that has been implemented into the system. A timeframe of 64 hours has been allocated to the
final sprint and it does have 24.2% from the total of development duration.

Estimation
Index User Story Task
(Hour)

Produce the wireframe for

1
registration interface

Design and create the actual

As a customer, I want to get a 1
interface for registration
15% discount so that I can get a
1.
cheaper price to pay for selected Implement the backend coding
service. for 15% discount on total 4
amount of payment
Review and test the overall
process of getting 15% discount 2
to ensure all works accordingly

Design and produce a section

1
for apply special offer code
As a system, I want verify the
special offer code so that only Implement the backend coding
2. valid offer code will be accepted for verifying the special offer 1
and apply discount on amount of code
payment. Review and test the overall
process of applying offer code 1
to ensure all works accordingly
As a system, I want to send Establish connection between
3. recommendations regarding Recommendations function and 2
special offers so that the users can database table “Customer”

Page 65 of 74
 enjoy more offers in placing order Implement the backend coding
while using our platform. for select particular customers 4
based on certain condition
Implement the backend coding
for Recommendation function 4
to send relevant information
Review and test the process of
send recommendations to 1
ensure all works accordingly

Test the connection between all

10
the sprints
4. Hardening Stage

Strengthen the coding section 10

Review the coding to ensure it

is readable for future 10
5. Review Stage development
Final testing for the system 6
Create final documentation 6

Table 6: Sprint Backlog for Third Sprint

Page 66 of 74
5.3.2 Sprinting Phase
5.3.2.1 Use Case Diagram

Diagram 3: Use Case Diagram for Third Sprint

Page 67 of 74
5.3.2.2 Scrum Board
This section will display the status of our scrum board for the third sprint throughout the whole
development of the project.

Image 45: Beginning of Third Sprint

Image 46: Middle of Third Sprint

Page 68 of 74
Image 47: End of Third Sprint

Page 69 of 74
5.3.2.3 Burndown Chart
These images attached under this section are the burndown chart of development throughout
the whole project.

Image 48: Burndown Chart (First Week)

Image 49: Burndown Chart (Full Timeframe)

Page 70 of 74
5.3.3 Sprint Review
There are two user stories getting fulfilled within this interface shown in the image below. The
booking placed through online will receive a 15% discount on their total amount of payment.
Additionally, a section is prepared for users to apply their special offer code if they have any.
The system will then verify the validity of the special offer code and the offer such as discount
will be applied automatically if the code is valid.

Image 50: 15% of Discount and Apply Special Offer Code

Page 71 of 74
5.3.4 Sprint Retrospective
The third sprint is the last sprint and it also serves as a hardening sprint in our project. The
Scrum Master did also assign the tasks that fall under the third sprint to the team members
before the starting of the third sprint. This sprint has a total of three user stories only but it still
has a hardening stage and review stage within it. There is a portion of agile developers who
reject having a hardening sprint as they think that having hardening sprints means their agile
sprint is not robust enough to deliver the potential shippable product. Therefore, hardening
sprint is believed to be a bad practice or habit to have in agile projects. Nevertheless, it actually
helps the team to ensure that the development in each sprint does not overlap on the sensitive
zone such as database connection which might cause the overall process getting gummed up
and it does not serve the original purpose anymore. We should ensure that every potentially
shippable product and the final product still serve the main purpose by having a well design on
the overall aspect. This is one of the lessons we learn through the final sprint.

Page 72 of 74
6. References
Atlassian.com. (n.d.). Jira Software. https://www.atlassian.com/software/jira/agile

Businessanalyst.techcanvass.com. (2020). What is a Hardening Sprint? 27 MARCH.

https://businessanalyst.techcanvass.com/what-is-a-hardening-sprint/

Lucidchart.com. (n.d.). Lucidchart.

https://www.lucidchart.com/pages/landing?utm_source=google&utm_medium=cpc&ut
m_campaign=_chart_en_tier3_mixed_search_brand_exact_&km_CPC_CampaignId=14
84560207&km_CPC_AdGroupID=60168114191&km_CPC_Keyword=lucidchart&km
_CPC_MatchType=e&km_CPC_ExtensionID=&km_

Planningpoker.com. (n.d.). Planning Poker. https://www.planningpoker.com/

Visual-paradigm.com. (n.d.). Visual Paradigm Online. https://online.visual-

paradigm.com/diagrams/templates/moscow-method/

Page 73 of 74
7. Pro-forma
Group/Team Name: Thunderous

Individual overall work

Team member name Student ID Additional notes on task description Signature
contribution (%)
➢ SCRUM Master
➢ Distribute workload
Student: Chia Teik Hua 001246861 25%
➢ Develop on allocated tasks
➢ Finalize documentation
➢ Development Team

Student: Tan Sha’o He’ng 001227082 25% ➢ Develop on allocated tasks

➢ Make report upon face any problem
➢ Development Team

Student: Ooi Kai Ze 001234342 25% ➢ Develop on allocated tasks

➢ Make report upon face any problem
➢ Development Team

Student: Cheong Yik Liang 001236429 25% ➢ Develop on allocated tasks

➢ Make report upon face any problem

Total 100%

Page 74 of 74
AGILE DEVELOPMENT WITH SCRUM

(COMP1807)

Student Name:

Cheong Yik Liang (001236429)

Intake: January 2022

Lecturer: Ms. Annida Said.

Reflection and Evaluation Report

My name is Cheong Yik Liang, I am from team Thunderous. We are assigned to develop a car
booking service system named “PrivateHire Cars” to allow our user to book their car online.
Teik Hua is our team leader and he is very helpful and responsive. While developing the system,
we use planning poker, which is a fun yet effective way to decide which requirements and
features to be include into the system and the priority of each feature to develop.

There is total three sprint of our system development. initial sprint, is to implement all the
options from Minimum Viable Product (MVP) that are categorised as a must. There are a
complete of sixteen user stories to be put in during this sprint which belong to the module of
register and login, build enquiry, online booking, make payment, client service and access
knowledge from system respectively.

Second sprint, all the Should Have (MoSCoW) features are going to be enforced into the
system. There are a complete of eight user stories to be developed that belong to the module of
on-line booking, build payment, review and feedback, client service and access knowledge
from the system respectively. We will still be putting your all into and install the main points
of the feature so as to satisfy each single user story.

For the last sprint, our team will still work on the third sprint once the completion of the second
sprint which is additionally the last sprint that may be developed during this project. There are
solely 3 user stories categorized as Could Have (MoSCoW) which belong to the module of
creating payment and access knowledge from the system respectively. All the three user stories
are going to be counteracted into smaller tasks because the previous sprint will so as to the
portion of applicable time frames for every method to be carried out. Therefore, our team will
have adequate time to develop those options with greater implementation.

For the make payment task, the goal is to let user to have various choice of payment method to
make payment with actual interface for registration. There is a discount features for user to
enjoy, which require implementation of the backend coding for 15% discount on total amount
of payment. After that, review and test the overall process to ensure the 15% discount features
are working accordingly.

Since the preparation of this project is time consuming, I need to manage my time well to
ensure that the project can be completed before the deadline. Thus, I realized the importance
of time management to improve my efficiency and effectiveness. As a result, our group had
agreed on several deadlines and meeting schedules to ensure our work goes according to our
plan. Moreover, I had learned how to manage conflict and disagreement during our group
discussion as every team member will has different opinions to contribute. For instance, I try
to be more open mind during the discussion to accept and understand my teammate’s idea from
his perspective. Therefore, we are able to come together to generate a better outcomes.