| |
|---|
8/8/2023: Blue Dot Sprint 15 Miro board | 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 Having a better understanding from the Product level what the expectations are for the rest of the project
"Shaking the tree" helps :) AKA reaching out in Slack and pushing for a little extra help FE sync has been helpful! Devs got on a call together to swarm big issues as they arise Open huddles in Slack for folks to join and collaborate if needed
More PR's in general vs before - these can take more time to review/looks like a lot more in the board Better communication in the PR about if something is fully ready for review vs needing to work on a few changes before it's ready If you need to prioritize one over another (i.e this PR affects other blocked tickets), reach out to managers - FE tickets reach out to Ashley & BE tickets reach out to Surya (now Matt)
Last handful of FE tickets Looking forward to getting it done, but ECM can't do anything with this until the PR's have been approved, merged & tested in QA Once this request is done (222 - which was out there for a long time), we should be able to push through more Suggest to get on a call with a few folks to work through it together if possible - hopefully that'll be quicker and allow for Q&A
Tickets from Refinement today should be good to go, and PM is continuing to reorder the Backlog & change priorities as needed There will be some situations where tickets are dependent on each other, so we may not technically be able to take the next one if we know there could be blockers Also priorities within the ticket description/ac - example using code within the backend as opposed to rewriting things for the front end if we can reuse what already exists - make sure to check with PM if you notice something like this If we need to, we can add it to the "fe reqs vs qa" & "fast follow-up" docs
|
7/11/2023: Combined Sprint 12& 13 Retro | Notes: |
6/26/2023: Q3 Quarterly Planning Week | |
6/13/2023: Blue Dot Sprint 11 | Notes: |
5/30/2023: Blue Dot Sprint 10
| Notes: |
5/16/2023: Blue Dot Sprint 9
| NOTES: If new details emerge or AC of a ticket change, please make a note in the testing instructions section to call out the change specifically to the QA team. Make sure to update AC and description in the ticket to reflect the change. SonarCloud build failures are a blocker to Zaengle devs – no insight into what the build failures are specifically related to. Peer Reviews still taking a long time If your ticket is sitting in peer review, reach out to default reviewers directly. Doing this in the supernurse-frontend channel will allow dev managers to see the blocker too and we can help push along Automation alerting channel to new PRs would be helpful.
Don’t be afraid to label a ticket as blocked. It only helps us to have that information. Sabi completed first automated test. WOOT! Async standups are awesome. Epic ownership is going well.
|
5/2/2023: Blue Dot Sprint 8
| Notes: |
4/18/2023: Blue Dot Sprint 7
| Notes: |
4/4/2023: Blue Dot 2023 Sprint 6
| Notes: Every other Tuesday with a bunch of meetings is a lot merp MB confirmed QA has been much better lately Follow-up on automated deployments below @Surya Bhatt (Deactivated) @Christian Roberts Can y’all help with this? (notes below)
|
Blue Dot Sprint 5_2023 | Welcome to the team Janaky Notes: Strong focus on communication - relaying updates & issues across the team in Slack Adhoc walkthrough for Devs to ask questions on design review Yay Dev team picking up tickets and working through tickets! Most productive & smooth Sprint yet!
|
Sprint 41 (4_2023) | Notes: What went well: We got QA environment setup PR reviews were faster than prior sprint Tickets moving along Pairing, knowledge sharing, getting up to speed (thank you, Tom Davies!)
To improve: Remember to set yourself as the developer on tickets that are assigned to you. This provides data on what work the teams accomplished in a sprint. Not all issues have testing instructions when they go to test Amount of revision cycles for PRs PR Reviewers list (need more discussion?)
|
Sprint 40 (3_2023) | Notes: Shoutouts: to Tom for the pairing sessions and helping team learn building craft components; Jay was very collaborative on the pairing session with Thom Thanks for being willing to try out a new sprint process and give feedback about what's not working! Team making great progress on learning Craft Product team got few things ready for the dev team to start building components PR approvals should be thorough reviews, not just rubber stamps. Please do not add an approval if you have not thoughtfully completed it. PR Review Responsibility: When 16 people are auto-tagged for review, that adds a lot of noise to inboxes and makes it easy to think that someone else will cover it. And not all PRs should be reviewed by everybody from the list. I think we could reduce the amount of time PRs spend waiting on approval if we designated certain people to review certain work. Add Work-in-progress limits to the workflow update written documentation of Craft standards and improve on boarding of people into Craft Time between sprints: Adding a longer "cool down" period between sprints would allow tickets to be reviewed in greater detail, then shaped, and scheduled, and result in less tickets being taken off the board mid-sprint because they aren't ready to work, or require other work prior to starting. If no testing by QA can be performed on your ticket, please indicate that in the Testing Instructions.
|
Sprint 39 | Notes: Quite a few tickets in the Done column. Nice job! Zaengle team was onboarded, doing a great job of being proactive and getting this done. Good start on Craft side buildout QA team got their locals set up Suggestion: Have an ‘.editorconfig’ in the repo to help with standardizing our code/avoiding pingpong changes due to editor settings. Tasks don't always have their pre-requisites / dependencies documented (e.g design). Makes it hard to see if a task is really ready for work. We need to have approved design ready before starting a sprint. As someone joining the project, it is somewhat hard to tell who has what responsibilities, and also what skills / specialities they have. Ensure the dev team has a cohesive vision for the approach to the build (i.e. project plan) and understanding team responsibilities. Tooling for code consistency / linting seems light - would be helpful to have that + agreed standards Meetings - For a lite sprint, there were a lot of meetings that feel like they could be asynchronous written updates.
|
|
Sprint 38 | Notes: It’d be great of Chris or someone with experience on the Vue components could walk us (Razar) through how we can help QA components Further clarity on tasks that are being done on our local testing regarding integrations Lots of work done this sprint!!! Chris’s demo aligned everyone on app architecture. Good movement on refinement.
|
Sprint 37 | Notes: Shoutouts: Isaac, for front end setup and auto reload. Chad, for integration/unit tests setup, and confluence doc. Chad, Jay & Thom, data layer work. Christian, helping Razar with frontend. Holiday break great team work. Lot of tickets got completed Learned more about RabbitMQ and AspectJ Many unknows still for Super Nurse Clearer design expectations in tickets, esp. foundational Coding Standards documentation More unit tests
|
Sprint 36 | Notes: Communities Meetup Good progress on Super Nurse tickets New Team Name Team work between both teams. Shoutouts: Diep, fixing SuperNurse backend API GTM Datalayer work Need UI mockups Refinement still needs to work out some issues Complete all the tickets in the sprint.
|
