Delivery

Framework

A typical Plone engagement for us roughly follows the steps indicated below. Should your requirements be reasonably vanilla, this can be achieved fairly quickly and cheaply.

We can (and do) deliver very sophisticated Plone offerings covering much more than ECM/CMS applications, and the bespoke nature of these makes timeframes and costings much more variable. Regardless, delivery happens at a rapid pace, with iterative deployment, and milestones.

• vanilla Plone deployment/pilot

• project manager/analyst user/features training

• requirements gathering * may be multi-phase/iterative - doesn’t need to be big bang * additional products/extensions/content types * other services - email, access and identity management etc * any legacy data migration * hosting options

• timeframe estimates * terms of reference * full job costing, both delivery and operational * deliverable priorities

• deployment * multiple dev/test/production environment setup (if required) * product/extension install and configure * other Unix/Linux services install and configure * website look and feel and templates * legacy migration scripting and loading

• user training