/
Retrospective: Sprint Caprese Salad

Retrospective: Sprint Caprese Salad

Owned by Rebecca Schneider, created
Last updated: Jul 31, 2024 by Kim Roark Loveland
2 min read

 Overview

Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.

Date

Jul 31, 2024

Team

CAD Team

Participants

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.

 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

Shout Outs

Struggles

Ideas

Commitments

  • @Nestor Rodriguez Ayala to set up time to discuss CEA testing with @Selene Gutierrez and @Rosa Illescas (optional)

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.

  • @Rebecca Schneider to come up with a way for folks to leave anonymous feedback about retrospective.

Devs for fixing so many issues reported and doing their job at the same time

image-20240731-152909.png image-20240731-153009.png

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

image-20240731-152919.png

Trying to deal with the project work and support for Outsystems.

 

 

Kim and Becky for giving guidence in priorities daillyimage-20240731-152925.png image-20240731-153257.png image-20240731-153258.png

Doing Retro on confluenceimage-20240731-153311.png

 

 

Team (including management) working together to decide to push 3.1 release. image-20240731-153309.png image-20240731-153311.png

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.image-20240731-152932.png

QA tasks remain in testing status for many time because of issues image-20240731-153424.png

 

 

QA and Devs work everyday is more syncronized image-20240731-153235.png image-20240731-153239.png image-20240731-153242.png

 

 

 

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.

 Action items