Category Archives: Agile Development

Using Agile Methodologies Presentation

Below please see the slides from the presentation I gave today at the Outsell Signature Event at the lovely Ritz Carlton in Half Moon Bay, California. I’m passionate about agile development because I’ve simply seen too many waterfall train wrecks that either kill companies (e.g., Ingres) or nearly kill them (e.g., Business Objects).

In many cases, those software development messes actually obscure underlying deeper problems. For example, at Ingres, I’d argue the root cause problem was a lack of competitive strategy for dealing with the fact that the company had been “lapped” by Oracle, resulting in a ridiculously long requirements list. But, I’d further argue that a realistic agile process would have made evident that the list could not be accomplished and may have forced the company to more quickly deal with the ugly reality that it faced.

One key point that’s not on the slides is that while most publishers will say “yes” to a survey asking if they are using agile methodologies, my anecdotal data suggests that those same companies’ IT leadership don’t see things the same way. For example, at the panel session on agility hosted by Marc Strohlein at last Spring’s Mark Logic user conference, one of the top audience questions was, in effect, how can I do agile at a company that isn’t?

Perhaps someone (e.g., Outsell?) needs to do some gap analysis between the business and IT sides of the publishing industry on this issue.

Every Publisher Should Read This: Agile Development

Just a quick post to highlight a report done late last year by Outsell entitled “Keep Ahead of the Competition with Agile Development.”

As publishers increasingly become application developers who build information products that mix software and content, they increasingly need to adopt state-of-the-art software development practices and methodologies.

Surprisingly, many of the publishers we work with are still doing big-bang development projects following a waterfall approach. I beleive that agile approaches are far better, particularly in the uncertain environment in which publishers find themselves. Rather than specifying huge projects up front, building them over a long time period, and hoping they work when launched, they need to deliver software fast and interact with users about what they’ve built.

Put simply, if you’re a publisher and you’re not doing agile development you should click here to buy this report for $395. (You can thank me later.)

You can read the excellent Wikipedia entry on agile development here. You can find the pithy Agile Manifesto here. You can find my blog post on content agility here.