I&A Series – “Being assigned features after planning before the PI is complete”
Marshall Guillory
Chief Transformation Officer | Enterprise Agility Coach | Change Orchestrator
I am starting a new series of posts where I will answer some actual problems/ideas presented in an I&A problem solving workshop as part of open space facilitation. This is the first of a few dozen that I plan on covering. If you have any comments, please, let's learn together.
Problem/Idea #1:
"being assigned features after planning before the Program Increment (PI/PIP) is complete"
A SAFe Answer
From a SAFe (and Scrum/Agile/Kanban) perspective, features (or stories) should never be assigned to a team. This is a common anti-pattern/fragile action that occurs during the early stages of cultural change where people are learning to let go of their theory X selves and dismantle the old belief system that people are dumb oxen that must be led by a bridle...
Please, read the rest of this article and visit my blog at blogagility.com.
Learn more at blogagility.com.
#RealWork #inspect&adapt
#SAFe #Agile #Scrum #Lean
Sr. Test Engineer at AstraZeneca
7 年:) Japanese companies encourage power-nap ~cof cof