Service Principal Retro - M1- Sprint 13

Retrospected Session

Date: Friday, 18 December 2020 at 12:21:10 GMT-06:00

URL: https://rdc-retro.azurewebsites.net/game/40_5xClke

Participants: Alfredo, AndyB, Nsikan, Ryan, jk, ljf9345iorlk345

Posts: 18

Votes: 31

(+4/-0) Quick turnaround and fixes for issues encountered during provisioning
(+2/-0) Great teamwork!
(+2/-0) Transition Speed
(+2/-0) I know how frustrating it is when you have stared at something for weeks or months, then you have a “user” who doesn’t know where to click. The team were incredibly patient when that happened.
(+1/-0) Even though we were in a time crunch, the team took the time to stop and explain a technology or concept even if it wasn’t clear, which really helped with context.

(+5/-0) Learned that documentation should be aimed at ultimate handoff recipient (with separate env and expertise) and not current development team
(+3/-0) Reaffirmed the criticality of observability
(+2/-0) How to mount a new file share to Cloud Shell
(+1/-0) Hardcoded resource names should be limited to reduce complexity of handoff
(+1/-0) Cosmos DB was new to me, so this was a great opportunity to learn about it in a real world context

(+3/-0) Test scenario walkthrough - customer perspective
(+1/-0) More robust setup in workflow before integration testing
(+0/-0) It might have helped to get core a dependencies list to me before we started (which GIT this would live in, prepping a Cloud Shell with persistent storage etc.) so we could hit the ground running.
(+0/-0) A broad contextual overview of what we were going to do, before we started, would have helped, to make sure all parties were on the same page and there were no knowledge gaps or inaccurate assumptions being made.

(+1/-0) Physical presence - walk throughs of setup and provisioning are much slower over video call
(+1/-0) Autogen of environment needed by git workflows
(+1/-0) Process for transition of code to customer
(+1/-0) CloudShell environment setup process
Action Items