Agile falls short, says author

Agile software development, which aims to offer a much quicker style of delivering software than traditional methods, has not yet met its promise, Steve McConnell, author and chief software engineer at Construx Software Builders, told the the SD West 2006 conference in Santa Clara, Calif., this month.

Presenting on the best and worst ideas in software development, McConnell noted what appears to be a contradiction in agile programming thus far. While intended to focus on individuals and interactions, agile seems to be mostly about processes and tools now, he said.

“It seems to me that the promise of agile development has fallen short at least so far,” McConnell said.

McConnell said after his presentation there has been excessive enthusiasm about agile programming. But he said this has happened before with other new technologies, such as CASE.

Agile programming was discussed during one of McConnell’s worst-idea items: that software practices are based on the assumption that developers are omniscient, and can know all requirements before building an architecture. He cited the traditional waterfall methodology as being based on this faulty assumption.

“I’m not convinced [SWEBOK is the ultimate answer],” McConnell said. “I think it’s a very good start, though.” The other worst ideas cited by McConnell included:

• There are only two development options: iterate everything and iterate nothing (the waterfall model).

• Agile projects are immune to DCI (defect cost increase) dynamics. “The software engineering research really does not bear out this idea,” McConnell said.

• We have to accept “wickedness” in software projects, since they are for wicked problems.

• Requirements are always changing.”[The] single most common source of changing requirements [is] requirements that were not significantly investigated in the first place,” said McConnell.

• Requirements can be gathered or they just drop out of the sky like manna from Heaven.

• Entrepreneurial companies cannot be afraid of risk.

• One single development approach will work best for all projects.

McConnell acknowledged that some of the content was not groundbreaking. “A lot of what I’m going to be saying this afternoon probably is not new. In fact some of it is…old,” he said.

An audience member Prabhu Raghavan, project engineer at Stryker Endoscopy, said he had read some of McConnell’s books and liked the presentation’s emphasis on recognizing that not all code is the same. Risk management pointers also struck a chord. “I like the (the idea of) identifying risks,” Raghavan said.

QuickLink 064240

Would you recommend this article?


Thanks for taking the time to let us know what you think of this article!
We'd love to hear your opinion about this or any other story you read in our publication.

Jim Love, Chief Content Officer, IT World Canada

Featured Download

Related Tech News

Tech Jobs

Our experienced team of journalists and bloggers bring you engaging in-depth interviews, videos and content targeted to IT professionals and line-of-business executives.

Tech Companies Hiring Right Now