Starting this blog Saloua and I made a vow not to become one of those lovy dovy blogs that treat agile as a new religion (Yep. There are some hardcore believers out there. They can be scary!). We also vowed not to become a pretentious known-it-all agile blog. We díd however vow to write about our journey. And a journey can be hard at times. There are the great highs and there are some lows. We love agile and believe in it’s principles. But let’s be honest. Sometimes agile sucks! It can feel like agile’s really trying hard to make you either cry in a restroom or just give up. So, here’s to honesty!
10 things we hate about agile!
- Control freak, move over! Coming from two huge control freaks, this is a killer. In agile, there’s squad responsibility and ownership. Great. But sometimes it’s not so great to hand over your task to a squattie who still has to learn. Or just does things a little different than you (Not worse. Not better. Just different 🙂 )
- Get real & reveal! Agile is all about transparency and visibility. As every user story, even every task, is assigned to a squad member, you can nicely track progress. It enables the squad to continue improving. But it also exposes your weaknesses and flaws. Always stalling that one task you hate but is part of your job? In agile, that is (sometimes painfully) visible.
- Ambition & realism ain’t always friends! Working at a large organisation, it can be hard to apply agile methodology and culture to your processes, applications and external stakeholders. It takes discipline and patience. Two qualities Saloua and I have a bit of a challenge with. Find a balance between being ambitious and define realistic steps toward that ambition.
- End to end feels like finding neverland! What does the buzz word end-to-end mean? Should you form squads with all capabilities needed for one purpose? And what if a part of your purpose is outsourced? Or what if your front-end guys can only start working when the engine services are fully tested on A? How to form the squad?
- Autonomous yet alligned! Squads are autonomous. Again, great! Autonomy empowers squads and enlarges the execution power of your organization. But being autonomous doesn’t mean there’s no need for alligment anymore. Informing and being informed to make sure your organization is doing the right things is still essential for success. Maybe even more than ever! “Meeting” is not perse a dirty word.
- It ain’t no holy grail! Agile won’t magically solve all your organizational challenges. It requires hard work and – again – discipline and patience. It’s a mean to get you to your goal, it’s not the goal itself. Sometimes people seem to forget that.
- Old habits die hard! Ever tried to stop smoking? Or drinking? Or did a diet? You have to constantly remind yourself to do it differently than your mind is used to due to your previous excperience. Same goes for agile. Used to ask your manager for permission and hide behind that mandate? Not anymore!
- Embrace your mistakes! Agile is all about finding out what works best for your situation using a few basic principles. It takes time to make it work. You make mistakes. You change. You learn. We don’t particulary like mistakes. We sort of hate them. Breathe in, breathe out, learn, adjust, try again!
- What about the bigger picture! Agile encourages you to focus on the next immediate steps. While doing that, it’s so easy to forget about the bigger picture. You need to combine the two, but that can be a challenge to fit into your day to day work.
- Go hard or go home! For us, this is one of the most crucial elements. Your whole organization, from top to bottom, has to stick to agile principles. That means from CEO to junior engineer and from Tribe Lead to Agile Coach. Discipline and patience!
Wow! That’s a relieve! And can you believe that – in spite of it all – we still love trying to make it work every day. Because when it works – and that happens 🙂 – it rocks hard! We are curious, do you reckognise these bullits? Something we missed or maybe something you have a different opinion on?
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.