Standup Sprint 2
- Garvi Poudyal
- Former user (Deleted)
- Joshua Smee
All team members should provide their priorities, progress, and problems each day in this report.
Team name | Fudge |
|---|---|
Direct supervisor | |
Table of contents |
Thursday <03/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | Refine requirements, based on new info | Added requirements on security and authentication | unsure on how secure our API should be, which makes it difficult to finalise requirements |
| 2 | Edward | Ticket - Get Email adress from xml invoice | basic functionality done, minor code revision needed | null. |
| 3 | Joshua | Setup github and base flask server | Finished setting up the github and created the basic flask server level. Was able to integrate the github into jira. | Integrating github into Jira required admin privileges in Jira and thus was done with the help of a tutor. |
| 4 | Tay | Try start code sometime soon! | Cloned git. Wrote more issues for the sprint (including more detail of task breakdown). | Have been vv busy! Not been able to do much oops. |
| 5 | Garvi | Refine requirements from sprint 2 info | Add security and performance - user stories | N/A |
Saturday <05/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | Think about tasks that need to be completed, when and by whom | not to much at this stage | thinking about all the tasks that are required to complete an issue |
| 2 | Edward | no progress | no progress | N/A |
| 3 | Joshua | Task allocation | Started working out the tasks that were needed for the sprint. | Still trying to understand the task fully. |
| 4 | Tay | No progress | No progress | N/A |
| 5 | Garvi | No progress | No Progress | N/A |
Monday <07/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | Work on health check pull github repo | start to think about potential implementation | not sure how to calculate the time the server has been running and how to access variables from other functions. |
| 2 | Edward | Ticket - Send email. | implemented | NA |
| 3 | Joshua | Database design | Started working on how to design the database and what we needed for it. | Don’t quite understand the documentation required for DB design. Example given in lecture different to Tays understanding. |
| 4 | Tay | Start ER, have a look at Email send code | Made a rough ER | Confused about email send code, will need to look at documentation |
| 5 | Garvi | Start thinking for code ~ for multiple recipients and how that can be implemented | Considering the implementation | N/A |
Thursday <10/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | Get health check finished | health check function is mostly completed health check endpoint has been added | need to figure out how to write a test that tests time can’t push to github |
| 2 | Edward | Fix email formatting | Fixed | N/A (changed text formatting from plain to HTML) |
| 3 | Joshua | Created database in sqlalchemy. | Took DB design and created the sqlalchemy classes to match. | Had to make adjustments to db. |
| 4 | Tay | Start comm report | Made branch and am starting skeleton of comm report | Not sure how to handle errors |
| 5 | Garvi | Finish updated stack architecture | Currently researching the different types of development and persistence layers | N/A ~ understanding what “framework” is Haven’t heard of quite few + need group’s familiarity with them |
Saturday <12/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | write tests for health check | figured out a way to test if time is working got rid of the bugs merged with main |
|
| 2 | Edward | Review assigned pull requests, 101 and 107 (Auth and CI) | reviewed 101 and 107 | N/A |
| 3 | Joshua | Added environment variables Added pylint CI Authenication | Was able to add environment variables to github and local file which distributed to group. Also added pylint github action to check pylint. Finished authentication for users. | Had difficult time adding pylint CI. Had to add file to tone down pylint. |
| 4 | Tay | To actually finish comm report | Finished skeleton of comm report | Errors were raising too early, difficult for report to be made |
| 5 | Garvi | Focus on report ~ documentation + anything communication related | Functions required to send email to multiple recipients were no longer needed (scrapped from my issue board) | N/A |
Monday <14/03/2022>
Name | Priorities | Progress | Problems | |
|---|---|---|---|---|
| 1 | Michelle | Finish the sprint focus on performance | written the pseudocode for each algorithm | time management, difficult to finish on time |
| 2 | Edward | complete swagger doucmentation implement CI | Swagger documentation completed CI mostly implemented | CI required rewriting of all http tests to work with github actions. |
| 3 | Joshua | Integrated production DB. Work on documentation.
| Was able to get heroku DB working. Finished up documentation related to development and deployment. | Had to add environment code to track if running on heroku or not and whether to use production DB. |
| 4 | Tay | Finish sprint, finish documentation and diagrams | Finished ER, finished comm report, finished uml | Was a struggle to finish |
| 5 | Garvi | Plan + complete sprint retrospective | Have to start | Whole team isn't here ~ difficult for everyone to give their insights. |