\uD83D\uDCCB Overview
Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.
🥅 Goals
FMP - URO Artemis Report
Status: Cancelled Halfway Through the Sprint
Client did not want to pay for new report
Yale Status Board - Complete Regression Testing and UAT for 3.1
Status: Complete
YPH-CEA - Redesign of Charting Pages Complete
Status: Dev Complete
Demoed for Client!
Umbicalc - SDK Update
Status: Contributors on PTO
FAS - Test Cases done by 7/25
Status: Incomplete
Identifying defects throughout testing process made the time estimate longer
Too many stories on the sprint
SDF - Plan migration
Status: Partially complete
Becki needs to confirm the dates
Contingency details need to be discussed with Netal
Yale App Manager - Complete research work on Shared AOs & Complete COA functionality.
\uD83D\uDCAD 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.
Shout Outs | Struggles | Ideas | Commitments |
|---|---|---|---|
| |||
CEA backlog refinements and planning where great | FAS tasks not moving as the priority. Later it was solved in the Sprint.
| To have a “Dev Rework” or “Reject” or something similar in Jira so tester can be aware that they are waitting a fix instead of openning each time all the tasks. |
|
Devs for fixing so many issues reported and doing their job at the same time
| QA using a new tool “qtest” to manage all the work. It takes some time to get accostumed to use it. But fortunatelly it is much better than “ALM” | To have a dashboard focused in work to be done. So devs and testers can take the next task in the queue. Of course if it is possible. | |
QA for quick turnaround on YSB 3.1 Tickets | CEA - Learning a new framework on the Go for both backend and frontend
| When possible, have a meeting devs/design to discuss any complicated UI/UX implementation | |
Grecia for the great CEA Design
| Trying to deal with the project work and support for Outsystems.
| ||
Kim and Becky for giving guidence in priorities dailly | Doing Retro on confluence | ||
Team (including management) working together to decide to push 3.1 release. | No clarity on the testing effort for CEA. | ||
Thank you to Kim for all her support and helping answer questions that came up with testing. | QA tasks remain in testing status for many time because of issues | ||
QA and Devs work everyday is more syncronized | |||
Great communication from QA and Devs | |||
Good to have a new UAT status in Jira | |||
Votes
Copy and paste the votes below on the bullet points you want to discuss.
Add Comment