Leading CMS requirements
Categorised under: Content management
Seth Gottlieb has written a piece on writing good CMS requirements. To quote:
Generic requirements gathering processes are self absorbed. They are optimized to comprehensively find business requirements, not understand them within the context of business goals. And the more the requirements are abstracted from the goal of managing content, the less they mean. Quantity and completeness are measurements of success rather than usefulness. What is more, most generic requirements analysis techniques are designed for building custom software rather than selecting software. While custom software development goes from requirements to design, when implementing an existing WCMS, much of the design is already in place. The trick to finding a WCMS is to match your needs with a pre-existing design. Generic requirements are an indirect path to that result.
This is all good advice, and something that I’ve written about. What Seth calls “leading requirements”, I call “key selection criteria”. More on good requirements:
James Robertson is the Managing Director of 