Delivery Methodology

Agile Delivery Methodology

Through many years experience delivering ECM solutions we have found that a Scrum Delivery methodology provides maximum ROI for implementing an ECM solution into an Enterprise. Using Scrum, requirements are delivered in order of importance to the customer ensuring the implemented solution evolves with the customers growing understanding of ECM principles and how these are most effectively delivered in their business domain. Our methodology may be summarized as follows, where each sprint is time boxed into a 3 week iteration:

Discovery Sprint:

Determine the high level business requirements for the project and ascertain their order of importance to the customer. Create a high level solution design to map requirements to the Alfresco platform and integration solutions to existing enterprise applications. Carry out a POC, this is used to prove the solution and educate the customer on how the solution will function.

Build Sprint(s) (repeat until complete):

A series of build and release sprints with continuous feedback of requirement changes at each iteration. The steps for each sprint are as follows: Determine sprint deliverables and map these to ECM suite capabilities. Implement & test Release to production

Handover & Support Sprint(s)

Develop and provide Train the Trainer type training around the implemented solution. Ongoing support and enhancements.