Organizations adopt agile to be able to handle changes. Agile helps teams to deliver products that satisfy the needs of customers; products which do not contain unneeded (and unused) features. Lean software development says: everything not adding value to the customer is considered to be waste. How can a transition from waterfall to agile software development help organizations to reduce waste?
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
A series of recent articles by Steve Denning on Forbes have highlighted the challenges that the Agile community faces to get acceptance by mainstream management.
Scott W. Ambler provides some analysis on the latest Agile State of the Art survey. InfoQ follows up with some other insights and questions.
Scott Ambler published the results of his annual IT project success survey, in which he examined the impact of methodology on project outcome. He looked at five different "development paradigms" and how they influence project outcome: ad-hoc, iterative, traditional/waterfall, agile and lean. Ambler's definition of success is deliberately subjective - how did the customer feel about the outcome?
As western governments struggle with difficult debt to GDP ratios, the UK is turning to innovation and agile practices to help create a more efficient and less risky IT project delivery framework.
40 years after the NATO Conference on Software Engineering, Tom DeMarco paused to reflect on the discipline's evolution, wondering whether the metrics orientation he championed has distracted from the real point of computing: "transformation, creating software that changes the world." Is his earlier advice valid, though? "No", he said, in Software Engineering: An Idea Whose Time Has Come and Gone?
In a recent newsletter, Scott Ambler looked at why fixed price projects tend to overrun and often fail to solve the business problems they set out to conquer. Scott named the key problems in fixed price projects, identified the bad habits they encourage for customers and developers, and ended with a call to revisit how we fund our IT projects, offering an alternative.
InfoQ editor Deborah Hartmann interviewed the creator of the CHAOS Chronicles, Standish Group founder and chairman Jim Johnson. The Standish Group's statistics on project failure are widely quoted, as they have been since the first survey results came out in 1994. Jim spoke with Deborah about his research, and the role of Agile in changing the IT industry.