Skip to content
2022 Sprint #22-24 Retrospective
select your name...[[
Assignee: Alexander Panin 0
Map Coda User to Jira Assignee
People: Alexander Panin submitted with average sentiment of
Should be closing the previous sprint sooner so we can have a normal 2 week sprint, even if we don’t add new issues.
There are no rows in this table
Need to make sure feature branch matches master branch (the branch to which you will merge) For request changes, better to have Han or Aaron on the ticket to review before merging Create slack channel to reserve ids for firestore or mysql? (to prevent merge conflicts) Perhaps discuss implementation approach during backlog refinement before estimating(?) Add more info in pull request to explain why/how you’re approaching the solution you chose. (follow Aaron’s example which helps explain logic!) [esp useful for bug fixes] when making a bigger, more fundamental change (not just isolated to one part of code)...should disseminate info to broader group ET-4278...This should have been labeled as BUG ET-4315 (Han) this was more of a research ticket, still ongoing (lower priority) Urmat/FuMing to look at Implemented/Review columns and prompt individuals to move them forward (to done) If Antony has feedback not related to ticket, let FuMing/Urmat... During standup, indicate whether there’s risk of not completing your tickets by end of sprint Garry: Bugs do take a lot of time which impacts progress on burndown chart (should we estimate them?) if not, reserve 30% bugger for bugs Standup: stickers on board, can better visualize (can help one another vs just taking something new from backlog) Add people from team for pull requests unless good reason to ask someone from other team (based on expertise, domain knowledge) In smaller teams, get more focused on code reviews with someone other than Han/Aaron reviewing Smaller teams will help us do more significant stories in a sprint (because of gains from team collaboration) Han: Remove longer-term tickets (Slava and other tasks [investigative/dev-ops/etc] which take longer) from sprint...can just apply hour estimations for these instead Q: When devs don’t have tasks (waiting for previously assigned tasks in review), should the new tickets they pick up be added to the current sprint or just worked on from the backlog?
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (