Your Project Is FAKE Agile, What Now?
Agile Development • Health & Wellness
It's finally sinking in. Your software project is FAKE agile. Is there anything you can really do about it?
Watch or listen to this episode
YOUTUBE
SPOTIFY
APPLE
Coping with Fake Agile: Strategies for Surviving and Thriving
If you’re on a fake agile project, you’ve likely noticed that the main concern at your company is getting things done on time. It’s all about efficiency and deadlines, not about being flexible or truly adapting to customer feedback. This is a far cry from what agile is supposed to be—where adapting to feedback is a core principle. But what do you do when you find yourself in a situation where the reality of your project doesn’t match the agile ideals?
Recognizing Fake Agile
Are you working at a company that claims to be agile, but you’ve realized it’s just not true? Or maybe you’ve always been skeptical of agile software development because, in your experience, it has never delivered the benefits it’s supposed to. You’re not alone. I’ve been in that situation many times, and I’ve coached a lot of developers who have come to the harsh realization that what they’re dealing with is fake agile.
Unfortunately, fake agile has become the norm. More companies claim to be agile than actually practice it. So, if you find yourself stuck on a project that isn’t truly agile, how do you cope without losing your mind?
Here are six practical strategies to help you survive—and even thrive—on a fake agile project.
1. Let Go of the Expectation to Fix Everything
The first thing you need to do is let go of any expectation that people will get the terminology right. This might be the hardest part, especially if you’re passionate about agile principles. You may feel compelled to correct people, to educate them on what agile truly means. But if you’re on a fake agile project, trying to fix the system is only going to drive you crazy.
Accept that the system is broken and that your efforts to change it are unlikely to succeed. Focus on what you can control—your own work and how you respond to the situation. This acceptance is the first step to finding peace in a chaotic environment.
2. Exercise to Manage Stress
I know this isn’t what you might want to hear, but exercise is crucial. When you’re dealing with a frustrating project, it’s easy to turn to temporary distractions like video games, YouTube, or even unhealthy habits like smoking or drinking. But these only offer temporary relief.
Exercise, on the other hand, fills your body with endorphins, serotonin, and other chemicals that help you cope with stress. If you start your day with a workout, you’ll find it much easier to handle the frustrations that come with fake agile. You’ll have more patience, and the things that used to drive you nuts will start to roll off your back.
3. Become a “Requirements Lawyer”
One of the promises of agile is that you don’t have to write detailed requirements—just user stories. But if you’re on a fake agile project, this approach can backfire. When the focus is on deadlines and efficiency rather than flexibility, you need to protect yourself by becoming a “requirements lawyer.”
Treat your user stories, acceptance criteria, and any other documentation as a contract between you and the business. This way, if there are any misunderstandings or changes later on, you can point back to the agreed-upon requirements and avoid being blamed for not delivering what was expected.
4. Charge for Changes
When changes inevitably come up—because they always do—you need to make sure the company understands that changes come with a cost. This could mean adjusting the deadline, reducing the scope of the project, or extending the budget. Don’t let management pressure you into absorbing these changes without adjusting the original commitments. Stand your ground and make it clear that changes require renegotiation.
5. Protect Your Reputation
On a fake agile project, protecting your reputation is crucial. This means buffering your estimates to allow for unexpected challenges. Management might tell you to estimate for the ideal case and that they’ll handle the buffering, but don’t rely on that. Add your own buffer to your estimates to protect your time, your reputation, and your sanity.
6. Define Your Own Success
Finally, you need to define your own success on the project. If you measure your success by the overall success of the project, you’re setting yourself up for disappointment. Instead, focus on what you can control—improving your communication skills, learning new technologies, or building better relationships with your team. By defining success on your own terms, you can walk away from any project, no matter how broken, knowing that you did a good job.
Conclusion
Are you on a project that’s fake agile? It can be incredibly disheartening, especially if you’re passionate about doing things the right way. But it’s important to accept that you can’t always change the system. Instead, focus on what you can control, protect your own well-being, and define success on your own terms.
If you’re struggling with fake agile and looking for support, consider joining my private Discord server through Patreon or YouTube membership. There, you’ll find a community of like-minded professionals dealing with similar challenges. You don’t have to go through this alone.
About the THRIVING TECHNOLOGIST show
On YouTube and all major podcast networks, Jayme shares teamwork and leadership strategies, guidelines for healthy company culture, and stories about real projects so you can have a sustainable career in the software industry.
Jayme Edwards
A family man and veteran of nearly 40 software projects, Jayme experienced many wins and losses over his career as an architect and consultant.
Now he's coaching software developers, managers, and business owners to overcome challenges in the IT industry - so they keep growing.