Table of Contents

1. Introduction................................................................................................................2

2. Sprint and Scrum Artefacts..........................................................................................3

2.1 Sprint Planning Meeting....................................................................................................4

2.2 Identifying requirements...................................................................................................................5

2.3 Result of MoSCoW method................................................................................................................5

2.4 Defining each product as ‘ready’.............................................................................................................6

2.5 Product Backlog..................................................................................................................................7

2.6 Daily Scrum Activity between planning and review...........................................................................8

2.7 User Stories........................................................................................................................................8

2.8 Sprint Review meeting.......................................................................................................................9

2.9 Sprint Retrospective.........................................................................................................................10

2.10 Product Backlog refinement............................................................................................................11

3.0 Technical Areas......................................................................................................11

3.1 Technical description of the Book a Table.......................................................................11

3.2 Technical Description of the registration and Login pages...............................................14

4.0 Contribution Matrix:...................................................................................................15

5.0 Commitment..............................................................................................................16
 1. Introduction

This assessment report is intended to provide the teamwork of the assigned team members
how they have utilized their skills, knowledge, and accomplished the assigned tasks to
successfully complete the proposed application using the SCRUM framework an effective
AGILE Project management to accomplish the proposed project successfully. The proposed
application is an Online Restaurant application where a customer can book a table and make
an order in the restaurant well in advance.

The proposed project is a web-based application which is developed, tested and

implemented. This report shall provide the features of the proposed project in the form of
user stories which are equipped in a Product Backlog, progress of the development of a
sprint in the form of Product Backlog, and implementation of the planned activities in the
outcome of a Sprint Review meeting, Sprint Retrospective meetings that are commonly
organized at the end of the sprint. This report shall be considered a performance evidence
for the team in which the individual contributions are also represented in the contribution
matrix by which the commitment of the team members is also evaluated based on the
contributions made for successful accomplishment of the proposed restaurant reservation
system.
 2. Sprint and Scrum Artefacts
The proposed application is developed using the Agile Scrum Framework with the following Scrum
Artefacts are discussed below:

1. Sprint Planning: The sprint planning activity is performed by the Scrum Team prior to the initiation
of the sprint. The sprint planning activity shall be consisting of the list of sprint backlog items that
are planned to accomplish in the upcoming sprint.

2. Daily Scrum: A regular meeting held at same time same location to review the work status on a
daily basis.

3. Sprint Review: At the end of the sprint a sprint review is conducted to review the previous sprint is
conducted to understand the team performance.

4. Sprint Retrospective: A sprint retrospective is done at the end of the sprint, which is used to
evaluate the previous sprint performance, based on the previous sprint the product backlog may be
refined i.e. addition/deletion of user stories are made for the Product Backlog.

5. Product Backlog Refinement: This activity is performed during the sprint retrospective. Here from
the product backlog the sprint backlog shall be refined as per the previous sprint activities or
changes made in the user stories by the Product Owner.

Figure 1: scrum procedure - Credit: staragile.com

 2.1 Sprint Planning Meeting
As specified earlier, this is a Planning activity which is usually conducted before the initiation of the
sprint, participants include the Scrum Team that consist of the Scrum Master, Product Owner,
Development Team and any other stakeholders are also include in the meeting such as Business
Analysts etc. For the proposed project the meetings are organized and initiated by Rohith and the
first meeting before the initial sprint has been organized using the online meeting applications i.e.
Zoom. The meeting host was also Rohith. The agenda of the meeting was to discuss about the
proposed project and list the requirements that are necessary to develop the proposed project and
meet the requirements. In this meeting we have defined certain terms like user story, Definition of
Done (DoD) and Daily Scrum with a mutual concern from the team.

 The following team members have attended the scheduled meeting. The members present
are Rohith, Shivam and Ayyapa.
 Requirements are the primary objective of the sprint planning meeting where we have
applied the most popular MoSCoW technique in classifying the requirements as shown in
the Figure 2 below.
 The next discussion important objective was to define the term ready i.e. Definition of Done
(DoD) which is to ensure that the product is development is completed.
 A time was fixed to conduct daily scrum which is mandatory for all the team members to
meet on a daily basis and discuss about only the assigned tasks and progress. The time
duration for a daily status meeting was fixed for 15 minutes and it is planned to organize
daily at 10:00 AM.
 The team has also discussed about the user stories and the capabilities to accomplish the
task.
 The meeting of the minutes are recorded by Ayyapa and were shared to team members by
e-mail.

Figure 2 MoScoW Method - Credit: visual-paradigm.com/

 2.2 Identifying requirements
With the help of MOSCOW method, we have planned to implement the requirements similar to
the requirements which are defined in the table 1 shown below. The requirements are classified
as Must have, should have, could have, and Won’t have. The requirements classified as Must
have are said to be mandatory requirements such as Customer Registration as the must have
requirement which needs to be developed in the proposed application. This requirement was
suggested by Rohith which is used to record and store the customer information.

The next must have related to the online restaurant management system is adding the
items into the menu i.e. Admin need to be provided with a privilege where they can Add, Edit,
Update and Delete the existing items in the menu of the proposed restaurant management
system. This requirement was specified by Rohith which is used to add the new items into the
menu of the restaurant application.

The Should have requirement are next higher priority which can be considered as vital
requirements for the proposed application. One of the requirements that can be considered as
should have is the validation for the field e-mail address to ensure that the e-mail address is
unique which is should have requirement proposed by shivam. This should have requirement
shall enhance the application features.

They could have requirements are the requirements that can be included in the project as a
part of enhanced features of the application development which shall be an enhanced
functionality such as sending an e-mail the advance reservation booking apart from the printing
of the receipt. These requirements are proposed by Ayyapa.

They won’t have requirements are that are not included in the development of the application.
The requirements such as using an animation video for the customer to register and book a
reservation in an advance and select the combo meal to be served with number of occupancy,
these requirements are provided by Shivam and Ayyapa.

2.3 Result of MoSCoW method

Using the Moscow method, the requirements can be presented as Table 1:

Table 1: summary of MoSCow method and outcome

Requirements Priority
Customer Registration Online Must have
Items Addition Must have
e-mail address validation Should have
Mailing Invoice Could have/Should have
Animation videos Won’t have
2.4 Defining each product as ‘ready’

Once the requirements are identified and classified successfully then the next immediate activity is
to define the term ready for the respective requirement. The respective ready shall be different from
the requirement to requirement. The Definition of Done (DoD) is used to define the completeness of
the respective requirement which can be shown in the table below :

Requirements Definition of Done

Customer Registration Online A working model where customer can register
successfully
Items Addition Admin can update the products on the fly
e-mail address validation Verification of the e-mail address structure when
the user attempts to enter the e-mail address in the
respective field
Mailing Invoice Post reservation activity customer can request or
receive an automated mail from the application
Book a Table A registered customer can successfully reserve a
table and update the table.

Rohith and Shivam have prepared the required amount of requirements work where they have
prepared the page layout and identified the respective fields and the input data type. Ayyapa
has provided the logical database design with the rough layout such as identifying the
mandatory fields that are required for the business. Shivam and Ayyapa has listed the
technology set that is suitable for the proposed application development and shared the list to
select from the technology stack as a collective activity.
2.5 Product Backlog

The lists of user stories that are listed in the product backlog are presented in the table below:

Product Backlog Item Priority Assigned to Tasks

Customer Registration High  Identification of actions
and Login Page that are required to be
Rohith performed.
 Identification of fields and
datatypes.
 Auto allocation of Unique
Ayyapa UserId.
 Terms and conditions
added to the registration
page.
 Login activity functionality
Creation of Database, High  Create a Database
tables  Create the customer table
Ayyapa  Store the customer
records
Shivam  Creation of Login table to
verify the login.
 Encrypting the password
field where admin cannot
read the password.
Creation of Customer High Rohith  Creation of HTML pages
Registration and Login with CSS and JS for
Pages Shivam validation in PHP.
 Organizing the web pages
Ayyapa  Design HTML pages with
CSS
2.6 Daily Scrum Activity between planning and review
The main aim of the Daily Scrum Meeting is improving the communication among the Development
Team and discuss about the tasks that are assigned to the respective individual. The daily scrum
meetings are conducted in the Zoom Meeting app daily from Monday to Friday at the specified time
10:00 AM to 10:30 AM.

These daily scrum meetings are documented by Ayyapa and the respective individual daily scrum
meeting responses are shared to Shivam. who shall archive and share them at the end of the Daily
Scrum meeting.

To summarize the discussion:

Shivam has provided the list of impediments related to the documentation of User Stories as how to
validate the user story and how we can keep assign the priority to a user story and also discussed
about the previous days task and current task. Rohith has addressed the impendences, and clarified
how to document a user story and how to assign the priority for a respective user story in a product
backlog.

Shivam- has specified the progress of the creation of the Database and Tables. It was also specified
that the MYSQL is the database that was selected for developing the database for the proposed
application. Shivam has also specified the naming conventions and column names, values that are
required in creating the database. Ayyapa and Shivam has also discussed about the respective
columns.

Rohith, Shivam and Ayyapa all have shared their respective daily scrum meeting status and by
which all the daily meetings are consolidated and shared to the team. This shall enhance the team to
understand and remember the discussions that are held during the daily scrum meetings.
2.7 User Stories
The user stories for the respective product backlog are specified in the Table 2.

Table 2: User Stories and Stage where tasks where at between meetings

Team User Stories To do Doing Done

member
As a admin I  Need to  Installation of  Development of
want to store choose the MYSQL ER- Diagram with
Shivam and retrieve database. software. relevant table
the registered  Need to names, fields
Ayyapa customers create a Effort - with their
details to database and medium constraints are
authorize their tables with identified.
Login activity required fields Effort – Small
and data
types.

Effort- High
As a registered  To create a  Installation of  Creation of
user, I want to database MYSql database
Shivam store the and table application  Creation of table
customer to store the  Use encrypt
registration customer Effort - high default function
information information to encrypt the
and encrypt the password
password. Effort - high
Effort - HIgh
As a customer I Create HTML pages Initial design of  Installation of
want a simple Registration page was PHP and Xampp
and user Effort - high developed as per the
friendly standards.  Created Zoom
Rohith registration room to facilitate
page to Effort - Moderate meetings
complete the Effort - small
registration
page
successfully.
As an Admin Create HTML pages Design and Identification of the
user, I want to development of the required fields that are
Ayyapa create new Effort - high web forms for adding associated with the
items and edit and updating the respective web page that
the existing Items are used for adding the
items so that I item.
can update my
Menu.
2.8 Sprint Review meeting
The Sprint review meetings are conducted in Zoom to maintain the COVID 19 distance measures and
the sprint review meetings are conducted at the end of the sprint to discuss about the impedances
that are observed during the previous sprint.

The summary of the Sprint review meeting are discussed below:

Rohith has presented the mock-up of the customer registration page and Login pages that are
proposed to be developed in the proposed application.

Shivam has demonstrated the MYSql application using the PHP MYADMIN and discuss about the
creation of database and tables. Implemented the password encryption using the default encrypt
function.

Ayyapa demonstrated the registration page with the required fields and column values that are
associated with the database design.

Rohith has demonstrated the respective php developed HTML pages that are associated with the
Admin activities i.e. Item creation and update functionality.

Team Done
member
 Developments of ER- Diagram with relevant table names, fields with their
constraints are identified.
Ayyapa  List of activities that are required to accomplish the product backlog.

 Creation of database
 Creation of table
Shiavm  Use encrypt default function to encrypt the password

 Installation of PHP and Xampp

Rohith  Created Zoom room to facilitate meetings

 Identification of the required fields that are associated with the respective web
page that are used for adding the item.
Ayyapa
2.9 Sprint Retrospective
The sprint retrospective activity is used to identify the impendences and solutions to address the
issues that shall enhance the productivity of the upcoming sprints. The following is the summary of
the sprint retrospective:

Shivam has reviewed the sprint and Ayyapa, Rohith has agreed that they can improve the
productivity by enhancing their skills in PHP and web page development. Shivam has clearly
documented the sprint retrospective documents and shared the proposed retrospective meeting
outcomes to the team members for effective product development.

2.10 Product Backlog refinement

The following items were identified for improving upon the product backlog.

Product Backlog Refinement proposed

Customer Registration In online customer registration page we need
to ensure that all the fields are captured and to
avoid multiple registrations ensure the e-mail
address filed is unique.
Login Page Ensure the login page has forgotten password
link so that user can request for forgot
password activity.
Creation of Database and tables Ensure that database design is simple and the
database design needs to be at least in 3NF.
The tables that all are being created need to
have a primary key.
Application Security Ensure that the application is secured and
Application level i.e. front end and at database
level.
Creation of HTML pages This shall be delivered at the end of the sprint
2. All the webpages are required to be
developed with responsive as the application
can be accessed using any device.
Admin activities Provide a default username and password for
admin to perform the admin activities such as
adding items, Menu items, staff and other users
of the application.
3.0 Technical Areas
3.1 Technical description of the Book a Table

The customer needs to be a registered user to book a table. The table booking activity can be done
for a dine out or to organize a party or a regular activity. Customer need to book the table at least
one hour in advance. For a successful table booking activity the customer need to be a registered
customer who can initially register and then place an advance booking. The booking shall be
accepted if the tables are not booked in advanced during the respective date and time. Customer
can take a print of the advance booking receipt after successful order placement and can also
receive a mail relating to the advance booking.

To confirm the booking the customer shall make the 50% of the payment in advance which is
applicable under certain criteria i.e. if the tables are booked for larger number of people such as 25
pax or 50pax . Upon upfront payment the advance booking shall be confirmed and customer can
avail the service. A customer can postpone or cancel the advance booking at least 72 hrs before the
slot and time for which 25% cancellation charges are collected as a part of penalty charges. The
respective tools and technologies that are involved in the development of the proposed application
are described below:

TECHNOLOGIES & TOOLS:

XAMPP
MySQL  via PhpMyAdmin
Internet Exploer 10.1
PhP, HTML, CSS, JAVA SCRIPT

Registration

Login

Reserve a
table
 Figure 3 – Table Reservation Process

Figure.4. Table Reservation Screen with a confirmation.

3.2 Technical Description of the registration and Login pages

A simple registration page is created where the user can provide their e-mail address to complete
the registration process. The e-mail address shall be the primary field where the e-mail address shall
be verified and validated to ensure that e-mail address is valid. Once a user is registered with a e-
mail address the same cannot be used by another user. The registration page is shown below:

Figure 5– Registration page

The login page for the admin is shown in the figure below:

Figure.6. Admin Login page.

4.0 Contribution Matrix:
Ayyapa discussed the consequences and explained how the user experience should be
reported and how emphasis should be placed on a product backlog for each user story.
Ayyapa The application MYSql was presented by Shivam with the PHP MYADMIN and
discussed data and tables creation. The default encryption function implemented the
password encryption

The progress of building the database and tables was defined by Shivam. The data base
chosen for the creation of the database for the suggested application was also stated. Shivam
also specified the naming conventions and column names required in the database creation.
The application MYSql was presented by Shivam with the PHP MYADMIN and discussed
data and tables creation. The default encryption function implemented the password
encryption.

Rohith organizes and initiates meetings for the proposed project and the first meeting is held
before the first sprint, i.e. via online application for meetings. ie Zoom. Rohith was also the
moderator of the conference. Rohith also did Installation of PHP and Xampp

Task Task Ayyapa Shiavm Rohith

Weight
Developments of ER- Diagram with
12.5% 100%
relevant table names, fields with their
constraints are identified
List of activities that are required to
12.5% 100%
accomplish the product backlog
Creation of database
12.5% 100%
Creation of table
12.5% 100%
Use encrypt default function to
encrypt the password
12.5% 100%

Installation of PHP and Xampp

12.5% 100%
Created Zoom room to facilitate
meetings
12.5% 100%
Identification of the required fields that
are associated with the respective web
12.5% 100%
page that are used for adding the item
5.0 Commitment
Rohith organized the meetings and planned sessions, the following staff members
participated. Rohith, Shivam and Ayyapa were the leaders present. Ayyapa registered the
minute meeting and was conveyed via e-mail to team members. T Ayyapa registered the
minute meeting and was conveyed via e-mail to team members. The whole team participated
in identifying the requirements for the project with each of them coming up with a
requirement showing their commitment to the project.

In order to create a page layout, and to define each area and type of data, Rohith and Shivam
have established the necessary amount of research needed. Ayyapa has supplied a rough
outline for the conceptual architecture of the servers, for example, defining necessary
business areas. Shivam and Ayyapa have listed the appropriate technology set for the
proposed application development and shared the list of collective activities to be selected
from the technology stack.

Rohith, Shivam and Ayyapa all share their respective day-to-day status and merge and
discuss their regular meetings with the squad. It strengthens the team's comprehension and
knowledge of debates at frequent scrum sessions. Shivam reviewed the sprint and Rohith
accepted that they would improve profitability by increasing their skills in the production of
PHP and the website.

The team displayed outstanding team dynamics, scraming activities, and agile project
management capabilities where consistency and expectations were implemented throughout
the whole project. Rohith, Shivam and Ayyapa have made every attempt to ensure an
successful and productive production of the project.