How do you think the Citizen Developer movement can benefit from a Manifesto similar to the 2001 Agile Manifesto?

 

The Agile Manifesto has been around since 2001 and has benefitted millions of multi-disciplinary professionals across the globe. We believe a Manifesto would be of great use for the Citizen Developer community!

Background

The Agile Manifesto was published in 2001 with the objective to provide an alternative to existing software development processes. It identifies 4 values and 12 principles. Ever since its publication, Agile has expanded to become more of a mind-set that now applies across a broad range of activities and work methods. Over the coming weeks we will release a series of articles, discussions and community polls with the intention to explore benefits with having a Manifesto (and associated principles, values and beliefs) for Citizen Developer.

The original 12 Principles of the Agile Manifesto reads:

1.       Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2.       Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3.       Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4.       Business people and developers must work together daily throughout the project.

5.       Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6.       The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

7.       Working software is the primary measure of progress.

8.       Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9.       Continuous attention to technical excellence and good design enhances agility.

10.   Simplicity--the art of maximizing the amount of work not done--is essential.

11.   The best architectures, requirements, and designs emerge from self-organizing teams.

12.   At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

How to get involved:

We would love to get your views and hear from you as we go through the process. To get you started we have published a poll and a discussion thread.

 Poll: Are the principles in the 2001 Agile Manifesto still relevant in 2020? 

Discussion: How can the Citizen Developer movement benefit from a Manifesto similar to the 2001 Agile Manifesto? 

Looking forward to hearing from you!

Martin Kalliomaki