In this part, I’ll discuss why agile is a culture change and ways to consider a system change to agile.
Agile looks something like this image.
The responsible person (often called a product owner) collects ideas and creates a ranked backlog for a cross-functional team. The team works on the backlog, releasing small chunks of value. At some point, the team demos to the product owner, retrospects and gets an updated backlog.
The system depends on these ideas:
- The team finishes small chunks of valuable work so the team and the product owner can get feedback about the story size and work to date. This requires the team finish their work. (You know, the discussions about done.)
- The team retrospects often enough to understand and fine-tune the team’s process.
- The team, including the product owner, retrospect enough to understand if the stories are small enough for the team to finish stories, and to change what the team works on when. Retrospectives include the product and the process.
This is a cultural change in these dimensions:
- From a culture of commitments through documents to a culture of commitments through working product
- From a culture of individual work (resource efficiency) to a culture of teamwork (flow efficiency)
- From a culture of management control (of the team) to team control of itself (self-management)
Culture change does not occur overnight. Change is hard work.
If you are one of the people nurturing your agile change, I bet you feel stuck in the middle between other managers, the manager(s) and the team(s). I invite you to join us at the Influential Agile Leader (Boston Apr 6-7, and London May 4-5) this year.