Sprints are supposed to be forcing functions to narrow scope, produce something useful for a customer, and make improvements in how we work together. They are NOT for trying to get developers to deliver as many story points as possible. Our industry has this so, so wrong.
3 subversive contentions about frameworks in 1 tweet:
1. It's helpful to see frameworks as mere exemplars of patterns
2. How they combine is often more interesting than the patterns themselves
3. How they're introduced matters way more than the framework itself #agendashift
KFTI came out 5 years ago! To be honest I haven’t checked the exact publication date but Facebook reminded me: https://t.co/D4YyFq7otr
#kanban#lean#agile
As usual Neil gets what I'm trying to say. A top-down imposed Agile transformation already isn't Agile. Trying to "scale Agile" by homogenizing your teams already isn't Agile. Many transformations are tantamount to a bait and switch.
#agile#scrum
@Right2LeftGuide 2/5. In Lean-Agile we celebrate #Lean & #Agile both separately and together. To Lean's "strategic pursuit of flow" (after Modig & Åhlström), we bring from Agile a safe default assumption, that in knowledge work, most failures of flow are rooted in failures of collaboration