* * * AGILE IS NOT THE PROBLEM * * *
For more than a decade, we have heard about “Agile failures”. Sentences such as “Agile is broken,” “Agile sucks,” “Agile is dead,” or “Agile does not work here!” became common at conferences and industry gatherings.
By talking with people who were involved in those failed initiatives –whether they are still there or have left– we can realize the type of story that quickly emerges.
Most of those cases go as follow:
Seasoned Agile coaches, highly-skilled Agile practitioners and even proponents of the Agile Manifesto, have repeated over and over again, that Agile is not a step-by-step guide nor a methodology or an out-of-the-box, chart-based process.
Agile is a set of principles, values and practices founded on proven management concepts, psychological frames and team-work theories.
Cooks rely on recipes; car mechanics rely on step-by-step guides; manufacturing relies on processes. However, organizations that produce creative work rely on people.
Each individual is an independent entity; as a whole, individuals make a company a living system. As living entities, each company is radically different from any other one.
If it is true that processes can be replicated, practices can be copied and equipment can be counterfeited, people cannot.
People behaviors are unique. People responses are inimitable. People habits are singular. The dynamic blend of all of them is what we call culture.
The Agile movement started as a way to collect some principles and values that worked, over and over again, across successful software development projects.
Although it has been growing since its inception and quickly extrapolated out of software-based initiatives, the principles and values remained valid and highly effective.
In an unfiltered-content world (the Internet) –plenty of false advertising and alternative facts and immerse in a completely lack of accountability– there is room for deceptive statements and misleading interpretations. However, common sense and experience can show the right path to follow –one which does not relate to big, fixed charts, descriptive guides or the result of two-day fancy training.
In order to take fully advantage of the benefits that Agile brings to the world, it is necessary to understand deeply and master three sets of elements:
Without that understanding, we will continue hearing stories about failure, complains about confusion and re-work, and tales about the second, third or fourth Agile transformation (attempt) inside the same organization.
To help you avoid becoming the subject of one more of those stories, complaints and tales is the ultimate purpose of agile-thoughts.
Useful? Interesting? Inspiring?
Through the last survey, most of you told us how interesting and useful it would be a section to make comments to the articles.
In fact, 87 percent of you wish to have the ability to post comments, while 42 percent would like to have the chance to questions both to the authors and the community.
The dilemma has been around keeping an open platform or closing it to only agile-thoughts’ friends and followers.
Although we believe in openness and inclusion, the former option would be problematic for two reasons:
The last month we worked hard to figure out a practical way to provide such functionality. The solution would include a one-time signup: as simple as possible, just enough to avoid spam and advertising effectively.
With the October edition, we hope to roll it out and count with your support. Three simple ways:
Stay tuned and be ready to get surprised!
The best gifts become bigger when we have the opportunity to share them. If an article, a paragraph or just a sentence resonates with you, multiply it. Spread the word.
Tell colleagues, former students, clients, teams and friends about agile-thoughts.
Use the opportunity to:
LinkedIn, Twitter, Facebook Slack and email are nice ways to say,
“Hello, I saw agile-thoughts and thought about you!”
If you believe what we believe, pass this gift along … and enjoy it!
2021 © Virginia, USA | Bogota, Colombia | Madrid, Spain
No part of this publication may be reproduced, stored in or introduced into a retrieval system, or transmitted, in any form or by any means.
Individual pieces –including charts, graphs and diagrams– are protected by copyright as collective works or compilation under the copyright laws of the United States of America and other countries, they are strictly for personal use, and cannot be used for commercial purposes without the individual author’s written authorization.