Sunday, March 2, 2008

Agile State of Mind

These days everyone seems to be blogging and writing up a storm about Agile methodology in software development. While that maybe, it is doubtful if any of them have ever thought of applying the Agile principles of supporting change, rapidly adapting and learning from it, leaving all communication doors open, being accountable and collaborating closely as a life philosophy to live by? Some may find it unnerving, but they shouldn’t? Agile in life is as applicable as in software development, since ‘Agile’ is not a discipline, but a life philosophy. Nothing but a set of principles and values, it is a broad approach and like all things in life, it means rapid adaptation to changes, learning, open communication, accountability, and close collaboration.

But, many people find responding to change requires a major mental shift that is difficult and takes time and environmental support. Society often penalizes people for being flexible or adaptable, as rigid traditionalists seem to think this translates to being uncertain, indecisive, uncommitted or even rebellious, as confirmed by the various blogs and comments reviling Agile. However, dip your toes in it and find that as a philosophy, Agile adapts itself pretty well to living life by it. After all, Agile philosophy emphasising a set of values, principles and practices can be applied outside of software... in business management, family and household, or... in agile classroom management.

For example, the easiest way to get a child to eat healthy is doing it one bite at a time, starting off with the best and tastiest bits first. This makes your goal of getting him to finish a healthy meal more manageable. That is to say, when faced with a life issue, as in Agile software development iteration by small iteration helps solve any problem, allows you to assess the situation and then proceed to the next step, and so on until you ultimately achieve your goal. However, always keep the big picture in mind when starting out on a goal achievement mission.

Basically, Agile methods are quite similar to 12-year olds, high on IQ, low on patience, with enough time on his hands to sit in front of the TV, frantically pushing every button of his Nintendo until he figures out how to do it, all without once bothering to touch the manual. It’s all about trying something else until you get the desired effect and then moving on to the next thing.

Using Agile methods in the classroom is easy. Simply start out by:
1. Carefully studying the syllabus.
2. Next, setting up one’s teaching goals.
3. Then, assigning a goal to be achieved within each sprint or iteration. Students have to be taught and they must understand what has been taught.
4. After completing a sprint or iteration, a test should be assigned to assess whether your goal has been achieved.
5. If, a majority of students do not pass the test, assess your teaching methods, selecting the successful ones, while junking those that fail to catch the students attention.
6. Simultaneously, the areas the students failed in should be evaluated and subjects put together, with the more interesting one’s first, trailed by the least interesting lessons.
7. Now, you start afresh with a new sprint or iteration.

Congratulations! At the end, you will find that your students have learnt and been able to retain, which means you have met your goal of teaching your class well enough to pass a difficult evaluation exam! And, you will find adapting Agile principles and values to life helps up your success rate!

No comments: