What is your view on how the Citizen Developer movement can benefit from a Manifesto (i.e. principles, values, beliefs) similar to the 2001 Agile Manifesto.
For example:
What does a Manifesto mean to you, and what should it contain?
How do you think it could help you?
How would you use it?
Should it be static or respond to change?
Cheers!
Martin Saving Changes...
Sort By:
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Not supportive of manifesto's, as they formulate beliefs and are used for marketing a belief system. Might create followers though and are sometimes helpful to instill a movement. On the hand they create conflicts, with other belief systems but also with reality.
Regarding CD, the underlying idea is to make it easy and simple to program computers, so that more, and less educated, and less payed people ('citizens') can do it. Is here for decades, all 2nd and 3rd tier programming languages are examples, or look at IFTTT, or parametrized packages, or just UX.
I am sold on the concept, now I am most interested in the training.
I want to learn about the tools and platforms are available and what professional project managers and Agilists can contribute to insure successful and timely delivery with a reasonable ROI. Saving Changes...
For me, a key benefit with having a Manifesto (and guiding principles) is that it will allow for a more tight knit community, including a common language and a name.
Another benefit in my view is that principles for Citizen Development will allow organisations and individuals to reach a common goal. Principles (as opposed to prescriptive rules) will also ensure that the path to that goal is not compromised.
What do you think? Are there any other benefits and risks that needs to be considered with a Manifesto? Are there any lessons learnt from Agile and its Manifesto that would be worth discussing? Saving Changes...
a couple of lessons from Agile & the original Manifesto are:
1. Ensure that values & principles aren't ignored in favor of blind adherence to frameworks and methods
2. Allow for evolution of the values & principles over time
...
1 reply by Scott Ambler
Jan 22, 2021 3:59 PM
Scott Ambler
...
Definitely agree about the need to be willing to evolve it. As you know, we originally wrote the DA Manifesto because the original Manifesto authors had effectively agreed to not evolve it. Fair enough, it's their work.
In DA we've chosen to move beyond both the concept of a Manifesto and beyond Frameworks/Methods. But that's just us. ;-)
Saving Changes...
Aws NabeelInformation Technology Multimedia Educational Technologist| Dhofar UniversitySalalah, Dhofar, Oman
Agree with Kiron. Thanks for the insightful answers Saving Changes...
Scott AmblerConsulting Methodologist| Ambysoft Inc.Toronto, Ontario, Canada
Scott AmblerConsulting Methodologist| Ambysoft Inc.Toronto, Ontario, Canada
Dec 10, 2020 8:11 AM
Replying to Kiron Bondale
...
Martin -
a couple of lessons from Agile & the original Manifesto are:
1. Ensure that values & principles aren't ignored in favor of blind adherence to frameworks and methods
2. Allow for evolution of the values & principles over time
Definitely agree about the need to be willing to evolve it. As you know, we originally wrote the DA Manifesto because the original Manifesto authors had effectively agreed to not evolve it. Fair enough, it's their work.
In DA we've chosen to move beyond both the concept of a Manifesto and beyond Frameworks/Methods. But that's just us. ;-) Saving Changes...
Jelili Odunayo KazeemCo-Founder | Currently developing a RAG-based app for scope screep detection| Convosync Solutions LimitedNewcastle Upon Tyne, United Kingdom
Evolution is one of the keys to growth. How we do business is massively evolving. We must evolve to control the future. Saving Changes...
