Sprint 3

Tracking of Sprint's work

1. Sprint Planning

1.1 Sprint Backlog

Sprint Backlog
Maintain Clinical Record
Maintain User / Login
Maintain Patient
Maintain Owner
Maintain Bath and Grooming

The team defined that these would be the UC's for this sprint. Some points were watched on picking up theses UC's, like:

Complexity of features;

Knowledge of the pairs;

Sprint Timebox;

UCs` relevance to the system;

Some technical issues were addressed and treated at this sprint like:

JPA implementation;

DAO`s generalizing for the application;

Change how the front-end communicates with the backend;

Change of application url;

1.2 Roles

Product Owner
Antonio Carvalho

Scrum Master
João Paulo Ferreira

Developers
Adailson Santos
Antonio Carvalho
Flávio da Costa
Gustavo Vieira
João Paulo Ferreira
Leonardo Sagmeister
Lucas Amoêdo
Luiz Guilherme
Marcelo Martins
Mateus Roriz
Varley Silva

Git reviewers
João Paulo Ferreira
Lucas Amoêdo

2. Boards

2.1 Knowledge board

2.2 Pairing board

2.3 Pairing analysis board

2.4 General Pairing board

3. Result analysis

On this sprint we made a decision of elect a scrum master because the workflow and the repository politics wasn`t been observed. The scrum master were in charge to explain again and manage how the members were doing their commits and issues referentiation. We started to validate fields and entries on both front-end and back-end of the application, still using the selected use cases to implement.