The Plan: Once we understand what our Customers want we need to set about delivering it. Working with our Customers we break the “User Stories” into a number of iterative releases. Between us we will have already assigned a priority and complexity – which helps us build this release plan. This identifies when new functionality will be incrementally deployed to your test environment. These incremental releases are typically delivered on a frequent basis as we’re constantly looking for feedback.

Iteration, Iteration, Iteration: Once we all have a clear Release Plan we start being techies – writing code, creating data feeds and building integrations. However, we don’t sit in darkened rooms only to reappear several weeks later with a finished product – that may or may not meet a Customer’s requirements. Instead the emphasis is still about collaboration. We are in constant contact with our Customer – demonstrating prototype screens, seeking clarification or discussing how aspects of the CRM toolkit can be used.

At the end of each iteration we put our latest work into your test system. We’re looking for Customer feedback on each iteration, which we use to shape future iterations. That way we continuously shape and improve the final system, whilst ensuring that we quickly eradicate any issues or misunderstandings.

Controlled Agility: Whilst our approach is agile our philosophy to development is certainly closely controlled. Our team always use the latest source control tools, follow best practise guidelines, work with appropriate technologies and track changes against User Stories.