S65 Retrospective
Date | Jul 19, 2023 |
---|---|
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 | @Denis Dovganyuk @Lite Farm @David Trapp @Carolina di Lello (Unlicensed) @Iván Perdomo @Joyce Sato-Reinhold @Duncan Brain @Sayaka Ono @Mwayanjana Bolokonya (Unlicensed) |
Recording | Posted in Slack |
Background
This retro is for the S65, roughly: Thursday, July 06th - Wednesday, July 19th
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 (S64) retro is here: https://lite-farm.atlassian.net/l/cp/L9WqHyBo
Retrospective
Discussion topics:
Team dedication vs expected delivery
We should take into account % of dedication to the project
Duncan specifically mentioned weighting the round robin algorith to take into account percentage dedicated to writing code.
Inefficiencies around how the work is split and who is waiting on whom.
Need to make it clearer on sprint planning what the priorities
PR review “merge time”
Prioritize review+merge over own development?
Split the work by “type” - feature development vs maintenance
Pair-programming?
By definition pair programmed work has a first code review.
Will re-approach after we have some data on transition from product created stories to engineering created stories
Start doing | Stop doing | Keep doing | Shout outs |
---|---|---|---|
|
|
|
|