Fragile Manifesto
If you think the Manifesto for Agile Software Development brought us all closer to World Peace – think again! It’s not the comfy and cosy team spirit that rules. But Fear is:
Jail-like isolation over individuals and interactions.
Strict rules over working software.
Healthy ignorance over customer collaboration.
Telling others to Shut Up over responding to change.
This is, while there is currently some hype for the items on the right, the items to left simply beat more meat!
And if it breaks, ship it. We are fragile, after all.
Advertisement
May 4, 2009 at 752
Since switching to SCREAM as a development philosophy we are experiencing a major increase in lines of code per hour. No more time robbing planings, estimatings and dull reviews.
Thank you fore giving us a giant lecture in FDD!
Sincerely your
Bunker Code Team
May 4, 2009 at 762
We finally got rid of customer feedback! No more whining like “Could you pleeeese fix bug #453349 – pleeaase?” or “We desperately need feature bla bla bla.” – Hell. No!
A healthy portion of ignorance can get you forward. No doubt!
Along with other improvements “project napping” is within reach! Fragile development changed my life – Chilling at work is fun now!
May 4, 2009 at 770
I got sick of my coding slaves – IMHO I found a cure for my pain by following the “Fragile Manifesto”!
All C.S. now work in shifts 24-7 in the basement. That gives me a bunch of new opportunities such as a indoor gulf club and a management lounge!
That’s a hell of a Product Owner life! I tell you! LOL!
May 4, 2009 at 834
Help! They want to increase productivity. What shall I do? I just got used to not releasing!
May 4, 2009 at 836
Establishing another steering committee on top of the water-head-board was a leap forward! Tis site was so inspiring. Thank you!
May 4, 2009 at 875
The road to success:
We came a long way – first we retired the old quality manager: Be honest! Do you really need to test your code? No! You don’t! Just believe in your strength!
Then we pushed responsibilities to the max. Now the new guy takes it all. LOL.
Last: The key is to have rules – they don’t have to be fair but strict! And you’ll always find someone to blame. Punishment first! Yes, you can!
Don’t ask what you can do for the project! Ask what the project- management can do for you!
Cheers
Jim
May 6, 2009 at 944
Hi Folks
We have the whole theme of “Fear Driven Development” and “Fragile” in our Company with management and the developers discussed. We had already noted in the past that we have already exceeded the zenith and had an urgent need for new ways. Management has to decide which path to go further and fully on “Fragile Development” must be set. Based on my experience I was appointed the rules of “Go Fragile in the enterprise and to make sure that each developer, each student, each char the basic principles are followed! For me, this evolutionary development of our corporate philosophy a clear career dar.
Even though I am still in the design phase, I can but at some points of my plan for the enforcement of management policies to:
* Each employee must have the “Fragile Manifesto” can recite from memory. No matter what time!
* We will create a closed section, which deals exclusively with the specification employed. Documents are created after one year of preparation to the developer over. Conceptual errors or ambiguities are punished those responsible – this is a “public blaming” salary sacrifice and voluntary provision.
* Management will in the future exclusively via SMS on the status of the projects. This form of communication to their workload is reasonable and the content is necessary to reduce the maximum.
* We are the walls between the offices and thus remove the space, in that the 95 developers can share. Direct communication is particularly at cross-cutting issues is a key to success.
* Also, the distribution must finally convince customers that we are not prepared to his weak-witted ideas into practice. This is a clear voice system named foot hold.
These are just some points that I do with all the harshness and brutality within the shortest time with the blessing of the management will implement. And if it breaks, then in a thousand pieces.
Please excuse my bad English.
Greeting
Dr. vet. (VRC) Patrick Klotzfuß
May 6, 2009 at 956
Patrick,
Thanks for sharing your strategy. It is great to see that you are turning your company just onto the Right Path.
And with “public blaming” you are definitely an early adopter of The Next Big Thing!
Keep it fragile!
May 7, 2009 at 385
[...] This post was Twitted by tomsulston – Real-url.org [...]
May 15, 2009 at 915
Finally we have a methodology that will make those programmers shut up and do what I tell them. Your Aren’t Going To Need It? Bah! Because I’m Your Boss!!!
Very funny. Much appreciated.