Standups

Fudge

@Max Owen

@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

@Michelle Kaminski

Wrap my head around the requirements of the project

• Read over the spec for sprint one

• Started to think about some of the tasks

• Not very much detail in the spec as it was quite vague.

• No access to Jira/confluence

@Garvi Poudyal

Reading spec - trying to understand the big picture - consider sprint planning.

Understand the teamwork requirements - types of group interactions.

Read over spec - trying to understand how the API works.

Jira and Confluence have not been set up yet

@Joshua Smee

Reading spec and trying to understand aim of the project.

Read over the spec. Starting to understand how our smaller project stands within the larger construction.

The links between the different parts is quite complicated.

@Former user (Deleted)

keep up to date and stay in the loop

checked teams, discord, fb

too many layers of communication.

@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

@Michelle Kaminski

Learn how Jira/Confluence works

• Got our teams sorted for Jira and Confluence.

• Had not yet had another group meeting. So could not make much more progress on the project

• Still not sure about the spec

@Garvi Poudyal

Set up Jira and Confluence

Ensure meeting minutes are all on confluence and not on google docs.

N/A

@Joshua Smee

Learn Jira and confluence

Fiddled around with Jira and Confluence and feel more complicated using it to work further on the project.

Jira is not a very clear program. Unable to link a git repository to it.

@Former user (Deleted)

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.

@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

@Michelle Kaminski

• Get to know the spec and the details of what is required.

• Assign group roles

• Assigned group roles

• Discussed the spec and what we thought was required

Still not entirely sure what the requirements are and the broader context of the project

@Garvi Poudyal

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.

@Joshua Smee

Understandign how our project stands within the bigger project.

Reread the spec with a greater focus on how our smaller function will integrate in with the other projects to understand what’s happening.

Still a big unclear on how the different projects are working together.

@Former user (Deleted)

• getting to know the spec

• created document “API requirements compiled” to put all relevant information in one place

• Not 100% sure on the spec.

@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

@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.

@Garvi Poudyal

Create issues on board → consider priority, tags, assign members. Need to consider story points, priority , subtasks and structure of epics.

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.

@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.

@Former user (Deleted)

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

@Tay Leung

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??

@Michelle Kaminski

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

@Joshua Smee

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.

@Garvi Poudyal

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.

@Former user (Deleted)

• get more comfortable with swagger for sprint 2

• Work on swagger documentation

translated the interface design from confluence into swagger.

still not 100% comfortable with swagger. there are some minor aesthetic issues in the documentation