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:

1. Individuals and interactions over processes and tools

1. Working software over comprehensive documentation

1. Customer collaboration over contract negotiation

1. 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:

1. People and interactions over processes and tools

1. Effective discipleship over comprehensive programming

1. Leadership collaboration over denominational negotiation

1. Responding to change over following a plan

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