2022-12-23 Retrospective

Owned by David Trapp
Last updated: Dec 23, 2022 by Lite Farm
2 min read

 

Date

Dec 23, 2022

Team

@Mwayanjana Bolokonya (Unlicensed) @David Trapp@Lite Farm @Anant Sunilam Awasthy (Unlicensed) @Richard Wasswa (Unlicensed) @Duncan Brain @Carolina di Lello (Unlicensed) @mika.pochta

Background

This retro is for S54: Monday, Dec 12 2022 - Friday, Dec 23 2022

Please add comments before the meeting! We’ll take a few minutes to add additional comments and discuss, then put together action items to operationalize suggestions.

Last sprints (S53) retro is here: 2022-12-09 Retrospective

Retrospective

S53 Discussion topics:

  • Noticing lots of back and forth on a few complex tickets (LF-2800 and LF-2801 in particular). What can we do as a team moving forward to try and minimize the amount of re-work? In particular I think there’s room for improvement around “tribal knowledge” like unit displays, systems of measure, display patterns, etc. that aren’t yet known to new team members.

    • Suggestions:

      • Heavy on pair programming to start

      • Small tickets to start

      • Focus on their strengths with slight expansion into areas they aren’t familiar with (e.g. if they are strong on BE, give them a ticket that’s mostly BE with just a little FE component)

      • Find out who knows a particular thing before diving into a ticket and connect with them

      • Doing a 1-hour code review of the app the first week, for example with Redux saga looking at containers and components

  • Feedback on hiring process. @Carolina di Lello (Unlicensed) and @David Trapp do you feel like your time was appropriately used in the interviews?

    • The assessment should be changed a little bit. Needs some more work on the back-end as well. Should also add a new table and do a migration.

  • How is everyone feeling about the change from two reviewers to one?

Start doing

Stop doing

Keep doing

Shout outs

Start doing

Stop doing

Keep doing

Shout outs

  • Taking a nice long holiday break!

  • Making Slack channels on a functional basis, e.g. “ui-ux”, “fs-hiring-dec-2022”, etc.

  • Incentives for contributors? e.g. After X merges, you get a t-shirt. After Y you get added to the website?

  • short meetings to discuss the issues/problems and PR review feedbacks.

  •  

  • Anant, for all his work on the project!!!! It has been a joy working with you and I’ve always appreciated your willingness to put in the extra effort. Also, thanks for sharing a bit of cricket with me!!! Had never really seen much about it and loved learning about it.

  • Boom! Second fix merged in for @Carlos Moreira (Unlicensed) - rockstar!

  • Great collaboration from @Duncan Brain on LF-2072 and it’s sub tickets

  • Big thanks to @David Trapp for picking up the slack and doing a great job on QA while Mwaya was out and Kevin was incapacitated

Action items:

@Carolina di Lello (Unlicensed) to add a few screenshots of unit displays and a link to Figma in action to the Unit displays write-up
@Lite Farm to modify the technical assessment to include some work around the back-end and a modification of the database, including a migration.
@Lite Farm to propose incentive tiers for contributors