No longer between library jobs. Big Yay! Started a new part-time library job last week. But continuing the discussion of Agile application to HR issues. (Don’t fret, we’ll bring the Agile discussion back to librarianship soon enough. In the meantime, taking this HR detour might eventually be instructive). Today, we are going to take a brief look at the history of Agile methodologies. Later in the week we will look at some considerations when converting or transforming existing processes to Agile ones.
Agile History
It is easy to trace the history of Agile to the Agile Manifesto of 2001 and the twelve principles that followed in its wake. Easy but far from sufficient. We need to look at a few of the antecedents to that 2001 gathering to know what is really going on.
Lloyd Wilkinson, in Agile Development: A Brief History, traces the roots of agile project management thinking to Toyota process in the 1950’s, more specifically, kaizen, or continual improvement in automotive manufacturing processes. In case you haven’t already clicked on the link, kaizen is a Japanese word that is translated as “continuous improvement.” In lean, or just in time manufacturing systems, the process itself must “continuously change in order to deliver value to the customer.” Before we take a deep dive, it is necessary to say that one might make an argument that HR systems bound by rigid rules and regulations are not capable of continuous change. I would argue (1) that the multiplicity of rules and regulations, all overlapping, is precisely what opens the door to flexibility and dynamism and (2) what manufacturing process was more rigid that automotive assembly line production, and yet, Toyota’s introduction of Kaizen practices made it a world leader in the automotive industry. But back to the subject…
Kaizen has a few foci that are particularly relevant to HR processes. First is the Kaizen 5S concept: sort, or removing anything from the space not needed for daily operations; straighten, or placing the essential things in the right place for optimum operations; sweep, or removing anything that is clutter and repairing anything broken; standardize, or codifying best practices; and sustain, or establishing new, more efficient standards and resisting the tendency to return to old ways of doing things.
Second is the concept of employee involvement supported by employee trust. Specifically, this concept has as its antecedent, the work of Elton Mayo and the Hawthorne Effect (please click and read!). Very briefly, Mayo concluded that
- The aptitudes of individuals are imperfect predictors of job performance.
- Informal organization affects productivity. The researchers discovered a group life among the workers.
- Informal organization affects productivity. The researchers discovered a group life among the workers.
- Work-group norms affect productivity.
- The workplace is a social system.
A moment here on James Martin and Rapid Application Development (RAD). James Martin, nominated for the Pulitzer Prize for his 1977 book, The Wired Society: A Challenge for Tomorrow, introduced in 1991 an approach to RAD that involved iterative development and the construction of intermediate prototypes. These two elements would play a critical part in Agile project management thinking in subsequent years.
For extra reading, this article also looks at the history of Agile thinking: The roots of Agile project management.
Later in the week we will look at some of the challenges and possible pitfalls of adopting Agile thinking to existing processes. And to raise eyebrows, we will call the next post: “The Road Less Taken, or, People are software in any production process.”
In the meanwhile, a bit of Sarah Vaughan for the Labor Day Weekend: