Marketplace Sprint 8
Focus Areas
Push to Prod
Push will be June 16th. Next sprint push to prod will include:
- The beginning of the SOW tools which are access controlled. (Need posting of the attachments) - Done!
- SSR for Scrud component. - Done!
- More polish - fixing bugs - Done!
- Alpha chatbot??
Foundations for Management Tools
Finalize endpoints and first UIs for creating SOW and enabling ability to upload and view reports.
Front End Test cases in CI/CD
Have front end test cases in CI/CD for openteams-nuxt
Support Chatbot Prototype
Test routing in staging. Push to production if infrastructure is set up and testing goes well
Polish Marketplace Pages
Push refinements
SOW Progress reports
Need back end and front end to support progress reports.
Testing
Continue to close gaps in testing, and create materials to train the team. Ensure REST APIs are tested as well.
Adopt SSR Form Gen
A change needs to be made to make caching configurable. This should be completed this sprint.
Documentation updates
We need more and more up-to-date documentation in our projects.
Schedule Changes
Jen is out on the 11th and in the afternoon on the 16th
Retrospective
The goal is to provide a summary of things that went well, didn't go well, and things to improve upon.
What went well
- Pushed to Prod! with scope and in sprint timeframe - Maryam and Jacob
- Architecture meetings teach a lot! - Maryam
- David is teaching on the environment - Maryam
- Learned a lot about caching and RBAC - Kevin
- Pushed SOW tools to staging - Kevin and Chris
- Status report was able to go quickly - Chris
- Was able to adjust to API changes quickly - Favour
- Was able to think longer term for chatbot for scaling - Favour
- Able to attend product meeting helps with seeing where we are heading, what are deadlines, etc. - Igor
- Documented steps about push to prod and it went smoothly - David
What didn't go well
- Challenges with SSR on staging - Maryam
- Bugs on some concepts that people didn't understand - Kevin and Chris and David
- Had small things when pushed to Prod. Would have more time to polish if push to staging/prod is earlier
- Production deploy required significant late fix and took more resources than it should.
What to try next sprint
- Capture things earlier in the sprint rather on later in the sprint. - Maryam
- New Methods for testing - Chris
- Next sprint push to staging to Monday and prod Weds if possible - Jacob and Igor
- Document how we define rest APIs using Swagger or OpenAPI (https://gitlab.com/openteams/openteams-backend/-/tree/sow-http-schema/openteams/apps/sow/http-schema) - David