Agile Education

Is your school agile?  Education administrators may not have a comfortable answer.  Let’s think about their process.  Up to 16 or more years after development starts, educators turn out a product that is supposed to be functional.  Throughout that development period, the needs and demands for full functionality are changing — but education processes are oblivious. Its time that education became more agile.  If students are going to function at their best upon graduation, education should take some lessons from software development and move away from the archaic development processes of the past.

The Agile Manifesto Principles are:

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly