Plone Advocacy

By now you may have noticed that this blog has a teeny, tiny bit of Plone advocacy in it. However, just as in my presentation to InterLab last week, the bottom line is to make sure you match requirements with systems. That includes feature comparisons to see that tools can deliver needed objectives, assessments to see that staff and consultants can use software systems, and a cold, hard objective review of your ICT environment.

There is no magic online feature matrix, no silver-bullet white paper, no error-free consultancy, no unambiguous, simple answer. A few blogs have attempted to approach the problem (for example, see Benamer and Burton's discussion), but there appears to be no general consensus.

For now I'll heft a toast to the lucky ones in Naples at the World Plone Conference and sit tight until the videos come online in a few weeks. And I think my strategy of measuring progress towards a successful Plone end-state (a widely adopted, stable yet evolving system) is more worthwhile than many other approaches, especially in that it encourages transparency and points towards similar efforts for other software systems.