Govstack SandBox Retrospective #4
Date
Mar 14, 2023
Participants
@Farina Owusu @Nico Lueck @Martha Vasquez @Oleksii Danyliuk @jarkkohyoty @Bert Viikmäe (Deactivated) @Artun Gürkan @Priit Puru @Jonas Bergmeier
Goals
Recall team progress and identify pain points to improve
Discussion topics
Action items
| Issue | Action + Owner |
---|---|---|
1 | Meeting minutes and meeting time | Timer should be handled by facilitator or meeting minutes taker for item-wise full/crowded meetings |
2 | Communication between vendors and working groups | attend TC if you want to learn more about overall progress |
3 |
| update our teams page regarding responsibility areas @Heidi Kuum (Deactivated) Mar 24, 2023 |
4 |
| overview of knowledge sharing possibilities could be set up and shared from general GovStack (onboarding page) @Nico Lueck @Farina Owusu Mar 31, 2023 |
5 | Physical team event for socializing | set up confluence page for opportunities and share with team@Meelis Zujev (Deactivated) Mar 21, 2023 |
6 | Feedback | if possible, provide guiding questions for reviews |
7 |
| Technical matter: New GovStack architecture group might be a good new exposure claim slots on demand for technical reviews cc @Meelis Zujev (Deactivated) @Heidi Kuum (Deactivated) @jarkkohyoty |
8 |
| provide traceability for feedback if you expose work results |
9 | BB vendors would keep in mind requirement about running app in cloud. | @Oleksii Danyliuk collects thoughts on technical “issues” regarding this and schedules follow-up including Nico and Jukka Mar 21, 2023 |
10 |
|
|
11 | Approach me (Nico) on some issues during sprints. Still, I feel protected from some issues? (maybe because of workload?) | regular session like weekly standup could be established @Meelis Zujev (Deactivated) Mar 20, 2023 where possible, move questions, chats and issues to GovStack #sandbox channel except for internal and organisational topics |
12 | Deploy BB in Sandbox can be huge task, bb may have a lot of component or may be tricky to create running setup in our sandbox that takes a lot of time. | covered by → BB vendors would keep in mind requirement about running app in cloud @Oleksii Danyliuk |
13 | (G)estimation for our activities to be afterword evaluate the learning and improve from that | stays a desire for now → should be reviewed when feasible to introduce |
14 | Get an impression of the vibe in the team. E.g. exciting work or business as usual? | see #11 next retrospective Happiness radar | FunRetrospectives @Jonas Bergmeier |
15 | More UI stuff to do for me - not just wireframes | asap! |
16 | that shared work results “sink in” after 1-2 exposures |
see #6 see #4 |