In agile Scrum parlance, the term 'Chicken' refers to those who are involved (but not committed) in the project and stand to benefit from it. Examples: Managers, Leaders, Coaches, Sponsors etc.
In a typical Scrum team, the role of Chicken is somewhat marginalized, at times to the extent of being derogatory. However as organizations Scale agility from doing individual pilot projects to enterprise wide Agile adoption, the role of Chickens assumes significant importance. A thoughtful organizational change management by the Chickens, can be the differentiating factor between success and failure.
Introducing '
A chickens manifesto for scaling agility':
-----------------------------------------------------------------------------------------------------------------------
"As responsible agile practitioners, we are optimizing the value delivered through agile software development by adopting innovative practices. In addition to the manifesto for agile software development, we have come to value:
attitude over skill
adaptability over predictability
effectiveness over efficiency
optimizing the whole over improvement in parts
That is, while there is value in the items on the right, we value the items on the left more."
-----------------------------------------------------------------------------------------------------------------------
I picked these values based on my own experience of scaling agility from a small team to be an enterprise wide phenomenon. Keeping your agile adoption journey in context, do you identify with the above mentioned? Do you have any other useful values to add?
Please leave a comment.
