\uD83D\uDCCB Overview
Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.
...
YSB: Complete first two levels of AI mentor studio issues. – Complete!
YSB: Complete Accessibility & Performance Testing – Complete!
YSB: Release 3.1 – Complete!
FAS: Send Divide General Funding - Startup/Research Feature to UAT – Complete! (Ready for UAT, Final story may be sent to Linda after her PTO)
CEA: Finish Front End Updates – Dev complete!
CEA: Complete QA Process for Stories coming from Caprese Salad –Initial review complete – Defects found, but Goal completed!
SDF: Complete all defects in Sprint – Incomplete – Blockers removed and team ready to complete remaining defects by mid-next sprint
Team met 8/13 to discuss next steps and confirm work to be completed. The expectation of having this work done as first priority is clear.
FMP: FMS Med 3 - Identify and contact users & send instructions to Help Desk – Complete!
YAM: Figure Out Breakdown of the Counts – Blocked - Need Additional input from Daniel
Arts Cal: Architecture Document – Complete!
\uD83D\uDCAD Retrospective
...
Shout Outs | Struggles | Ideas | Commitments |
|---|---|---|---|
Chris for all the help!
| Not taking QA Availability into account in sprint Planning | Change how we do UI/UX stories. Carrying over many incomplete stories that are outside of our control | Team commits to having larger conversation about story size: Ask Kim to help deliver larger stories (IE, making “Create, edit, view, delete” functionality all one story, eliminating separate popup stories) Devs collaborate to create more/specific subtasks This will also help with proper time tracking |
Becky always stays positive and makes things happen | Stories not ready | Plan for QA availability even if it means going slower | Becki to commit to re-investigate Game Lunch |
Rosa and Selene for helping prioritize work focused on releases | Defects are created that block the original story, when they are not defects but improvements | Slightly larger tickets to cut down on duplication of Code Review, Unit Testing, Deployment, etc. subtasks which add up to extra money spent for clients. Make more subtask instead of more stories when possible -- Ask Kim to help deliver larger stories (IE, making “Create, edit, view, delete” functionality all one story, eliminating separate popup stories) Devs collaborate to create more/specific subtasks This will also help with proper time tracking | Ask Netal to investigate team outing! |
Nestor for all his great work on the CEA visual refresh!
| Sometimes the Acceptance Criteria is ambiguous | Peer review and feedback on Goals/performance throughout the year | Investigate re-ordering statuses in the dropdown menu |
Chris for thoroughly documenting the charting options for CEA clients
| Scope misunderstanding between clients and team for CEA project. | ||
QA for finding all the defects on CEA ASAP | Dev work and QA work still not sync’d up for closure during sprint on certain tickets (leaving story points on the table) | ||
Jesús Rangel always available to help and support in anything OutSystems related or YSB
| Sometimes we are underestimating dev time for some stories/task | ||
Chris Cadden for all the mentoring and tutoring for my FY25 goal! | Lots more overhead/admin time with new ticket refinement process – less time for actual dev work. | ||
Edward Morcaldi for tackling FRMS on this sprint in OutSystems | Burnout | ||
Not enough QA resources to cover all the project work added into the sprint. | |||
...