3 ms·
"commitments" do not exist in Agile. Agile was created to remove commitments and insert collaboration in it's place. You don't have to make big promises when y
by hopler 8y ago
"commitments" do not exist in Agile. Agile was created to remove commitments and insert collaboration in it's place.
You don't have to make big promises when your client has ongoing clear visibility into your progress.
- JohnFen 8y agoThat is technically be true, but I've worked at four shops that have implemented Agile methodologies and it hasn't been true for any of them, nor for most of the engineers I personally know but don't work with. I do personally know one person who works on a team that this is true, but he's the only one. This may be doing Agile wrong, but if something can be so easily done wrong that it's common, I count that as serious flaw in the methodology.
- cromulent 8y agoagile is not a methodology though - it's a set of principles. Many so-called "Agile methodologies" put structures in place that prevent agility.
- jdauriemma 8y agoI'd push back on calling Agile a methodology. [The Agile Manifesto](http://agilemanifesto.org http://agilemanifesto.org) a set of ideals, that's all. These ideals often run afoul of conventional wisdom in traditional management/business/sales circles, so we end up with a set of procedures masquerading as "Agile" in order to not upset prevailing sensibilities.
- JohnFen 8y agoI did not call Agile a methodology. I referred to "Agile methodologies", as in "methodologies that are intended to adhere to Agile principles".