/
S64 Retrospective

S64 Retrospective

Owned by David Trapp (Unlicensed)
Last updated: Jul 19, 2023
2 min read

 

Date

Jul 5, 2023

In sprint

@David Trapp (Unlicensed) @Mwayanjana Bolokonya (Unlicensed) @Javier Antonio Hernandez De Paz @Carolina di Lello (Unlicensed) @Duncan Brain @Sayaka Ono @Joyce Sato-Reinhold @Denis Dovganyuk @jeremy.bennett8 (Unlicensed) @Cedric Levasseur-Laberge (Unlicensed) @Gursimran Singh @Iván Perdomo @Lite Farm @Shang Heng Mak

At retro

@David Trapp (Unlicensed) @Mwayanjana Bolokonya (Unlicensed) @Carolina di Lello (Unlicensed) @Duncan Brain @Sayaka Ono @Joyce Sato-Reinhold @Denis Dovganyuk @Gursimran Singh @Iván Perdomo @Lite Farm

Recording

Posted in Slack

Background

This retro is for the S64, roughly: Thursday, June 22nd - Wednesday, July 5th

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 (S63) retro is here: https://lite-farm.atlassian.net/l/cp/W40t1L3K

Retrospective

Discussion topics:

  • Your topics here…

    • Jira ticket format review

      • Technical document review

      • Functional Requirements / Design process review

      • Ticket format / “How to make good tickets”

        • Templates for different ticket types

    • Attending Design sessions - I may have changed my mind devs could participate more - @Duncan Brain

      • With repeat crop plan there have been a lot of iterations - might have been better to get engineer input earlier.

      • Without dedicated attention to a story / epic it’s hard to flag feasibility issues earlier. Need to have an “implementer” mindset when looking at screens / requirements.

      • Storybook may make a back and forth between design and engineering easier. This is fine, but time is a constraint

Start doing

Stop doing

Keep doing

Shout outs

Start doing

Stop doing

Keep doing

Shout outs

  • Proposal: One single person leads a feature to completion (not only tech lead)

  • Proposal: Document functional and technical requirements, leave issues for tracking the progress

    • Use Confluence for overarching documents and then track individual tasks on Jira. There is a lead on functional requirements and then a technical lead to create technical documentation. Example

    • Functional requirements also need to connect the team with the domain knowledge - the experience of the users.

  • As you’re thinking about a problem or implementation, take the time to write it out - it helps you think through the issue. Everyone can do this, not just a “lead”.

 

  • Reviewing the action items from the previous sprint retro

  • reviewing tickets in the daily

  • Tech Daily agenda document

  • Owning implementation and specific areas of the codebase (getting support from tech lead but not assuming they will own it)

  • Everyone is awesome!

Action items:

Review previous retro’s action items
@Duncan Brain to update document communication and make sure that Github auto-assignments are described and that they take place for folks outside the core team
@Lite Farm put together a session for reviewing current requirements → engineering process. Include discussion of overall process including how and when to incorporate engineers and feasibility into the design process.

Related content