Scrum: Development Methodology

We will describe in this chapter the development methodology chosen to conduct our project, and we will illustrate by then the different steps showing the technological, functional and technical aspects of the final product.

\section{Scrum as a Development Methodology}

In order to ensure a high quality product available to the customer, the team in which I had to integrate is basing on the principles of agile methods, specifically Scrum \cite{Scrum}.

Scrum is an agile methodology that can be applied to nearly any project; however, the Scrum methodology is most often used in software development. The Scrum process is suited for projects with quickly changing or emergent needs. Scrum software development progresses via a series of iterations

The Scrum model expects the team to bring the product to a potentially deliverable state at the end of each Scrum sprint.

The second artefact is the product backlog, it represents the complete exhaustive list of the functionality that remains to be appended to the product. the backlog is prioritized by the product owner so the team always works and develops on the most valuable features first.

In order to establish a product backlog using Scrum methodology there is a very known way which is to populate it with user stories. User stories are short descriptions of functionality described and detailed from the perspective of a user or customer.

Supplementary artifacts resulting from the Scrum agile methodology is the sprint and release burndown chart.

Those charts display the amount of work remaining in a sprint or a release, and they are an efficient tool in Scrum software development to determine whether a sprint or release is on schedule to have all planned work finished by the estimated date.

\subsection{The Agile Scrum Project : Main Roles}

Despite the fact that individuals may join the team with various job titles, those titles in Scrum are insignificant. Scrum methodology exposes the fact that each person contributes in whatever way he can in order to accomplish the work of each sprint.

\subsection{Scrum Application in our Project}

In our case in this project, Scrum team members are not all present. Given the project, the development team is composed of two people, a front-end developer and myself as an architect and a back end developer. I am also considered to be the Scrum Master. The product manager of Leadscore.io is considered as the Product Owner.

The Identification of business requirements was considered incremental. After each meeting with our partners and pilot customers , and assignment of priorities for each requested functionality by the product owner, a product backlog is implemented within GitHub and considered as a starting point of the project development.

\section{Application Architecture \& Development