Retrospective
Where did we improve? 
- List anything that went well in this sprint including shout out to others that went out of their way to help (add your name after your comment)
- Frontend refactoring is going smoothly, we are still on track to meet scheduled release date despite small amount of hiccups and bugs (Ying, Ming (NIH/NCI) [C])
- As side effects, we fixed a few bugs without trying to do so! It proved refactoring is working fine and worth doing! (Ying, Ming (NIH/NCI) [C])
- We had our tickets assigned ahead of the planning meeting and were able to get a deeper look into them in advance of the sprint starting. (Mattu, Alec (NIH/NCI) [C])
- Awesome work, everyone! It's really encouraging to see the progress we've made together. I want to express my gratitude to each team member for their valuable contributions. Let's keep up the momentum and continue to build on our successes. (Sheth, Karan (NIH/NCI) [C] )
- I wanted to give a shoutout to Ying, Ming (NIH/NCI) [C] for their great work on the new monorepo structure. It's been a game-changer for the Bento Frontend team, making it much easier to write cleaner and clearer code. Thank you, Ying, Ming (NIH/NCI) [C]! (Sheth, Karan (NIH/NCI) [C] )
- Big thanks to the Frontend team for their hard work and dedication to the Bento Frontend Refactoring project. All efforts are paying off and we are seeing significant progress. (Sheth, Karan (NIH/NCI) [C])
- Lerna implementation and new project structure making easy to publish npm package and appropriate sequence or steps on refactoring process. (Rana, Ambar (NIH/NCI) [C] )
- I appreciate our team members always being available and willing to discuss challenging things such as bugs that pop up, in this sprint Stogsdill, Hannah (NIH/NCI) [C] and David, Sofia (NIH/NCI) [C] were particularly awesome. (Kuffel, Gina (NIH/NCI) [C] )
- The demos by the Bento team are top notch, very clear and thoughtful presentations. (Kuffel, Gina (NIH/NCI) [C] )
What areas still need improvement? 
- List anything that we could have done better in this sprint (add your name after your comment)
- Admin portal was vastly underestimated, caused some tickets overflowed into next sprint. (Ying, Ming (NIH/NCI) [C])
- Breaking user stories into smaller, more manageable tickets and accurately estimating them will help us better track progress and meet our project goals.(Sheth, Karan (NIH/NCI) [C])
- Making sure we follow-through with the entire release checklist so that things like release notes are actively maintained on GitHub (Kuffel, Gina (NIH/NCI) [C] ).
What you have learned? 
- List anything you learned about in this sprint (add your name after your comment)
- How to use "cross-env" NPM library to unify build scripts for Linux/Mac and Windows. (Ying, Ming (NIH/NCI) [C])
- How to build a component that can be easily integrated with an existing redux store and manage it's own states, etc (Mattu, Alec (NIH/NCI) [C])
- I've gained valuable knowledge about how Lerna can be used to effectively manage a monorepo, making it much easier to publish independent component packages.(Sheth, Karan (NIH/NCI) [C])
- Case based reasoning for configuration, store and state management. (Rana, Ambar (NIH/NCI) [C] )
- Combine use of usereducer and contextProvider (Rana, Ambar (NIH/NCI) [C] )
- Became an expert with the AWS CLI and loaded 88 genomic files into an ICDC non-production facing bucket and populated all of the data loading files for this study now named OSA03 (Kuffel, Gina (NIH/NCI) [C] ).
Actions
