/
2022-02-21 Meeting notes

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

Presenter

Notes

Actionables 

  • Asynchronous Standups on Friday 

  • Garvi set up the Jira / Transfer meeting minute notes (for tomorrow)  

  • Joshua - start looking at architecture 

  • Set up folders on Confluence (before tuesday tut)  

Team Expectations  (of team and term)

Edward : 

  • No mark expectations until the first iteration is complete

  • High expectation of the team in doing their best. 

 

  • Course will be us figuring out what path we want to go down for the assignment - building off the minimal documentation + researching.

Garvi : 

  • Communication - asking for help, there’s quite a few tasks that need to be completed.

 

  • Course : Team is still figuring out the spec. Making sure to reach out to tutors to fix quieres 

Joshua : 

  • Work relatively hard + communication - rely on your team 

  • We learn something in the course :))

Michelle : 

  • Figure out when other deadlines are, and actually work and plan

  • Being accepting of things/events in other people’s lives (if there are other things due or life events)

  • Similar expectations of term as others

Tay : 

  • Not slacking off + a lot of communication. Being okay to call each other whenever. 

  • Help each other - and be open minded and taking time out, if they can’t set up something etc etc. e.g. a bug. 

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 : 

  • Procrastinate -  need deadlines 

  • Good at picking up concepts and languages 

  • Enjoy working with others (pair programming) 

  • Will get work done! 

Joshua : 

  • Pick up languages quite quickly. 

  • Fast at completing tasks 

  • Limited at visual 

Michelle :

  • Very organised 

  • Experience in leading groups 

  • Time to understand, 

  • Good with deadlines - accountability

Garvi : 

  • Visual requirements + interface 

  • Organised

Edward : 

  • Struggle the most with organisation - keep me accountable. 

  • Stepping in and helping others, feel quite comfortable. 

  • Getting the work done, once starting. Disciplined to finish off task. 

  • Comfortable reading through code and helping with bugs 

  • Pick up languages quickly 

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. 

  • Input - UBL format and we need to send this. Sending the XML file. 

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

 

  1. Need to have 1 API call → return saying we’ve sent it 

  2. If there’s a problem, return a problem 

  3. Also need to do testing.

Design the API done by week 1. 

  • Have the URL - what it send and what it returns 



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

https://stackoverflow.com/questions/50767064/send-and-recieve-an-xml-file-from-client-to-server-using-python-flask

^ Take inspiration off of

 Action items

Reread spec and sprint 1 assessment
Asynchronous Standups on Friday
Garvi set up the Jira / Transfer meeting minute notes (for tomorrow)
Joshua - start looking at architecture   
Set up folders on Confluence (before tuesday tut)  

 

 Decisions

  1. Team roles for each member
  2. How to structure our report → Each of the headings in the spec i.e. teams, communication etc etc.

 

Related content

Standups
Standups
Read with this
2022-02-22 Meeting notes
2022-02-22 Meeting notes
Read with this
Interface
Interface
Read with this
2022-02-27 Meeting notes
2022-02-27 Meeting notes
Read with this
2022-02-28 Meeting notes
2022-02-28 Meeting notes
Read with this
Stack architecture
Stack architecture
Read with this