BTR Reflective Retro 19.2

Hi Team BTR,
This retro was concluded as a reflective retro so we could address any lapses and
Inspect and adapt as a team for better efficiency.
As we reflected on this sprint progress with the team and on this project it
was great brainstorming with you how we can get better and
become a high performing team.

Mural link
https://app.mural.co/t/citzservicebcbcros0435/m/citzservicebcbcros0435/1697471110203/3c6ec3b4271eb3781e31e107a728493bc40f7c34?sender=u2a165c8bb7d8735b0bd51331
Attendance
Absent
1. Avinash
2. Steve 1. Magdelena
3. Guna 2. Scot
4. Kial 3. Thor
5. Festus
6. Hrvoje

During the Retrospective Session we agreed on the following Action Points as an action point for the team .

What went well?
• Sprint Planning.
• Each team member helping others.
• Kick off conversation with IDIR.
• Profile Requirements getting clear.

What didn’t go well :
• a bit worried how we're testing the UI across the common/layout/main.
• really would like the CI running.
• UI deployment into dev not working.
• Requirements on UI could be clearer.
• UI deployment into dev not working.
• OCP upgrades broke a lot of things / caused many issues across all environments this sprint.
• Proactive check for environments availability for Register BO tickets
•

Actions to take.
• Dev meet on the above ways to mitigate testing.
• iron out a better process for releases that allows us to get things out quicker.
• plan for QA and fixes.
• Define flow of requirements more clearly Stakeholders -> UX -> tech

These are our takeaways from the reflective retro we had we had, we will work on these takeaways as we
Improve as a team. Thank you for being part of the journey so far.
We do appreciate any feedback and any other opinion that was not captured.
@Kaineatthelab , @trishreimer , @lmcclung

The issue contains retrospective notes and a Mural link but names no repository file, test, or entry point. Review the listed concerns around UI testing, CI, deployment, releases, QA, and environment availability first. There is no defined completion condition or scoped deliverable, so the issue needs clarification before work can begin.

Written by the indexing model from the issue text.