Manifesto for Agile Church Development

While not a software development, I appreciate the agile software development methodology which they use. I recently discovered the Manifesto for Agile Software Development, which is:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

I appreciate these principles and believe that they just need a slight reworking to be applicable to the church:

  • People and interactions over processes and tools
  • Effective discipleship over comprehensive programming
  • Leadership collaboration over denominational negotiation
  • Responding to change over following a plan

How do you respond? What would you add, change or delete?

Advertisements