Agile (for teachers)

Nicholas H.Tollervey / @ntoll

1. The problem

Software development is...

  • Complicated
  • Collaborative
  • Costly

Demo: Stuff I do

Boils down to...

  • What's the problem..?
  • How long will it take..?
  • How much will it cost..?

2. Proposed solutions


Top down!

Change is constant

3. Agile


  • Customer satisfaction by rapid delivery of useful software
  • Welcome changing requirements, even late in development
  • Working software is delivered frequently (weeks rather than months)
  • Close, daily cooperation between business people and developers
  • Projects are built around motivated individuals, who should be trusted
  • Face-to-face conversation is the best form of communication (co-location)
  • Working software is the principal measure of progress
  • Sustainable development, able to maintain a constant pace
  • Continuous attention to technical excellence and good design
  • Simplicity—the art of maximizing the amount of work not done—is essential
  • Self-organizing teams
  • Regular adaptation to changing circumstances

blah blah blah

  • Sprints
  • Stand-ups
  • Visibility
  • Roles
  • Retrospectives






4. Agile in the Classroom?

Over to you...

  • Can you, as teachers, use agile?
  • Could kids do agile?