3 ms·

I hate agile. And I'm a dev. This is not a matter of hating the wrong thing or not knowing what agile is. I literally hate agile, i think the definition of agi

I hate agile. And I'm a dev. This is not a matter of hating the wrong thing or not knowing what agile is. I literally hate agile, i think the definition of agile is loaded. I propose a new form of project management called "Relativity." The definition of relativity based project management is effectiveness. If something is not effective don't do it, if something is effective do it. Wait aren't devs doing this anyway? Is putting a fancy word on top of this obvious concept pure BS? Is this what agile is doing? No it can't be BS. Not when people can take a class for it. Once a class is made for "Relativity based project management" you know it's no longer BS.

mindcrime 7y ago
So which principles from the Agile Manifesto do you disagree with, exactly? And what is the alternative that you would prefer?
- crimsonalucard 7y ago
  I'm gonna name a new process of walking, but not just walking... effective walking where you avoid obstacles. I'm going to give it a fancy name and call it "Quantum movement." It's different from regular walking as Quantum movement adapts to terrain and avoids obstacles where the priorities of the person who is walking are satisfied. Agile is the same concept as above. It's different from regular development as it's trying to satisfy the customer.
- alkonaut 7y ago
  One alternative I prefer: not specifying any deliverables or deadlines at all. It’s just that mangers often have a hard time selling that to stakeholders. But if you can be in that process, it’s fantastic. That is “our product is great, but it’s going to be outdated in 10 years, so we’ll put you 5 devs in a room to try to build the Next Big Thing”. I did that and it was great.
  - username90 7y ago
    Sounds like my job, seems to work at Google at least.
  - kthejoker2 7y ago
    Yeah, a process like this is applicable to maybe 5% of development projects out there, and is definitely not ripe for abuse by all and sundry in the other 95%. Demonstrate you're producing valuable work on a regular, fixed cadence. Use whateve process you want to do so. The hard part is defining value somewhere below "the whole project is done." Harder than it sounds, people get it wrong all the time, astoundingly so, almost to the point where I'm convinced it's some sort of evolutionary defect.
    - alkonaut 7y ago
      Completely agree. But here is the thing: as a developer I'm probably going to dislike any process that management and stakeholders agree is viable. It's not that I expect to find myself in any kind of non-viable process, but I also don't expect to not dislike it.
  - yoz-y 7y ago
    That is a great way to do software if you have unlimited money. This can be achieved either by working on something that does not yet have any stakeholders and get income from elsewhere or by working at a huge company that has time to spare. If you want to create a company that is profitable, you absolutely must have a deadline for shipping something. If you don’t decide one yourself then your bank account will do it for you.

mindcrime 7y ago

So which principles from the Agile Manifesto do you disagree with, exactly? And what is the alternative that you would prefer?

crimsonalucard 7y ago
I'm gonna name a new process of walking, but not just walking... effective walking where you avoid obstacles. I'm going to give it a fancy name and call it "Quantum movement." It's different from regular walking as Quantum movement adapts to terrain and avoids obstacles where the priorities of the person who is walking are satisfied. Agile is the same concept as above. It's different from regular development as it's trying to satisfy the customer.
alkonaut 7y ago
One alternative I prefer: not specifying any deliverables or deadlines at all. It’s just that mangers often have a hard time selling that to stakeholders. But if you can be in that process, it’s fantastic. That is “our product is great, but it’s going to be outdated in 10 years, so we’ll put you 5 devs in a room to try to build the Next Big Thing”. I did that and it was great.
- username90 7y ago
  Sounds like my job, seems to work at Google at least.
- kthejoker2 7y ago
  Yeah, a process like this is applicable to maybe 5% of development projects out there, and is definitely not ripe for abuse by all and sundry in the other 95%. Demonstrate you're producing valuable work on a regular, fixed cadence. Use whateve process you want to do so. The hard part is defining value somewhere below "the whole project is done." Harder than it sounds, people get it wrong all the time, astoundingly so, almost to the point where I'm convinced it's some sort of evolutionary defect.
  - alkonaut 7y ago
    Completely agree. But here is the thing: as a developer I'm probably going to dislike any process that management and stakeholders agree is viable. It's not that I expect to find myself in any kind of non-viable process, but I also don't expect to not dislike it.
- yoz-y 7y ago
  That is a great way to do software if you have unlimited money. This can be achieved either by working on something that does not yet have any stakeholders and get income from elsewhere or by working at a huge company that has time to spare. If you want to create a company that is profitable, you absolutely must have a deadline for shipping something. If you don’t decide one yourself then your bank account will do it for you.