Versions Compared

Old Version 1

changes.mady.by.user David Trapp

Saved on

compared with

New Version Current

changes.mady.by.user David Trapp

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties

Date

21 Jun

In sprint

David Trapp 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 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

...

  • 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

  • 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.