Follow up points retro 04.11.22

[standeren]

• [x] Think about how we can prepare for/work with upcoming roadmap items @alle
  • [x] Make a slack thread to discuss ^ and/or do a roadmap review meeting @FinnurO
• [ ] Look into getting someone non-technical (domain expert etc.) on team @HanneLauritsen1967
• [ ] Get control of cypress testing in Azure pipelines (include @acn-sbuad and @altinnadmin? to distribute the knowledge) @TomasEng
• [x] Agree on our standard for doing review of PRs @mijohansen @alle
• [ ] Apply for a possibility to work overtime in November @HanneLauritsen1967
• [x] Everybody should share their opinions in these retro meetings @alle
• [ ] Assign one person being responsible for each area in the solution? @alle
• [x] Figure out if old converter code can be deleted, and potentially other parts of the backend code @mirkoSekulic @nkylstad
• [x] Try creating story points out of S/M/L estimates to view in chart @andrealouisestanderen

[standeren]

• [ ] Look into new arrangement of seatings at office @HanneLauritsen1967
• [ ] Look into getting someone non-technical (domain expert etc.) on team @HanneLauritsen1967
• [ ] Make issue: Get control of cypress testing in Azure pipelines (include @acn-sbuad and @altinnadmin? to distribute the knowledge)@TomasEng
• [ ] More coffee breaks together @alle
• [ ] Fix access to prod and dev resources @HanneLauritsen1967
• [ ] Discuss who is "responsible" for datamodeling externally @FinnurO
• [ ] Gather overall understanding of a unified solution including PDF, receipt, design @FinnurO
• [ ] Consider summing up the retro points in a different way - share retro tool in slack? @alle