How Agile Are You Really?

rethinkingsoftware.substack.com

5 points·aard··4 comments

I am not very Agile nor am I certain I want to be. Do not get me wrong, I am not satisfied with how my current employer operates, despite claiming to be Agile, but I do not believe becoming more Agile would eliminate a lot of the issues either.

Much of the article reads like a great idea on paper, but I can see plenty of problems arising during execution. Can some teams make it work? Perhaps, but from what I have read, witnessed, and experienced, Agile is a burnout-machine.

how does your current employer operate? how does delivery of working software happen for you?

My current employer is chaotic and disorganized and lacks the necessary communication to operate at its true potential; however, I do not see pure, raw Agile fixing anything. In fact, I think in our circumstances, pure Agile would just be more rope to hang ourselves with.

I remain unconvinced that the reason Agile exist is so BAs, "Scrum" masters, PMs, etc. can all justify their paychecks while bringing little to nothing of value. If I can program a computer, I am certain that I can also self-manage myself/a team. Software development is not a complicated from a business process point of view. I am not sure why all these "methodologies" need to exist.

This Githug page sums up my opinions quite well:

https://github.com/rayfrankenstein/AITOW

I love these kind of think pieces, and I agree with most of the points - it’d be nice to have engineers that are engaged and knowledgeable about their customers… but I’ve never seen this in practice, except for like… emergencies or super urgent things (and it’s always the best, haha). But I wonder about how to tee this up to management or examples of teams doing this in real life.

Reply on news.ycombinator.com