- Tim: liked the process. The working mode matured a lot, feels like we're getting into a good cadence of working together.
- Barrie: a lot of helpful changes in IQDB, Jacob and Barrie worked on cards together
- Fernando: things were more structured, JM reported bugs earlier, getting better about communicating
- Johnny: things went well, with quality without killing ourselves, created the "convergence" process - everyone contributes - the voice becomes how code/completeness/testing gets measured as a team voice
- Alex: a well spec'd out ticket, communicating with jacob a lot.
- Andrew: we did planning well. it resembled a sprint.
- Jacob: codified out scrum process, looked forward and set up quote-web for success
- Tim: be a little more user centric "delightful". Sitting in our glass castle, tech capable, but the users we ship to are not as tech savvy on things we find obvious. US issues, bugs or performance. Like for us to be more aware of that at all times.
- Barrie: we don't have a dedicated design resource and it causes frictions
- Fernando: certain changes that happen in tickets that don't take into consideration global concerns. Changes are not well understood in terms of what exists in the existing app
- Johnny: running into a lot of friction with a semi-remote team with different hours, realizing that differences in backgrounds and opinion don't serve the project well.
- Alex: didn't think about the repo for the player before starting to work on it. Schedule was a waste of time, but we didn't have the designer to make the product sane. tech stack slowed him down.
- Andrew: an eng will be working on a ticket, as they are, major pieces will come out. He would like to figure out a way to address those that doesn't require making a quick decision but rather take the energy/time upfront to talk through.
- Jacob: Gary hasn't been a part of our tech focused conversations and we need to include him and leverage his skills
- splitting up big tickets
- Tim: ask what the user is thinking
- Finding a designer, do a job description
- list out things that exist today that are close to it within the app
- communicate more about the above
- johnny: collaborate before, not after. create unified team voice and consistency. self consistency.
- alex: ask earlier. think before you move. keep figuring out what our code should look like.
- Andrew: take time to think through and answer questions when they arise
- Jacob: break out big tickets, don't do work on stuff without tracking it on jira