PROJECT:

Development of a Web Application for the Newport Institution Implementing the SCRUM Methodology
 Table of contents
1. Introduction. 2
1.1 Purpose. 2
2. General Overview of the Methodology. 2
2.1 Foundation. 2
2.2 Work values. 2
3. People and roles of the project. 3
4. Artifacts. 3
4.1 Increase. 4
4.2 Burn Down Chart. 4
4.3 Meeting to generate the Product Backlog. 4
4.4 Meeting for generate the Sprint planning. 5
4.5 Meeting of Work. 7

1 | Page
1. Introduction

This document describes the implementation of the SCRUM work methodology in the
Newport Institute Web Application Development Project.
Include along with the description of this iterative and incremental life cycle for the project,
the artifacts or documents used to manage the tasks of acquisition and supply:
requirements, monitoring and tracking of progress, as well as the responsibilities and
commitments of the participants in the project.

Final Report of Sprint 1

Development of the Newport Institute Web Application Nº de Sprint:1

Planning October 20, 2014
Description of the work methodology

Description of the work methodology

1.1 Purpose
Report the way of working that was adopted by the team for the implementation of the methodology.
Scrum and to describe the process that followed in the development and control of the first sprint.

2. General Description of the Methodology

2.1 Foundation
The main reasons for using the SCRUM methodology for the implementation of this
project are:

Modular system: The features of the NEWPORT INSTITUTE application allow

develop a minimum functional base and build upon it by increasing the functionalities or
modifying the behavior or appearance of those already implemented.
Frequent and continuous deliveries to the customer of the completed modules, so that they can
to have basic functionality in a reasonable time and from there a
increment and continuous improvement of the application.

Satisfy the customer.

Welcome changes in requirements.
- It is possible that the system incorporates more functionalities than initially planned.
identified.
- It is possible that during the execution of the project, the order in which things are desired may be altered.
receive the completed modules or user stories.
2.2 Work values
They were elected by vote by the Scrum team where it was concluded that they must be
practiced by everyone in the development of the project with the aim of achieving the objective
established and successfully carry out the methodology. These values are:

Team autonomy
Respect in the team
Responsibility and self-discipline
Focus on the task
Transparency and visibility information.

2 | Page
3. Project personas and roles

Role Member
Scrum Master Martha Leticia Sánchez López
Product Owner Maria Esmeralda Pérez Piñón
Analyst/Documenter Diana Fernanda Díaz León
Designer Jurhiata Joel Ibarra Garnica
Programmer Miguel Ángel Rodríguez Guzmán
Programmer Ignacio Alan Moreno Álvarez
Programmer Antonio Abraham Ochoa Avalos
Tester Celeste Álvarez Aguirre
Programmer Miguel Ángel Ramírez Rodríguez

The Scrum Master:

o Help the rest of the Scrum team to follow their process.

o Work with the Product Owner to keep the product backlog up to date.
o He/She has a good understanding of Scrum.
o Act as a coach for the Scrum Team

The Product Owner

o It is responsible for deciding which work should be done.

o Record in the product Backlog the user stories that define the application.
o Updated maintenance of the product stack at all times during the
project execution.
o Incorporation / removal / modifications of the stories or their order
priority.

The development team

o Responsible for carrying out the necessary work to deliver the increase of the
project.
o Updated knowledge and understanding of the product stack
o Sprint backlog creation.
o Auto-assignment of work.

4. Artifacts
Product Backlog
Sprint Backlog

Sprint

Increase

Graphs for recording and tracking progress.

Progress chart or Burn Down

Communication and meeting reporting.

Meeting to generate the product backlog
Sprint planning meeting

3|Page
 Work Meetings

4.1 Increase

Part of the application that was produced in a sprint and delivered to the client completely.
finished and operational.
4.2 Burn Down chart

Show the progress status of the current sprint work.

Effort chart
Pending Effort

16
14
12
10
8
6
4
2
0

4.3 Meeting to generate the Product Backlog

Meeting to determine the functionalities or user stories that will be included in the Sprint.

Generated by the Product Owner Esmeralda, Scrum Master Martha, and the development team.
This meeting took place on Friday, October 3, 2014

Where was it determined which are the most important modules for the client? What are the stories?
What will be part of each of the modules and what is their priority?
Follow-up that was done that day:
- The Product Owner (Esmeralda) mentioned to the rest of the Scrum team what the
general project requirements as well as what matters most to the client.
- The product owner writes down these requirements on the whiteboard, subsequently the team members of
team gave their opinion on which ones have higher priority than others, in the cases
that not everyone agreed on the priority, an explanation was requested as to why it is considered that.
of higher or lower priority, ending their explanation, the rest said because they were
agree or not, in cases where they did not yield their opinion, it was determined by majority
voting.
- The team members self-assigned themselves to the responsible parties for each H.U according to the
skills that each individual has and taking into account the roles they perform.
- Scrum acted as a moderator in this decision-making process.
- This is how the activity of gradually generating the entire product backlog was carried out until it was completed.

4 | Page
4.4 Meeting to generate the Sprint planning

The purpose of Sprint planning is to provide the team with enough information so that
determine how they will work during the 2 weeks that the sprint lasts.

This Sprint planning specifically produced:

A Sprint goal
Work with commitment and responsibility in order to deliver on time and in the correct manner the first
sprint of the Database Design thus satisfying the client's requirements.

A list of members (and their level of dedication)

Member Dedication
Martha Leticia Sánchez López 100%
Maria Esmeralda Perez Pinon 100 %
Diana Fernanda Díaz León 95%
Jurhiata Joel Ibarra Garnica 95%
Miguel Ángel Rodríguez Guzmán 85%
Ignacio Alan Moreno Álvarez 85%
Antonio Abraham Ochoa Avalos 85%
Celeste Álvarez Aguirre 85%
Miguel Ángel Ramírez Rodríguez 85%

A Product Backlog

It is a prioritized list of requirements, or stories, or functionalities (that the client wants, where it is used)
terminology).
Product Backlog

project_name Newport Institute

Start Date: 03/10/2014

General Objectives and Scope:

Develop a website to manage and administer staff and students enrolled at the Newport Institute.
The website must allow users to take online placement tests and store the generated data in a database.
Allows registering users' exam scores, as well as querying scores through the students.
The staff of the Institute that manages the website will be able to register, deregister, modify, and consult personnel and students.

Definition of Tasks and Activities

Id Estimation
Description Responsible State Sprint
H.U (hrs)
Database Design Half of the team 5 1
001 Design the contextual diagram Juri Finished 3
002 Design entity-relationship diagram Juri Finished 3
003 Design relational diagram Juri Finished 3
004 Implementation of the database Juri Finished 2
Database communication with the server Antonio / Ignacio /
005 Finished 3
web Miguel A / Miguel
Fig. 1 Format implemented for the Product Backlog.
A Sprint Backlog

5 | Page
This consists of breaking down the user stories into tasks that the team will develop in the iteration.

Sprint 1
Sprint Start Duration

1 06/10/2014 2 Weeks
Sprint Backlog

Sprint Hours/Effort for

State task
Id. H.U. Requirement/Tasks Responsible
o
0 1 2 3 4 5 6 7 8
001 Define entities and attributes of each entity JURI T
Now that the entities are defined, apply
002 JURI T
cardinality to each of the entities
002 A relationship is made between the entities JURI T
002 Cardinality is applied to each of them. JURY T
The corresponding attributes are assigned to
002 JURI T
each entity
Each of the is associated in a table.
003 JURI T
entities with their corresponding attributes
The primary key(s) for each is defined.
003 JURI T
entity
A list of the entities is made, relationship
003 JURI T
What was done in the previous diagram?
The appropriate foreign key is assigned to one of
003 JURI T
the entities
The database is created in the handler that is
004 JURI T
election

004 Each of the entities (tables) is created. JURI T

Each of them is assigned at least

004 JURI T
a primary key
To each of the attributes (fields of the
004 A data type must be assigned to them (table). JURI T
with a specific field size
The fields of the must also be assigned
004 JURI T
foreign keys
004 Foreign keys are assigned as indexes. JURI T
Relationships are made, defining as
004 JURI T
CASCADING each of the relationships
Relationships must be made between braces
004 JURI T
primary keys and foreign keys
Antonio
Ignacio
005 Set up a database on the server T
Miguel A /
Miguel
Antonio
Create a user that has privileges over the Ignacio
005 T
database Miguel A
Miguel
Antonio
Ignacio /
005 A connection file is created in PHP language T
Miguel A
Miguel
Antonio
Ignacio
005 Create login form for the database T
Miguel A
Miguel

6 | Page
 Antonio
Create a query to verify the existence of the Ignacio
005 T
user Miguel A
Miguel
Antonio /
Ignacio
005 Create session validation file T
Miguel A
Miguel
Antonio
Ignacio
005 Create interface to terminate connection T
Miguel A
Miguel
Fig. 2 Sprint Backlog Deployment Format

A specific delivery date for the Sprint

The duration of the sprint is: 2 weeks
06-10-2014
10-20-2014

A defined place and moment for the Daily Scrum

Location: room F2
Time: 1:00 pm to 1:15 pm

Where the Scrum Master supervises the meeting and notes the needs or impediments that I can.
detect the equipment.

A defined place and time for work meetings

Place: room J4
Time: 11:00 am to 2:00 pm
Day: Friday

A Work Structure
Communication within the team will be informal, through email, social media and
face-to-face dialogue.

Some Aspects to Evaluate within the Team:

- Punctuality at work meetings
- Individual responsibility
- Organization in the workplace
- Commitment to the delivery of individual and team work.

4.5 Work Meeting

This aims to develop the sprint activities in which the whole team participates.
Scrum.
Follow-up that was given:
The Scrum Master takes attendance at the agreed time, noting delays and absences of
team members.
Subsequently, the sprint planning is illustrated, where the order of the activities is observed.
elaborate.
The activities were carried out according to the planning, taking into account the planned hours.
but in case it does not reach, the dedication time will be extended.
The Scrum Master is responsible for providing everything necessary to ensure that there are no impediments.
to work and to record the conflicts or obstacles present for the completion of any activity.
In case not all activities of that day are completed, another workday is proposed or if each
individually responsible performs their task but with a due date.

7 | Page
 Meeting October 10, 2014

o The Scrum Master takes attendance at 11:00 am.

o The Scrum master took charge of reading what the H.U is to the rest of the Scrum team.
o The person in charge of that H.U starts to design the contextual diagram of the database on the whiteboard, asking
subsequently the opinion of the other members of the development team, where
they considered some changes due to the vote of the majority of the team. (conflicts that arise
they presented, they could not reach an agreement on the relations between the entities.
o The designer is generating the entity-relationship model design with the support of the challenge of
scrum team.
o Finally, the design of the relational diagram is completed with its respective Normalization.
where the entire team participated in its creation and the designer was responsible for illustrating it in the
blackboard
o The documenter was in charge of transferring the designs onto paper.
o While the development team was working, the testers were in charge of creating the stories of
test for the finished Stories.

Meeting October 17, 2014

o The Scrum Master takes attendance at 11:00 am.

o The designer was responsible for creating H.U 004, creating the database in the database manager.
data.
o The programmers were responsible for carrying out H.U 005 of the database connection with
the server.
o The testers conducted the tests of the completed H.U.
o The Scrum master and the product owner updated the product backlog and supported the rest of the team.
team in their activities.

Work Meeting Attendance Chart

Assistance
Delay
faults
1

0
Miguel Miguel Celeste Anthony Jurhiata Maria Martha Diana Ignacio
Angel Angel Alvarez Abraham Joel Ibarra Esmeralda Leticia
Fernanda Alan
Rodriguez Ramirez Aguirre Ochoa Garnica Perez Sanchez Diaz Leon Moreno
Guzman Rodriguez Avalos Pine nut Lopez Avila

8 | Page