Way back around 2000, I worked at a company that used what most people would think of as an agile dev process, administered by the devs, for the devs, and it worked pretty well. It did the thing that a software process needs to do: let everyone know what was important, who was working on what, who needed help, and what needed to be done differently. And it was good.
As a _philosophy_, Agile gets those things done. It's fine.
As a _process_, as most places that "do Agile", it exists for it's own benefit and not for what it _does_. In almost all cases, it's a people problem more than a process problem, but no process will solve those sorts of people problems.
As a _philosophy_, Agile gets those things done. It's fine.
As a _process_, as most places that "do Agile", it exists for it's own benefit and not for what it _does_. In almost all cases, it's a people problem more than a process problem, but no process will solve those sorts of people problems.
reply