Antsstyle
2 min readDec 30, 2021

--

Actually, it is you who need to become more knowledgeable. You are treating Agile like a religion, where anyone who doesn't do it the way *you* think it should be done is just a false believer who isn't practicing true Agile, when that is not how it works at all. You are not the authority on how the Agile Manifesto should be interpreted, and neither am I, which is exactly why it is done badly so often; there is no authority who decides how it should be done, and the result is a tendency to bend to commercial pressures. Certification doesn't help that since many companies will embrace their own idea of Agile regardless.

I note that "ask devs to do maintenance in their personal time" was sarcasm, which you appear to have missed. I asked what *your plan* is for maintenance, because your writing implies that you think maintenance will magically perform itself with no time allocated to it by anyone. Therefore I suggested that sarcastically, because you seem to have left all other possible options for maintenance time closed, unless you have invented a time machine.

I also didn't advocate for 'pushing devs harder'. I told you the commercial reality of most companies is pushing devs harder when you want 'adaptation', I did not say that is a good idea. Your last response implied that you think "adaptation" is some magic solution when you need to meet an impossible deadline, but that is not how it works in reality - companies often decide there is no need to adapt if they can simply force devs to work longer. That's how *companies* think, not how *I* think. I'd like to see crunch and other such practices gone, because 'pushing devs harder' is a terrible practice that destroys teams in the long term for short term profit.

I can't believe I have to say *this* either, but if you think you will ever work in a company where you don't have to obey the commands of your manager, I'm afraid I have some bad news for you.

--

--

Responses (1)