Agile Teams are Self-Organising Teams
Peha’s (2011) version of the 12 principles of the agile manifesto reinterprets the last two as follows:
- The best ideas and initiatives emerge from self-organizing teams
- At regular intervals, teams reflect on how to become more effective, then tune and adjust their behavior accordingly
We will explore this idea using a combination of Boris Gloger’s Ball Point game (Gloger, 2008) and Mike Rother’s Kata in the Classroom (Rother, 2015). Kata is a term from martial arts. The Improvement Kata is a repeating routine for continuous improvement.
The following diagram of the improvement kata process is adapted from material on the katatogrow.com website.
The goal of the ball point game is for each team to get as many balls as possible to pass through the hands of every team member in 2 minutes. The game involves both estimation and self-organisation.
- You have four rounds to iterate quickly and improve by trying different strategies.
- You always have 2 minutes in between the iterations to update the scorecard and re-strategise.
The four basic requirements of the game are that:
- As each ball is passed between team members, it must have air time
- Every team member must touch each ball for it to count
- No ball to your direct neighbour on either side, you must pass to your front
- Every ball must end where it started. For each ball that does, the team scores 1 point (make sure you count your points)
Scrum is an Agile Process
Scrum is a lightweight process framework for agile development. It is an iterative process that consists of a series of sprints that each deliver something useful. It enables teams to self-organize and collaborate, and accepts that the problem cannot be fully understood or defined up front.
In Scrum, the product backlog (of user stories) is broken down into a series of sprints. In each sprint, a priority list of stories (the sprint backlog) is chosen for completion. The sprint lasts for a certain period of time (e.g. 2 weeks, 30 days etc.). There are daily stand up meetings during the sprint, and at the end of each sprint a working increment of the software is delivered. In other words, it is only a successful sprint if it delivers something useful.
CC image from: https://commons.wikimedia.org/wiki/File:Scrum_process.svg
Agile Leadership Styles
Agile leadership is situational, adaptive, empowering and inspirational. The most important leadership theory applied to agile is that of servant leadership (Highsmith, 2009).
“For the Agile Leader, servanthood is the strategy. Situational actions are the tactic” (Filho, 2011).
The key characteristics of the servant leader include awareness, listening, persuasion, empathy, healing, and coaching. Situational leadership means that the servant leader may act as a democratic leader, a laissez-faire leader, or an autocratic leader in different situations (Koganti, 2014).
Servant Leadership
The originator of the servant leadership concept (though inspired by a Herman Hesse story) was Robert Greenleaf. “The servant leader is servant first... It begins with the natural feeling that one wants to serve, to serve first. Then conscious choice brings one to aspire to lead.” (Greenleaf, 1970). A longer extract from this work, which was this week's flipped preparation activity, is in this week's media
Teachers as Servant Leaders
Servant leadership has been applied by a number of authors to teaching. “The teacher as servant leader functions as a trailblazer for those served by removing obstacles that stand in their path. Part of unleashing another’s talents is helping individuals discover latent, unformed interests. Art, music, and science teachers are prime examples of educators whose genius lies in leading students to discover unarticulated interests.” (Bowman, 2005).
Ten Characteristics of a Servant Leader
- Listening
- Empathy
- Healing
- Awareness
- Persuasion
- Conceptualization
- Foresight
- Stewardship
- Commitment to Growth of People
- Building Community
These characteristics, that come from Northouse (2013), are outlined in a blog post by Penn State (2013).
You may find this Servant Leadership in Teachers tinyurl.com/TMLServantTeacher blogpost a helpful source to create a story card in the Trello board's learning backlog.
References
- Bowman, R. F. (2005). Teacher as Servant Leader. Clearing House: A Journal of Educational Strategies, Issues and Ideas, 78(6), 257.
- Filho, H. (2011). Achieving Agile Leadership: Proposing the Agile Leadership Manifesto. Retrieved from
https://www.scrumalliance.org/community/articles/2011/january/achieving-agile-leadership - Gloger, B. (2008). Ball Point Game: A game to feel what Scrum is. Retrieved from https://kanemar.files.wordpress.com/2008/03/theballpointgame.pdf
- Greenleaf, R. K. (1970). The Servant as Leader, The Robert K. Greenleaf Center, Indianapolis, IN.
- Highsmith, J. (2009). Agile Project Management: Creating Innovative Products. Upper Saddle River, NJ: Addison Wesley.
- Koganti, S. (2014). A Brief History of the Servant Leader. Retrieved from https://www.scrumalliance.org/community/articles/2...
- Northouse, P. G. (2013). Leadership: Theory and Practice (6th ed.). Thousand Oaks, CA: Sage Publications.
- Peha, S. (2011). Agile Schools: How Technology Saves Education (Just Not the Way We Thought it Would). InfoQ. Retrieved from http://www.infoq.com/articles/agile-schools-educat...
- Penn State. (2013, June). Servant Leadership in Teachers. Retrieved from https://sites.psu.edu/leadership/2013/06/23/servant-leadership-in-teachers/
- Rother. M. (2015). Kata in the Classroom: A simple exercise to help you teach scientific thinking. Retrieved from http://www.slideshare.net/mike734/kata-in-the-classroom-overview-47711515
Comments
Post a Comment