@rh
Ok.
This doesn't apply to me.
We don't have crum, can't ban, or jirry or any of that.
10 replies (most recent on top)
The proposed pod model reportedly involves groups of 2–4 engineers working alongside agentic AI capabilities.
Similar organizational structures have been attempted in the past, with mixed results. Previous implementations created additional dependencies between teams, increased handoffs, and contributed to delivery delays.
There are also questions about how the new structure will affect existing Scrum Master and Kanban Lead roles. Build League and individual developer stack ranking are expected to continue under the proposed model.
@ch Oh but they are. You can break up the team into Pods
All pods are 2-4 people so my guess.. layoffs of extras
PODS are 2-4 Dev team members.
Goes with Kanban not Scrum.
Effective Dec 7 going to Kanban boards to monitor time dev takes to complete the points. Another monitoring system.
Scrum Masters will now be Delivery people for releases. SM work will now be dumped on the Product Lead aka Product Owner.
@OP
What the he-l is a POD?
All I know for sure is that it will be yet another excuse to downsize people. Every single HY strategy has that as the primary feature.
Who came up with this cluster “F” and thought it could work here ?
Just another mechanism for the can't do to control the can do so that they can feel some sense that they are managing it right.
Stupid, I have 2 teams, both 14+ don't think they can pod us, lol
More stupidity.