For this milestone, we worked on implementing our use cases and applying software processes and practices.
For each use case, we implemented the basic flow described by the use case. We implemented a minimal proof of concept (that covered all our use cases).
For building our software we went through careful planning and delegation of work by conducting two sprints of one week each, as part of our process milestone. Wherein, at the beginning of each sprint we discussed any remaining tasks and assigned them equally to each team member.
For both the sprints,
- We divided our use cases into stories/tasks.
- Assigned story points (1,3,5,8) to each user story
- Assigned a team member, who is committed to complete the story by the end of the iteration.
We utilized the kanban board (Github project). We used notes to indicate the story points and developer assigned for each tasks
- Wed Oct 23-- Fri Nov 1 --> First Iteration start meeting notes
In this Sprint, we aimed at replacing our mocking functionality with the actual service and divided the tasks accordingly.
The tasks were divided equally among the students. Each member of the team created their branch and pushed their commits. The first iteration was aimed to be able to complete individual tasks as dicussed in the scrum meeting and documented in kanban. All the bugs and errors were being fixed in individual branch before integration into the main Flask app for the bot. The tasks were assigned with points where each member was allowed to subdivide their 8 points into sub tasks according to their anticipation of time needed for each subtask within the main task. The areas of concentration were -
- Ability to have basic conversations with bot and let the bot know intent of user
- Designing workflows and deciding on datapath for each usecase.
- Ability to correctly parse the data from the commands assigned by the user for each use case
- Store and access data for each user (plot images for each plot type)
- Generate plots, samples from the parsed data and return to user
By the end of the sprint, we have completed all the tasks that we committed at the beginning of the sprint. We have created 8 user stories at the beginning of the sprint and all of them were completed.
- Sat Nov 2--Fri Nov 8th --> Second Iteration start meeting notes
This sprint was aimed at completing the remaining tasks for the POC and assignations accordingly.
For the second iteration, the main objective was to integrate individual contibutions and resolve conflicts, if present with our main application. Whenever a team member's tasks got completed, him/her were merging their code to the master and resolving conflicts. After a succesful merge, a different team member was assigned to review their merges and suggest any fixes, if required. This helped in code refinement and also prevented severe program crashes or bugs in the application with the help of a second pair of eyes. Testing the code with the bot on server and checking for any latency in response were main focuses in this sprint.
By the end of this iteration, we have completed all the tasks that we committed to at the beginning of this sprint.
Status of all tasks at the end of the iteration
For our software process, we followed a "scrumban" methodology, that is a blend of kanban and scrum practices.
We did this by holding biweekly scrum meetings and maintaining a Kanban board for our tasks.
We conducted pair programming sessions to complete our tasks. The driver in this case was the assignee and another navigator who would watch over the driver's implementations. These roles were rotated for each task
We made our code available to the entire team by creating branches for each task. With this other team members were able to verify and improve upon any part of the system they felt necessary
Another practice we followed were code reviews. Each of us created a seperate branch for our tasks, and once those tasks were complete, we created a PR and assigned it to one of our team members for review. Once the reviewer reviews the code, they will merge the code into the master branch.
Work was equally divided among the team. Also, the work was completed uniformly. Each of the team member had approximately 12 Story points worth of work. And these tasks were assigned at the beginning of each sprint
