Product Guide

Product types

We offer clients three distinct products delivery paths:

CMS products are based on WordPress with extensions. CMS products may be extended with development projects.  An initial CMS project can usually be delivered in a few Sprints depending upon the design and functionality required.  CMS projects are suitable for marketing purposes and can be connected to Social Media, updated constantly by the client and hosted inexpensively.

Product Evolution

Agile methodology evolves software. The principal values of Agile are:

  • Individuals and Interactions more than processes and tools
  • Working Software more than comprehensive documentation
  • Customer Collaboration more than contract negotiation
  • Responding to Change more than following a plan

Agile itself has evolved two software development frameworks: Scrum and Kanban. We employ these principles:


Each project is estimated over a number of Sprints. Sprints shall be two weeks in duration for Development Projects.

Each Sprint is a delivery or integration stage where finished segments or branches are incorporated and staged (for development).

A Remote Development Sprint has three distinct stages:

a) Initial – the opening sprint establishes the software development, staging and live environments.  A Trello board plan for the project is shared with the Client.
b) Productive – each sprint is ten days, and nine of these are dedicated to achieving the tasks of the sprint. Each completed task is peer-reviewed, integrated and tested on a Staging version of the site.
c) Integration and planning – The tenth day allows the team to present new features and plan the next sprint.


Tasks are managed on a Kanban board (Trello) and daily meetings of the development team should include the client.  


Our aim is to continue development to achieve a Minimum Viable Product so that the Client can market their idea or attract funding to take it to the next phase.  

Git and GitFlow

Proper use of Git is essential to this process. All commits must be atomic and each stage of development is tested before being merged to the Staging branch.

Future evolution

A project may be estimated to be, for example, five Sprints.  Progression is mapped on the Kanban board.  At the end of the projected number of sprints, we expect clients to return with new ideas and the development process repeats with a new proposal for a series of Sprints.