# Shield Retrospective Notes 2024

## March 11 - March 15, 2024

### Liked
**Courtney** - Love that Katie reaches out to me with questions or to confirm things with functionality of the UI. Great collaboration!
**Courtney** Welcome to the Team Ryan!

**Katie** - welcome to shield Ryan!! He's picking up his first story today and hitting the ground running
**Katie** - Always great collaborating with Courtney. She is always so responsive to my questions/feedback and on top of any adjustments that may need to be made
**Katie** - You can tell that Dan is really starting to feel comfortable on the team. He has been doing really great work these past couple of weeks

**Dan** - Welcome to the team, Ryan!
**Dan** - Renovatebot PRs are steadily getting completed

**Wade** - Remember, if we are breaking things, we're learning not to fail later.

**Jillian** - Happy to hear Ryan's onboarding went well with Dan, Katie, and Wade.
### Learned
**Courtney** - I can pay better attention to the board for stories that involve my work and I will attend more standups the weeks that have it.

**Katie** - tracking our renovatebot stories on the board has been a great way to ensure we are keeping up with them. I'd like to continue doing this!

**Wade** - I learned that I still know how to manually issue appointments!

**Dan** - I learned how fast PagerDuty will call if I don't acknowledge an issue fast enough.
**Dan** - I second tracking the renovatebot stories on the board being helpful in seeing the work and making sure we keep up with it :)

### Lacked
**Katie** - was there a way we could have avoided yesterday's incident with appointment issuing? Maybe we need to consider expanding the areas we are testing for SCIM integrations? Should we consider a post-mortem?

**Wade**- Continuing with Katie's suggestions, I wasn't sure what we missed in testing. Hopefully a post-mortem would expose how it was missed.

**Brandon** - I need to have better communication with the devs. Especially as these stories get more complex.

**Dan** - Could having a revert plan in place have be helpful to handle yesterday's incident? We didn't have a revert PR and we were unsure if it was safe to revert

### PTO
**Wade** 3/18-3/20

---

## March 4 - 8, 2024

### Liked
**Jillian** -very happy with the progress we have been making the past couple of sprints
**Jillian** - happy to hear the meeting went well and will have no shortage of work in the upcoming year

**Brandon** -It was a slower week as far as testing goes but we got a couple of stories across the board.

**Katie** - Onboarding with Ryan went well!
**Katie** - Great outcome from our planning meeting, looking forward to the next couple quarters of work.
**Katie** - Shoutout to Dan for helping me with the React portion of SHD-436, since my React is very rusty. Pairing has been great!

**Dan** - Planning meeting went really well.
**Dan** - Pairing with Katie with the React was great

**Wade** - Seeing the team in person!

### Learned
**Katie** - I need to brush up on React 🙂

**Dan** - I need to remember my badge when I come to the office

### Lacked

### PTO

---

## Feb 19 - March 1, 2024

### Liked
**Jillian** : It is great having Carlos back on the team to help with all of the SCIM work which also allows for Katie and Dan to stay in their swim lanes and make progress elsewhere! This is a huge win for the team.
**Jillian** : Really looking forward to having Ryan join the team next week. He will be in a lot of onboarding , but lets do what we can to get him up to speed.

**Carlos** : Excited about a new team member in SHIELD and looking forward for his contributions!
**Carlos** : The progress in SCIM sync is making is good

**Brandon** : Good week getting stories across the board.

**Jon** : Great week testing the teams stories!
**Jon**: Shoutout to brandon for his help this week

**Katie**: The team has done a great job at moving stories across the board the past two weeks.
**Katie**: Discussions with the mobile team and Jenny about priority were reassuring we are marching in the right direction.
**Katie**: I feel like I say this every other retro, but collaborating with Courtney is always great. She really listens and works hard to make sure she understands the requirements we have, as well as industry standards.
**Katie**: Carlos has been doing a great job with SCIM, shipping those stories incrementally. It has been great having him on the team these past few weeks.
**Katie**: Looking forward to our new teammate joining!

**Dan**: We're getting another dev!
**Dan**: Great discussions around our priorities
**Dan**: Kudos to Ben for taking care of several PRs
**Dan**: Carlos is quickly putting out the SCIM work

### Learned
**Carlos** : Testability of some of our stuff isn't great, and having a nitro-id environment up for testing is sometimes safer

**Katie**: We'll need to put together an outline for bringing Ryan up to speed when he joins the team.
**Katie**: Our priorities will be shifting a bit once we wrap up the security work. We'll be taking on further support for the mobile team, and then working with Watchmen to bring SAML/MFA to the AnyConnect VPN

### Lacked
**Jon** : lacked the tools necessary to effectively test one of carlos' stories. - but i am in the process of getting them downloaded (waiting on kraig)

**Katie**: Health and wellness was lacking for me this week 🤧

### PTO
**Carlos** : I'll need a day off next week

**Katie**: Not PTO, but I'll be doing dev onboarding for 1.5 days during our next sprint

---

## Feb 2 - Feb 16, 2024

### Liked
**Katie**
- Dan kicked some serious LDAP butt this week 🥊 just want to shout him out for the resilience he demonstrated digging into all the complexities with the new image locally and in CI
- Shout out to Ashley for all her help covering while Courtney was out and to Courtney for preparing everyone for her absence so thoroughly. A+ teamwork all around
- Having full-time ninja support has been great - shout out to Jon + Brandon for being generally awesome and helpful
- Very excited to have Carlos guest-starring on the team. I think this will be helpful for us to continue to focus on security improvements while he stays in the SCIM swim lane
- getting a new teammate 3/4!!!

**Jillian**
- Great job for getting a couple of stories over! (last sprint)
- Brandon and Jon joining standups is great

**Dan**
- The conversations with Carlos were really helpful with understanding our potential issues and next steps regarding the SCIM API work
- Shout out to Katie for handling the inter-team communcation. It's been helpful for my learning about what's coming up and things I need to learn

**Brandon**
- Good first week being in stand-ups. Being a little more aware of what the team is working on will help us with testing.

**Jon**
- Excited to start testing shield work. +1 to what brandon mentioned
### Learned
**Dan**
- Continued to learn a lot about NitroID and have a better understanding of our upcoming work
- Docker and OpenLDAP keep adding wrinkles to my brain and the occasional headache

**Katie**
- Just how intricately weaved the user model is throughout nitro-web

### Lacked
**Jillian**
- what are the biggest blockers keeping us from shipping this Sprint? (outside of needing a 3rd developer)
- this quarter's work is a lot heavier/complex.
- working with nitro-id and nitro-web
- influx in outside team communication !!
- SCIM related: Katie initially wrote something simple, then Carlos came in and redid it. Team was under the impression we had everything we needed for SCIM (dan's story to be the last thing), but has now increased in scope. Realistically, Carlos should have finished it 100% not us pick it up and try and understand where everything was left. Again, handoff could have been handled a lot better.
- XMEN- new feature of installation crews; VPs and some others users can create a new user called Crew Chief. limited set of permissions. they are not getting created with a password. expected to go through forgot passphrase flow, but isn't fully working yet. (pulled us into a path where Katie had to put down security integration. ) This new user flow was a surprise to us and shifted our priorities and had to pick up some more complicated work than what we had planned for in our OKRs.

### PTO
FULL TEAM FOR 2 weeks!

---

## January 22 - Feb 2, 2024

### Liked
**Jillian**
- made it through some work this week! Finally got to push through some blockers so I appreciate everyone's hard work
- Katie and Courtney for pairing on the upcoming work
- Lots of "good" meetings for Dan and Katie. Glad we were able to energize through those because I know it can be a lot
- Courtney for being on top of communication with her PTO coming up and having Ashley fill in for her

**Katie**
- Meetings with other teams went smoothly. I am excited for the integrations we have coming down the pipeline. Palo Alto VPN is especially exciting
- Collaborating with Courtney always goes well. We were able to identify some areas in the flow charts that could be even more clear, and will work on improving them when she returns from her time away.
- Shout out to Dan for being really tuned in to the LDAP/SCIM work. He's gained a lot of knowledge in a short amount of time. This will be a huge benefit to the team in the long term.

**Dan**
- SHD-483, the SCIM API story, is in Review. I learned a lot which will help with future stories going forward.
- While not quite finished, I made progress on the development Open LDAP update. I'm excited about this because it sets the foundation for our future LDAP/Password Policy stories.
- I appreciated being a part of all the meeting with other teams. While I wasn't always able to chime in, it did give me a good perspective of all the upcoming integrations and allowed me to expand my knowledge.

### Learned
**Katie**
- We have a much better idea of what is needed from the mobile team after meeting with them.

**Dan**
- Learned a lot about our SCIM API, LDAP, and Docker

### Lacked
**Jillian**
- more so for the previous Sprint, but so many blockers and we just couldn't get ourselves out of it with the test failures and figuring out what that route cause was

**Katie**
- The communication around the mobile team's issues felt like it was making a mountain out of a mole hill. I was extremely alarmed to hear they were having issues with sign in / sign out, only to learn that the issues was actually the API integration bug the team was already looking into.\
- Spoke to Jillian about this already, but reiterating here for transparency: I think it would be helpful to have a third teammate, considering all the support requests for integrations we have coming in. It would introduce additional drag initially, but I think it will utimately make distribution of support requests and feature developemnt more manageable and evenly distributed. Not to mentione extra time in between on-call shifts :)

**Dan**
- Not really work related but I wish my cough would go away faster.
- It would have been nice to get the Password Policy work unblocked and moving forward.
- I second Katie's point, with all the work coming in it sure feels like we have enough work coming along that we could use help

### PTO

---