S83 Retrospective

Background

This retro is for the S82:

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 (S82) retro is here: S82 Retrospective

Discussion topics:

• What is the structure to ensure tickets in sprint planning have already been groomed?

  • Rather than making all states ahead of time for planning, would it be easier to just do the basics and then reactively do the states where there are questions or comments from engineering?

    • @Loic Sans “No, it’s part of my design process.”

  • One thought: Grooming could more concretely focus on the next sprint rather than touching on several topics that will be worked on over the coming months.

  • Should there be a design flow similar to engineering? For example using the LUX board with various stages, e.g. “Farmer success review”, “Ready for grooming”, etc.

    • @Duncan Brain sees value in this.

    • @Loic Sans thought it would difficult because design scope is squishier.

• Sprint logistics for transition

  • Document making

    • Also can we get the holidays/timeline spreadsheet

  • Meeting invites

    • @Joyce Sato-Reinhold will do so!

  • Transferring from product timeline to sprint goals / scopes

    • @Lite Farm will create a document outlining key deadlines for FY2024 and when we should release to satisfy each of those. During “the transition” it will probably come down to what is most ready for working and then that will become the next sprint.

    • Once we have a new product person, they will proactively chunk sprints

  • Dedicated/rotating “speaker” role?

    • Just facilitation could be a 1 pointer that is claimed at every sprint planning session

    • Actually prepping AND facilitating (esp. sprint planning) would likely be more in the range of 2 - 3

  • Any other changes to meeting goals etc?

    • Anto had been assigning tickets to the engineering team - should we continue this or should folks volunteer for them at sprint planning?

      • Volunteer based post-pointing session post-planning

    • Should we look at closing out tickets on the kanban before starting S84?

      • No one is doing validation for the time being, so once verified the ticket is “Done”, @Lite Farm will make this transition in Jira

    • @Joyce Sato-Reinhold misses the dedicated pointing meeting (this was a casualty of Focus Friday).

      • Dedicated pointing session post-planning

  • Agile bot admin

    • @Joyce Sato-Reinhold to become admin!

Action items:

Rollover action items from last time