| Info |
|---|
All team members should provide their priorities, progress, and problems each day in this report. |
Team name | Fudge | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Direct supervisor | |||||||||
Table of contents |
|
\uD83D\uDDD3 Thursday <17/2/22>
Name | Priorities \uD83E\uDDD0 | Progress \uD83D\uDE0A | Problems \uD83D\uDE10 | |
|---|---|---|---|---|
| 1 | See what is going on… try to get onto Jira and Confluence! | Honestly none - just had another quick skim of spec | NOTHING ABOUT OUR ACCOUNTS AND NOT MUCH MORE CLARIFICATION | |
| 2 | Wrap my head around the requirements of the project |
|
| |
| 3 | Reading spec - trying to understand | Read over spec - trying to understand | Jira and Confluence have not been set up yet | |
| 4 | ||||
| 5 | keep up to date and stay in the loop | checked teams, discord, fb | too many layers of communication. |
\uD83D\uDDD3 Saturday <19/2/22>
Name | Priorities \uD83E\uDDD0 | Progress \uD83D\uDE0A | Problems \uD83D\uDE10 | |
|---|---|---|---|---|
| 1 | Similar to thurs - get onto Jira/Confluence | Got our team Jira and Confluence! Went and digged around a little | Cannot do much until team is together | |
| 2 | Learn how Jira/Confluence works |
|
| |
| 3 | ||||
| 4 | ||||
| 5 | explore the software development tools we are to be using (confluence, jira) | explored the new Jira and confluence environments | still not 100% confortable with Jira and confluence. |
\uD83D\uDDD3 Monday <21/2/22>
Name | Priorities \uD83E\uDDD0 | Progress \uD83D\uDE0A | Problems \uD83D\uDE10 | |
|---|---|---|---|---|
| 1 | Sort out tasks and questions for big team meeting + tutor check-in | Sorted out team roles etc. in meeting, not much done individually | Still not sure about spec, and what we can actually do for sprint 1 | |
| 2 |
|
| Still not entirely sure what the requirements are and the broader context of the project | |
| 3 | Sort out team roles Understanding spec | Re-reading through spic and asking members for help - 40% unclear. Finalised team roles | Confused about spec and the requirements of API (4) - what that entails. | |
| 4 | ||||
| 5 |
|
|
|
\uD83D\uDDD3 Thursday <24/2/22>
Name | Priorities \uD83E\uDDD0 | Progress \uD83D\uDE0A | Problems \uD83D\uDE10 | |
|---|---|---|---|---|
| 1 | Finish requirements in order to do other things (interface, issues + sprint 2 planning) Ticking off marking criteria for sprint 1 | Explored Jira. Started writing requirements on tuesday, wrote more requirements since (user stories etc). Started interface document. Tabulated Architecture document. | Not sure if requirements is specific enough/meets criteria Feeling a little behind and stressed with timeline | |
| 2 | Get to know the spec and try to understand what is required | Allocated team roles and got to know more about how Jira and Confluence work | Not knowing the wider context of the task and trying to figure out what that means for our task. | |
| 3 | -Create issues on board → consider priority, tags, assign members | Update : completed by end of the night Using a lot of online tutorials to understand. | Initial problem with issues - disappeared, yet could be traced back when looking at the backlog. | |
| 4 | Working on setting up Jira. Tech stack. | Worked out issues in Jira. Completed different options for tech stack. | Can’t seem to connect up github repositories. | |
| 5 | begin user stories and start working on the needs of the users started looking into local hosting on raspberry pi | began user stories, worked on the requirements of the api and built a better understanding of the spec |
\uD83D\uDDD3 Saturday <26/2/22>
...
\uD83D\uDDD3 Tuesday <Date>
...
Name
...
Priorities \uD83E\uDDD0
...
Progress \uD83D\uDE0A
...
Problems \uD83D\uDE10
...
\uD83D\uDDD3 Monday <Date>
Name
Priorities \uD83E\uDDD0
Progress \uD83D\uDE0A
Problems \uD83D\uDE10
Name | Priorities \uD83E\uDDD0 | Progress \uD83D\uDE0A | Problems \uD83D\uDE10 | |
|---|---|---|---|---|
| 1 | FINISH SPRINT 1!!!! Try to get enough detail so Max will mark us well | Roadmapped with epics. Wrote some more issues with subtasks. Assigned tickets. | Not sure what to put in the planning doc, but am working on it. Also unsure of detail needed for tickets. NOT SURE IF TASKS NEED TO BE BROKEN DOWN MORE?? | |
| 2 | Finish the requirements for sprint 1 | Thought about the constraints of the project and potential ways to lessen the effects | Not sure on the amount of detail required for the sections | |
| 3 | Finish architecture document. | Was able to finish the architecture document. Finished up a summary of the options and then wrote why we will be using the options we’ve picked. | Had to email Max about the persistence as couldn’t quite understand it. | |
| 4 | 5 |
\uD83D\uDDD3 Wednesday <Date>
...
Name
...
Priorities \uD83E\uDDD0
...
Progress \uD83D\uDE0A
...
Problems \uD83D\uDE10
Finish off sprint 1 + Communication - Finish off the sprint retrospective as a team | Currently working - set up table. | Trying to add enough detail, to show our logical thought process. | ||
| 5 |
| translated the interface design from confluence into swagger. | still not 100% comfortable with swagger. there are some minor aesthetic issues in the documentation |