On Feb 11, 4:05 pm, Arne Vajh?j<a...@vajhoej.dk> wrote:
On 2/10/2012 11:26 AM, simplicity wrote:
On Feb 8, 11:51 pm, Iqra Educational Portal
<iqraeducationalpor...@gmail.com> wrote:
Agile software development is an iterative, incremental approach to
developing and releasing software. A range of agile methodologies have
emerged and they are based frequent releases, ongoing testing,
customer and stakeholder participation throughout the development
process, co-ownership of code and pair-programming.
iQRA?s Agile Exam will test your knowledge about Agile Development
including XP, and SCRUM techniques in the light of Agile Manifesto
http://iqra.org.pk/certification-startup.aspx?CertID=11&type=
Agile is garbage. Code before thinking.
All at the expense of quality but creates lots of "overhead" positions
for largely worthless project managers of all kinds.
Most agile processes does not specify overhead positions
and quite a few does not even include project managers.
I think you have completely misunderstood agile.
Misunderstood? I am judging from my personal experience. I was part of
agile development in 3 environments: small organization (< 40 people)
which was trying to implement it, mid-size and large - by large I mean
800 employees. Each was a failure in one aspect or another. And in
each, the common themes were (1) a blotted overhead, (2) questionable
quality, (3) lack of architectural consistency and (4) reoccuring
breaks of the old and often obscure features.
Interesting that when I raised these issues (with examples) during one
of the internal seminars on agile, the presented, some "big kahoona"
consultant on agile, quickly diverted into a different topic