Fill in retro details in the table below. Type /date to quickly add the date and @mention participants to help them find the page.
Background
This retro is for the S64, roughly: Thursday, June 22nd - Wednesday, July 5th
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 (S63) retro is here: https://lite-farm.atlassian.net/l/cp/W40t1L3K
Retrospective
Add your Start doing, Stop doing, and Keep doing items to the table below. We'll use these to talk about how we can improve our process going forward. |
Discussion topics:
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)
| |
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.