As I mentioned in my post on December 1st, here at WebWorks we are talking to more and more people who are adopting an Agile software development model and as a result wondering how they can adapt their content publishing model to suit.

To help answer that question I have put together a short white paper on “Publishing in an Agile World” that I hope will help answer some of those questions, and in particular show how using ePublisher three stage workflow, of DESIGN. CAPTURE and APPLY, can make the task even easier.

You can find a copy oif the white paper on SlideShare

Or if you prefer just sens me an email at aporter@alanjporter.com and I’ll be happy to send you a copy.

Over at her  just write click blog, top industry commentator and author, Anne Gentle, recently posted an excellent piece comparing collaborative authoring tools.

The blog post had been prompted by the move within her company to adopt an Agile development approach. As Anne remarks the change meant “we’re going from 5 people to 47 people in total who could author external or internal documentation within our two week sprints.”

Later in the piece Anne kindly makes mention of the various ways that ePublisher can fit within this new business model.

Here at WebWorks we are used to the Agile process, we use it internally to great effect and it was key to our switch to delivering four product updates a year. At  our RoundUp conference in 2008 we spent a great deal of time talking about the Agile process and how it applied to the whole company.

But over the last six months or so we have seen a marked increase in the number of our customers who, like Anne’s company, are adopting the process and are starting to use ePublisher as a key component of an Agile workflow.

I often mention that I believe we can learn far more about how our software works by talking to customers than we ever can from lab testing, and I’d like to find out just how well ePublisher is doing in this developing new model.

If it works, what does ePublisher provide that helps make it a good tool for an Agile team?

Are there things we could do better to serve the Agile workflow?

If you are on an Agile team, or know someone who is and would be interested in sharing your insights, please contact me at aporter@webworks.com – I’d love to chat and hear your ideas.