In Pt. 1 of our two-part series on Agile Learning, we discussed the value of this nimble approach to classroom instruction. In this installment, we get into the nuts and bolts of actually using it in your classroom, from preparation to implementation, with a focus on practical experience, continuous testing, and group study using the Scrum methodology.
If you missed Part One of this series, you can read The Agile Classroom—What Is It? here.
As you prepare your classroom for an Agile Learning framework, there are a few concepts you’ll want to keep in mind. First, think Lean. Lean is the principle that gave rise to Agile philosophy. It’s a lot like the principle of simplicity in science. Our goal is to cut away any of the extraneous fat (hence the word lean). In practical terms, this means eliminating those variables or processes that distract from value production.
Lean thinking originated in the Japanese auto industry in the 1950′s. It was adapted in software development, which gave rise to Lean principles and Agile philosophy. Eric Reis is frequently recognized as the originator of Lean principles, particularly through his oft-cited book, The Lean Startup.
Putting aside this background, the basic idea is that you learn, measure, and build; or build, measure, and learn. This simple cycle drives value-based product development. Throughout the process, you are continuously verifying what you’ve already learned. Nothing is left to assumption.
...thinking Lean means placing less emphasis on lesson planning and more on the actual learning process.”
Now, let’s return to your classroom preparation. At its heart, thinking Lean means placing less emphasis on lesson planning and more on the actual learning process.
Sounds simple, right? It really is. At least, it’s simpler than traditional methods of instruction and evaluation.
But, how is Lean thinking done in the classroom?
One of the features that makes Agile Learning so valuable is the set of practical tools it provides teachers and students not just for collaborating across the classroom, but for breaking out into yet more nimble and dynamic study groups. This is where Scrum comes into play.
Scrum is an analogy drawn from Rugby. Like Agile, Scrum originated in the field of software development. And, like Agile, it has shown itself to be extremely effective in other contexts as well. This is why the business world has adopted it. The oil, automotive, journalism, and gaming industries—among many others—use Scrum strategies with regularity.
Scrum’s Rugby-inspired name is fitting. In a rugby scrum, the team huddles together and uses its combined strength to gain possession of the ball. On a symbolic level, this strategy signifies that the work of succeeding at the game takes the pooled strengths, roles, and talents of collaborating individuals in order to achieve some specified goal. This idea has proven effective when applied to project development. And the Agile Learning philosophy gives us insight into how Scrum might help in our approach to studying.
Scrum is an extension of Lean principles and Agile philosophy—a framework for applying these philosophical principles, one that allows for the type of flexibility required to maximize learning. Scrum does not adhere to a step-by-step approach. If it did, it would not permit the dynamic needs called for by different contexts, subjects, and students.
Instead, Scrum is a way of approaching development in an Agile classroom.
Studying is in many ways a project. There are developmental and managerial aspects to studying. Like all projects with their varied characteristics, studying too has its varied characteristics: what needs to be learned; whose assessment needs satisfying; and what skills need to be applied.
A basic outline of Scrum is to plan, track, and collaborate.
A Scrum Team is composed of three basic positions—the developers, the product owner, and the Scrum master.
The developers are those who do the work of putting together a plan and building the project in question—think of students primarily as the developers. It is the students’ shared responsibility to begin a project with a plan; track the progress of that plan; and work together, using their varying strengths, to ensure the success of the whole team.
The product owner is the one who represents key stakeholders. This person is at once the initiator of the project, and simultaneously represents the general desires and expectations of key stakeholders. Stakeholders are those who have an investment in the outcome and will therefore set the requirements for the product. Consider the teacher the product owner. The teacher oversees the product, while keeping the desires of administrators, principals, parents, department heads, and the broader community in mind. Certain results are necessary to bring about the final product.
The Scrum master is the servant-leader—the individual who motivates, educates on Agile philosophy, helps keep the developers on track, aids with assessment, and oversees reviews. In the broader classroom setting, the Scrum master may be a teacher, but in a study group, a student-developer may assume this leadership role.
The move toward Lean Classrooms, Agile Learning and Scrum Studying would represent a long overdue shift in educational values, prioritizing human interaction, dynamic change, and meaningful learning experiences over planning, procedure, technology, and tools. While it is true that students can benefit from thoughtful planning, helpful procedures, and emergent technologies, these should be secondary in the process of learning. The focus must be on actual learning experience and less on control, entertainment, and presentation.
Lean classrooms and Agile Learning have the potential to transform the classroom. These strategies are fluid, adaptive, and energizing. You, the teacher, will find that your prep time is less about evaluation and more about growth. And, most importantly, you’ll see evidence right before your eyes that your students are learning.