The Agile Manifesto works. All (Agile) methods/processes/frameworks do not work. The idea about he manifesto is to constantly (re)think about improving your process (read: way of working). When you adopt a process, like Scrum, and stick to it, you stop doing that. Thus, you are no longer agile.
I complete agree with you. Violation of the first principle of the Agile Manifesto happens way too often.
Too many people out there in the industry, trying to push Agile as a solution to problem X... Without understanding this first line.
It would be weird if we were invaded by buzzwords at each stratum of software development but not on the methodology level. Judging by the amount of books, courses, silver bullets, variations of agile, self anointend gurus and so on, it's perfectly understandable that meanings get lost in the process.
On this website we debate all the time about the viability of this or that approach, of this or that technology, it's not easy to debate the viability of different approaches to develope software as a whole or to manage teams only by the cover.
Ben's approach, to be always changing and refining, it's probably the most functional, but as you said, many people read an article or a book, decide it makes sense because they used it successfully in company X and then use Agile as a hammer. Kinda like some devs use microservices as a hammer because they used them successfully at Netflix ;-)
I'm guilty of using my favorite programming language as a hammer in the past.
This "agile confusion" we're in is understandable and Jira's complexity doesn't help.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Im constantly sadden by
Too many people out there in the industry, trying to push Agile as a solution to problem X... Without understanding this first line.
The end result is many projects being, agile in name only.
And unfortunately with my very terribly small dataset of personal experience. This correlates strongly to those who insist on JIRA being the answer.
The Agile Manifesto works. All (Agile) methods/processes/frameworks do not work. The idea about he manifesto is to constantly (re)think about improving your process (read: way of working). When you adopt a process, like Scrum, and stick to it, you stop doing that. Thus, you are no longer agile.
I complete agree with you. Violation of the first principle of the Agile Manifesto happens way too often.
It would be weird if we were invaded by buzzwords at each stratum of software development but not on the methodology level. Judging by the amount of books, courses, silver bullets, variations of agile, self anointend gurus and so on, it's perfectly understandable that meanings get lost in the process.
On this website we debate all the time about the viability of this or that approach, of this or that technology, it's not easy to debate the viability of different approaches to develope software as a whole or to manage teams only by the cover.
Ben's approach, to be always changing and refining, it's probably the most functional, but as you said, many people read an article or a book, decide it makes sense because they used it successfully in company X and then use Agile as a hammer. Kinda like some devs use microservices as a hammer because they used them successfully at Netflix ;-)
I'm guilty of using my favorite programming language as a hammer in the past.
This "agile confusion" we're in is understandable and Jira's complexity doesn't help.