Increased confidence level from 2 to 3 - maybe has to do with the teams focusing on their own teams' work vs the project as a whole since there's not as much visibility
We only have 23 tickets in the backlog with 17 (excluding data migration/job credits potentially) not started yet - more of a direct vision to "the end"?
EM's to work with PM's to determine what work is left and how to best group Devs to work on that together
Trying to get things out quicker can cause us to overlook things, but some folks don't seem like this is a new problem right now
Change to FE duplication standard could be a possibility - moved from 3% to 90%
Team to focus more on the PR process to try and catch these earlier if possible
Difficult trade-off rush to get code out vs focusing stronger on quality
Bri, Janaky Raymond: Instead of waiting for approval before the team starts work, can we have folks pull tickets in from the Backlog in order and they can tag you to let you know they've done it and then ask if there's something else that takes higher priority?
Don't want people to not feel empowered/trusted to work on what needs to be done - try to find a balance between "asking permission vs forgiveness" (for lack of better terms)
Follow up with Isaac / ECM on getting FE's backends to point to QA
FE team had a lot of issues recently - couldn't get builds to build consistently, not sure what the original issue was before
Had to revert back to Java 17 for some - others it just started working on its own
Improvements to the clean command should be revisited after initial launch
Discuss splitting larger tickets during QP Refinements
Krypton Sprint 5_2023
Notes:
Our team is a safe space for all feedback - don’t hesitate to each out if issues arise. You can reach out to your DM/EM directly if you aren’t comfortable sending to the larger group.
We may be changing the process for Sprint 6 (more details to come)
Capacity Tracker will help with potential PR blockers
Krypton Sprint 4_2023
Krypton Sprint 3_2023
Notes:
New sprint process had some stumbles, some fine tuning may be necessary (will revert to a more traditional sprint process)
PR bottlenecks
FE needs gate to make sure it is “working” code that is merged in
Sprint 39
Notes:
Issues with frontend side communication on how things will be done. And overlapping work
To have FE and BE work be split to different tickets
Peer Review process seemed to get backed up a little bit
Vue composition API requirement wasn’t communicated before hand. Had a action item specified above regarding this.
Should consider dependencies when assigning tickets to other team
Kudos to Qiyi for all testing in the Sprint. Sean for reviewing every backend ticket. Surya is back.
Team work and team synergy seems to be increasing
Datalayer code successfully deployed to Production
Got amount of work done within the sprint.
TEAM SHUFFLE
Sprint 38
Notes:
Unit tests on code were good
PR have improved. No longer stuck for long in the column
Lots of tickets were completed
Sprint 37
Notes:
Shoutouts: Jeff! Jimmy! Great teamwork!
PR comments were helpful
Team members were helpful in answering questions
Product leadership working hard to flesh out backlog
