/
S82 Retrospective

S82 Retrospective

 

 

Date

Mar 14, 2024

In sprint

@Anto Sgarlatta @Joyce Sato-Reinhold @Denis Dovganyuk @Duncan Brain @Sayaka Ono @David Trapp @Loic Sans @Kevin Cussen @Navdeep Dhammu

At retro

@Anto Sgarlatta @Joyce Sato-Reinhold @Denis Dovganyuk @Duncan Brain @Sayaka Ono @Loic Sans @Kevin Cussen

Recording

Not recorded

Background

This retro is for the S82:

Thursday, February 29th

Wednesday, March 13

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

Discussion topics:

  • Weekly stand-ups working still? No comments

  • How to understand whether something in “Development” is 20% done or 90% done as we’re coming up on Sprint planning in order to appropriately scope the following sprint.

    • For stories in sprint you can look at sub-tasks and assess based on the number of “Done”

    • You can filter for sub-task on the active sprint screen and see how many aren’t yet in “Done”

    • @Lite Farm to start checking asynch starting Monday before the end of the sprint

Start doing

Stop doing

Keep doing

Shout outs

Start doing

Stop doing

Keep doing

Shout outs

  • Check in about estimated spillover during the last 3 days of a spprint (M, Tu, W)

  • Resigning from LiteFarm +1

  • Validation step - not a reflection of best practice, but a reflection that @Lite Farm isn’t doing it and that unless @Loic Sans and @David Trapp want to do this - it won’t have any owner for some time.

  • Catch up sprint when we’re falling behind – feels good to have almost completed scope for the past sprint!

  •  

Action items:

Review previous retro’s action items

 

Rollover action items from last time

@Lite Farm to put together a proposal on how team meeting cadence looks
@Lite Farm to schedule a team discussion on the appropriate mechanisms for verifying a release will be successful (e.g. bug free)
Look into Jira: is there a way to calculate and track the portion of time spent on feature vs tech debt @Anto Sgarlatta
Begin a Confluence doc on things you want to learn and things you’re interested in teaching and then schedule sessions around them @Anto Sgarlatta

 

Related content

Sprint planning - S83
Sprint planning - S83
Read with this
S81 Retrospective
S81 Retrospective
More like this
S87 Retrospective
S87 Retrospective
More like this
S98 Retrospective
S98 Retrospective
More like this
S89 Retrospective
S89 Retrospective
More like this
S90 Retrospective
S90 Retrospective
More like this