Standups

All team members should provide their priorities, progress, and problems each day in this report.

\uD83D\uDDD3 Thursday <17/2/22>

	Name	Priorities \uD83E\uDDD0	Progress \uD83D\uDE0A	Problems \uD83D\uDE10
1	Tay Leung	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
3
4
5

	Name	Priorities \uD83E\uDDD0	Progress \uD83D\uDE0A	Problems \uD83D\uDE10
1	Tay Leung	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
3
4
5

	Name	Priorities \uD83E\uDDD0	Progress \uD83D\uDE0A	Problems \uD83D\uDE10
1	Tay Leung	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
3
4
5

	Name	Priorities \uD83E\uDDD0	Progress \uD83D\uDE0A	Problems \uD83D\uDE10
1	Tay Leung	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	Michelle Kaminski	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	Garvi Poudyal	-Create issues on board → consider priority, tags, assign members		Initial problem with issues - disappeared, yet
4	Joshua Smee	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