...
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 |
|---|---|---|---|
|
|
Action items:
- Review previous retro’s action items
- Meeting on how to make our sprints more efficiency? Kevin Cussen to add something to the calendar mid / late August to discuss and brainstorm.