...
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. | Kim Roark Loveland to set up meeting to discuss story statuses/defects after this sprint |
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 | Team to pay special attention to story statuses, defects, and the Jira board this sprint to discuss ideas next sprint. |
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 | |||
...