Little Timmy, you know what I said about staying away from the medicine cabinet? Do the same with "Agile Project Management"
Seriously though, it's a very broad term and is often done badly. The usual common theme is breaking up the work into very small pieces, and delivering iteratively as opposed to waterfall where everything is speced out, designed, written, tested, deployed one after another.
There are loads of (usually horrible) ways of doing it, the more complicated ones being the worst.
Please note almost all of them have little to do with The Agile Manifesto.
Please note almost all of them have little to do with The Agile Manifesto.
This is my main gripe with all this. Every time you see somebody talk about their Agile process (upper case A), which generally isn't really agile (lower case a).
The agile software development manifesto is not a big document. It's just a few principles. One of the principles is generally violated by the Agile processes which rule in companies who practice Agile software development: Individuals and interactions over processes and tools
They have a process, and that is the way they work. End of discussion.
Quite often companies claim to be agile, but they just do Scrum in the classical sense and to the letter.
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.
Little Timmy, you know what I said about staying away from the medicine cabinet? Do the same with "Agile Project Management"
Seriously though, it's a very broad term and is often done badly. The usual common theme is breaking up the work into very small pieces, and delivering iteratively as opposed to waterfall where everything is speced out, designed, written, tested, deployed one after another.
There are loads of (usually horrible) ways of doing it, the more complicated ones being the worst.
Please note almost all of them have little to do with The Agile Manifesto.
This is my main gripe with all this. Every time you see somebody talk about their Agile process (upper case A), which generally isn't really agile (lower case a).
The agile software development manifesto is not a big document. It's just a few principles. One of the principles is generally violated by the Agile processes which rule in companies who practice Agile software development: Individuals and interactions over processes and tools
They have a process, and that is the way they work. End of discussion.
Quite often companies claim to be agile, but they just do Scrum in the classical sense and to the letter.