Sprint 57 (SVS onboarding (easy onboarding instructions / tools (Further…
getting them ramped up could be more of a challenge
not everyone can run all the services
easy onboarding instructions / tools
Further improving onboarding :check:
How to run services without dependencies - improve documentation (highlight - calling it out)
Save Glue - simplify save-glue - make dependencies optional
Add 2 services that are missing from save glue
How we can work with SVS :check:
SVS worst case scenario
mitigate by pairing
is it worth it?
how does pairing looks like? At their HQ
tasking physically @ 1600 - switch with Nicole
Pairing mandatory the first sprint
outage in production
By not following norms
Making norms explicit
slow us down
internal check-in, maybe EOD?
hours Monads spend with SVS
how does pairing going to work on Fridays?
Check after 1 sprint on whether they're slowing us down or not
what would success criteria be like?
compare to our velocity
Need to be able to have a tech discussion to be able to estimate more accurately
Do we want to talk about tech solution (technical output) during grooming (high level, which services will be affected)?
5 stories with tech output vs 5 stories without tech output [chris and kevin] before next planning :check: