Meeting #7

Follow up on action items from previous meeting

Tommy

2

Meeting #6

Updates

Everyone

10 mins

• What have you been working on?

• Do you have anything blocking you?

• What do you plan to work on?

Tommy: sitemap, meeting with directors, plan to do: c, update about state of project

Sergio: sitemap, completed all design tickets

Jarvis: Plan to do: how to refine style scape, how to design front page

Paula: design tickets. Todo: last tree test and wire frames

Abraham: backend tickets Blockers: trouble with backend

Jie:

Retrospective/Post-mortem

Spinner (minus Sergio)

15 mins

https://www.atlassian.com/team-playbook/plays/retrospective

Since we know the idea, 1 point for each section to speed up retrospectives.

Since we know the idea, 1 point each for each section to speed up retrospectives.

What went well:

• Dockerfiles and live reloading for all components - enthusiastic about learning new things.

• Learned Adobe XD and we used it to make the Sitemap.

• Learned some basic vue.js and vuetify

• Gained understanding of how to authenticate securely

• Learned about LDAP

• We made a lot of progress on the site map, we seemed to be taking a lot of ideas from our research and applied it to our design.

What we can improve on:

• Coding team didn’t host any meeting

• Range is not used quite often

• Could code more while learning; more team coding sessions if a time suits everyone?

• a bit more communication between design and coding team.. Range helps + combined standups

Next Steps:

• Use Range :)

• Fixed time as per when2meet for coding?

• Add coding session as a ticket

• Communicate blockers early

• Walking the board during jira

Internal Showcase Milestone

Tommy

2 mins

Internal showcase is set for the end of trimester 2. On the Jira roadmap, we will be finish with content syndication by then and would have move on to CMS. What we need to make sure is that the design and the frontend front facing customer part of the website is complete for an internal showcase and feedback session.

Updates on the current trajectory of the project

Tommy

10 mins

This sprint will be the most important sprint of the whole year. It decides whether we will be able to deliver on time.

• We need to complete at least half of what is left in content syndication. This is because as the semester ramps up and internship applying season comes around we won't have the time or mental capacity to dedicate to the project. Most of the tickets that are left are related to design.

• At this point we have completed the sitemap and need to finish wireframes for content syndication. This will require expertise and efficiency to undertake this task. This is an aspect of the project that I will monitor closely to make sure that it doesn’t fall behind and impede development progress.

• This means we need to play to the strengths and weaknesses of team members. Hence, Sergio will be working through tickets because your ability to move the project along and keep team members on their feet with your energy will be invaluable. Jie will join him because of his technical knowledge and speed in which he adapts to requirements. Jarvis will spearhead the completion of wireframes given that he has more experience than any of us. The discussion starts off with how many people Jarvis will need to help him get it done.

• Sergio, Jie, Abiram on coding team

• Sergio and Tommy working on architecture maps

• Jarvis and Paula on wireframes → make sure that the landing page is done, but the rest of the pages exist.

Feedback

• Questions?

• Comments?

• Concerns?