7/25/2023 - Notes in Miro
- Includes Sprint 14:
7/12/2023-7/25/2023
| Fist-to-five - unanimously 2: - Still have a lot to cover from the automation piece, requiring refactoring as code changes, testing, etc.
- Automation may not technically prevent us from launching, but it's struggling to get off the ground, and will really helpful once we have it - will push us through quicker
- Potential for missing bugs given fully manual testing
- Requesting requirement/UI updates part way through development as questions/concerns arise
- A lot of manual file changing as reqs change (i.e address format)
- BE changes cause FE changes
- What refactoring can/should wait?
- Doing this work takes longer now, but should save us time post-launch
- Only one more ticket that should require big changes/refactoring before MVP launch
- Refactoring now vs. later - NEED PM REVIEW FIRST:
- What's the LOE now vs. later
- Allows PM to decide on prioritization
- BE changes are happening to fix dependencies, so they're not really unavoidable right now
- Sean doesn't merge BE changes that would break FE until a FE ticket's created that fixes those issues
- Request: provide info on where changes are in PR (see GraphQL files)
- Bri & Sean pulled cards out of the initial launch
- Anytime we know BE refactoring work is required, pull in smaller groups (EM/PM, specific Devs, etc.) to determine next steps
- Sean pings FE channel when changes are required (keep doing that)
- Once amount of work is determined (ex: decent amount of work that will affect timing), bring up to PM
Next steps in alerting PM: - Determine BE & FE impact
- What is the LOE/scope increase
- Reach out to PM to discuss priority
PR's (top priority): - Need FE help - they take a really long time
- Christian is no longer a PR approver - who else can we add?
- "Rotation" meaning communication between default reviewers to ensure folks aren't duplicating effort on reviewing the same tickets unnecessarily
- Reduce size of PR's if possible
- FE/BE sync - call out PR & have separate call to walk through and hopefully review quicker
Distribution of work on PTO: - Chat with PM to cover work if needed
- Share info with other Devs in case questions come up
UX may not update Figma files if PM descopes: - We'll make sure Jira is update and is the source of truth - responsibility on PM to denote changes in testing instructions
Process standards still being worked on: FE Devs us QA instead of locally? - Quick FE changes directly to QA?
- No "garbage" data
- Allows for different viewpoints
- Technical Roadshow: go over similarities
- Zaengle doesn't have access to some apps
- If they can't, definitely need to need to point to QA
- Sounds like they should be able to without this - need to follow-up with Christian
Segment setup needed from ECM: - Henry, Lakshmi & Surya to talk to Jose about the
Staging environment: - Lack of data causing instability
- Maybe use Staging like a "test" for now until we go live, then ensure Staging has accurate/clean data
Fetch QA token: - No real emails sent out - impossible to fetch right now
- Setup local email? Mailtrap (Christian has more info - looking into setting up)
| - Alyssa: Share fist-to-five info with leadership & determine next steps
- Team: Make sure to alert PM so they can determine priority when
- BE/FE changes will impact each other
- Scope/LOE changes
- Devs: Determine how to handle PR priority
- EM’s/Devs/QA: Determine process for distribution of work when on PTO
- Zach & Isaac: Process standard documentation
- ECM: Segment setup (do we have a ticket # to follow?)
- Team: What are we doing about the Staging environment for now?
- Christian: Mailtrap setup?
|
6/26/2023: Q3 Quarterly Planning Week  Image Modified | Shared components - need improvements: - Be more vocal about recognizing shared component opportunities during refinement/design review
- When creating a component that may be shared, call it out for feedback to ensure flexibility
- Jasmine’s doc will call our pre-existing components
- Once Storybook is implemented, this should replace that
- More granular breakdown of design into more component-based views
- Look at components from library instead of using part of one and having to make others
- Call out in FE Slack channel to see if component has been worked on before starting a new one
- Communication before/during work has helped
As details emerge, update Jira to reflect necessary updates: - Testing instructions needed/changed? AC accurate? Impediment/blocker?
- Devs to ensure testing details are up-to-date
- Only PO should update AC
- Link tickets & add comments with detailed information
- More info is better
| - Blue dot to go back to Tuesday/Thursday in-person DSU
- Cross-team Retro once/month (start on 7/25)
|
