Skip to content

12th October Tuesday

Jump to bottom
Lilly Daniell edited this page Oct 21, 2021 · 1 revision

Hello, it’s Lilly. One sixth of Team IO, which is made up of Shakira, Jordan, Tom, Ifrah, Boris and myself. At the end of two weeks we will have built an interactive web application based on a widely-known social networking site we’ll call Acebook. This is where we’ll chart the journey . . .

Team IO’s (frankly genius) name was invented by Ifrah — we all have either an I or an O in our names (or both if you’re Boris) and it stands for input / output, as well as being a domain extension for tech startups.

The name became the foundation for our USP - giving us the inspiration for IOBook - a network specifically for programmers, which is more sociable than LinkedIn and GitHub, and easier to make friends and present snapshots of your projects to your tech community.

Shakira was randomly selected by Siri to be scrum-leader today, and after a couple of hours of self-study in the morning, we kicked off with the stand-up and planned an outline for the day:

  • Build upon the wireframes layout we created yesterday in Figma, guided by Shakira who explained the tool to the rest of the team.
  • We created a colour palette for our app using coolers.co
  • Limit Figma design to a 2-hour timeframe and then move on, as a group, to domain modelling, CRC cards, Database structure, MVC — so we can start tomorrow coding in pairs.
  • We'll convert some of the Trello instructions into User stories and include them in the readme.md
  • We'll decide on an MVP that we aim to deliver by this Friday.

Some other notes from the meeting:

  • We’ll follow a branch naming convention: initials_of_pairs/branch_name
  • Someone outside of the pair’s branch will confirm pull requests to be merged
  • We’ll finish for the day after the retro at 5.30pm
  • When to break will be discussed and decided on between each pair when the begin for the day
  • Keep conversations to threads on slack
  • There are no stupid questions!

We’re well in to the planning stages of our web app engineering project, and as a team we're all giving input to the layout, design and functionality.

Clone this wiki locally