Sprint 6 retrospective
- Lukas Reidinger
Analytics
T Overview
Reflect on past work and identify opportunities for improvement by following the instructions for the Retrospective Play.
Retrospective
Spend 10 minutes to write down what you think went well in this sprint and what needs to improve in the upcoming sprint. Togehter will discuss Actions to make those improvements.
What went well | What needs to improve | Actions |
|---|---|---|
Jason: Resources beeing disabled post events > make enabled Working on backend ticket stuck on it > talk to Kareem | Excape room is more of a times quiz not an excape room. | Nick: sprints should be mapped to bandwidth. |
Kareem: task for mini games keept growing in the same sprint.
| Improve sprint planing Use ep | Use epics do not use subtasks Have a peer review day on Wednesdays. |
Shruthi: Quick sprint, | Funkctionalities about tickets, Minigame test local, dev testing tickets were confusing > hudle with Bray to figure it out. | Use Epics. Make notes on a BE ticket that this is not testable by itself. Jason suggest to use notion for a template how a ticket should be layed out. |
Justin: Sprint is going well. Escape room is more work. Lot of extra design was added on, late in the game. Why do we need revisions? Only do if customer askes for it. | Escape room function might have needed to be more defined. Revisions will not be started yet, to much work load. First it needs to be solid. | Escape room should be in but comunication between Unity and Sidekick will not be there for V1. |
Riley: Did not work on Sidekick. |
|
|
Marcel: Did not work on any tickets. |
| Note working on a project, Helium packaging up differnt itmes, css, Tailwind |
Bray: PR for early version of engagement feture versioning. Mini game tickets review with shruthi. All mini games merged into dev.
|
|
|
Jason: Are we still working for Oct 3 rd deadline. |
| Kareem: Yes we are. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|