It's so weird when you are listening to people online in a seminar or podcast, and they're singing your song, and then they start to use your own figures of speech and metaphors, and even stories.
I mean, it's flattering to be sure, but it's like looking into a funhouse mirror: it's you, but it's not you.
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.
Article begins "you shouldn't assign every ticket to a developer at sprint planning"
I'm thinking that this is going to be good - people pick up work as they become free, work in teams, and self-organize to complete work, right?
No: They argue that every developer should assign themselves a full load of tickets at sprint planning time.
Same problem: no room for collaboration, only individual action. Same queues, waits, dependencies. Still scatter-gather. Sigh.
So why? "So they FEEL more empowered."
Well, that's great for changing the optics without making a difference.
Lewin's equation is that behaviour is a function of the person and their environment. A common well-intentioned error is to focus only on the individual or only on their environment/system.
Both shape behaviour. Both have to. This suggests that you needn't be exactly the same (in behavior) at home and at work.
Be at work at work. Be at home at home.
Be you in both contexts, but be you in that context, not context-free you.
When is the last time you saw people actually planning in a planning meeting? All we see is the un-teaming of team members.
https://agileotter.blogspot.com/2026/02/do-you-even-plan-bro.html
Adventures imply challenges. No challenge? No adventure.
You know I like continuous anything better than episodic anything when it comes to coding. I don't want quality and security scans to happen after I think I'm done, but while I'm coding (why make bad code now and fix it later?).
So I want to know how you do continuous security checking while coding. What IDEs and plugins are you using, and do you background-scan while coding? What git hooks help you stay on top of it?
