2022-02-21 Meeting notes
Date + Time
Feb 21, 2022
Time : 10:30am - 12:00pm
Location : Virtual - discord
Participants
@Tay Leung
@Garvi Poudyal
@Former user (Deleted)
@Michelle Kaminski
@Joshua Smee
Minute Taker
@Garvi Poudyal
Goals
Finish agenda and discuss ways forward in starting the API
Discuss team expectations, skillset
Have team roles finalised by end of this meeting
Discussion topics
Presenter | Notes |
---|---|
Actionables |
|
Team Expectations (of team and term) | Edward :
Garvi :
Joshua :
Michelle :
Tay :
|
Skills and Experience | <everyone 1531> Edward: MIPS, C, Python Garvi: MIPS, C(limited) , Python, HTML(v limited) Joshua : MIPS, C , Python, Java (rusty) , ReactJS, Dart/Flutter Michelle : MIPS, C , Python, Tay : C , Python, Java(rusty) , Javascript + HTML + CSS (mediocre) , SQL |
Strengths of Each member / Even better if (logically according to individual member strengths / goals?) | Tay :
Joshua :
Michelle :
Garvi :
Edward :
Edward + Joshua : Strengths include hands on coding. |
Team Dynamics Have the team roles been allocated logically according to individual member strengths / goals? Has the entire team participated in the process of delegating team roles? | Garvi : Delivery Manager – Organises the meetings, ff we are slow on our deadlines, checking up on teammates and ensuring everyone is working at their tasks. Edward : Product owner - Understanding the spec Joshua : Scrum master - Overseeing the code in the project Michelle prefers to not be product owner - not enough knowledge of what we want Tay : Scrum master (with Joshua) → manager of people, keeping people accountable on tasks and providing help if needed. |
Confluence | Complete both the board and roadmap |
Additional Topics | -Sending an SMS + through email. -Send it as a downloadable email. Storing is also an option.
-Creating websites Output : Your output should be able to pass any correctly implemented validator mentioned in the “Invoice Validation” section of this document. (from spec)
Design the API done by week 1.
^^ Set this up for week 1 (1531 example) -API design on Swagger and Requirements on Confluence |
Additional Notes | https://app.swaggerhub.com/apis/J43163/fudge_api/1.0.0 ^ Take inspiration off of |
Action items
Decisions
- Team roles for each member
- How to structure our report → Each of the headings in the spec i.e. teams, communication etc etc.