PROCESS.md

WORKSHEET

SPRINT 1

Deliverable	Item/Status	Issues/Tasks
Scenario	Choosing Ideal Database for our Use-Case (Complete)	#29
Scenario	Setting up Database Environment (Complete)	#30
Scenario	Designing Database Schema (Complete)	#31
Use Case	Integration of Database with all of the Use Cases (Complete)	#32
Testing	Evaluation of edge cases (Complete)	#33
Mocking	Replacing the mocking integration with the actual database integration (Complete)	#34

SPRINT 2

Deliverable	Item/Status	Issues/Tasks
Use Case	Implementation of self-stats use case (Complete)	#43
Use Case	Implementation of leaderboard use case (Complete)	#44
Testing	Modification of Unit Test Cases for Use cases 1,2,3 (Complete)	#45
Testing	Creation of Unit Test Cases for self-stats use case (Complete)	#46
Testing	Creation of Unit Test Cases for leaderboard use case (Complete)	#47
Testing	Evaluation of edge cases (Complete)	#48

Kanban Board Sprint 1 issues

Kanban Board Sprint 2 issues

Corollary & Core Practices

Corollary Practices

We practiced the following corollary practices while working on the project:

1. Incremental Deployment: To begin with, we were always making regular updates to the feature and dev branches which helped us to keep track of the failing cases and do continuous monitoring of our code.

2. Shared Code: All of our project code base is set up on the shared github repository and hence it helped all of us to keep progress of each other's individual work and contribution.

3. Team Continuity: All of our team members have equally contributed to the project. On some days, even if someone completed his/her daily tasks then also he/she collaborated with the other team member who was yet to complete his/her daily task. This shows that our team members always sticked together and worked as a team should work.

Core Practice

The core practice which we used in our project is "Pair Programming". In these sprints, each use case was worked upon by a pair of two people. So, two team members worked on one task at a time in which one team member would write the code while the other team member would monitor and evaluate the programming logic of the written code. Moreover, these roles were switched between the two team members periodically.

Daily Scrum Meeting Notes

Sprint 1

Sprint 2

Process Reflection

Overall, throughout the sprints following things were observed -

1. All the stories committed were completed on time and were completed uniformly without last minute hassles.
2. All team members contributed uniformly and were available for team meetings despite other commitments.
3. This process had us practice the industry level practices and it was overall a great experience.