Manifesto for Opinion Driven Decision and Gossip based development
The satire. Or – data from life.
Based on the inputs of some users and real-life experience I have published here the data on ODD and GBD. Some wordings might cause upset, as intended by the contributors, and I will do my best to ensure you get the point.
We are uncovering disastrous ways of management and by doing it helping management to earn more.
Through this work we have come to value:
- Opinion and gain of power over individuals and common sense.
- Blaming others over self-correction.
- Managements financial gain over human behavior.
- Responding to management over basic natural laws.
That is, while there is value in the items on the right, we value the items on the left more.
Principles behind the ODD Manifesto
We follow these principles:
- Our highest priority is to satisfy the management through early and continuous following of their unique and untouchable decisions.
- Welcome changing daily opinions, even late in development. Opinion driven processes harness opinions for the management’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the opinion needs.
- Business people force developers to daily changes, based on the nightmares of a few.
- Build projects around unmotivated individuals.
Destroy the environment and enforce task force,
never trust them to get the job done but manage on a microservice level.
- The most efficient and effective method of transporting information to and within a development team is the face-to-face devaluation of those who try to get the show on the road.
- Working software is overrated, ensure that the delivery times are met.
- Opinion driven processes promote sustainable management.
The sponsors, developers, and users should be able to act on the everchanging ideas.
- Continuous attention to management opinion and appraisal of the management enhances opinion.
- Overloading–the art of maximizing the personal profits of those who failed –is essential.
- The best architectures, requirements, and designs emerge from ignorance of facts.
- At random intervals, the team is forced to drop their work and never reflects on how to become more effective, but to serve those who are in charge.
- Always f*** courageous colleagues from behind; if my boss tells me so