Mastodawn

I'm always concerned about handoffs, because where there is a handoff there is a queue, and where the queue reader is busy it results in a wait (and, of course, every item in the queue waits on the one before it).

So with Platform and Complicated Subsystem teams, how are you handling Stream Aligned teams' dependencies? How are you avoiding queuing and waiting for those dependent teams?

Curious if you are loaning out your people to teams to avoid handoffs, bringing their people into your teams' code to expedite, leaving the code fully open to external changes (with review and refactoring to follow), or just dealing with queues and waits.

Show thread

Matthew Skelton Feb 20

@tottinge there is no waiting because the platforms and CS teams provide capabilities as a service, like a vending machine.

This is very different from ticket-based workflows like Jira. 🎫⛔

With the vending machine model, you either consume existing capability, or you build it yourself, or even reschedule work to come later.

Build based on what's available - like LEGO bricks 🧩 - and never couple your work to that of another team.

Show thread

Dawn Ahukanna Feb 22

@tottinge
Against management resistance, created UI squad with dedicated & nominated focal for each part of UI “micro service” for static code & runtime delivery/troubleshooting/operations
1. UX Designer
2. Front-End (browser) dev
3. Backend-For-FrontEnd(BFF) dev
4. Integration API dev
Means there’s shared agile practices; working as multidisciplinary unit; have holistic, knowledgeable understanding of system they are making; manage dependencies; provide built-in backup cover for vacation, etc.