Our Agile development process
The Agile process is a well known workflow in software development, but it’s often overlooked for web projects - especially smaller ones.
But the foundation of Agile development is to grow a project incrementally, based on feedback, testing and experience, instead of trying to deliver a full solution all at once.
In our own take on Agile development, we split work into 2 week sprints. Typically, the first sprint begins with the creation of an MVP (or Minimum Viable Product).
At the end of each sprint we test and gather feedback, and make a plan for the next sprint.
This enables us to plan the development of the product based on real user interactions and feedback - hard data that tells us what’s working, what’s not and what users want from their experience.
This Agile workflow means that we aren’t making a leap of faith and investing lots of time (and money) into features and functions without evidence that they’re going to be successful.
It creates an organic growth of the project, based entirely on what users want.
The traditional waterfall approach
A more traditional approach to development is the waterfall method, where each stage of the process leads into the next.
The waterfall workflow is usually the best process for websites that have a fixed cost, specification and timeframe.
It’s essential in waterfall development that the first stages (Research and Planning) are done in depth and detail, as it’s much more difficult to make changes once you’ve moved on to the development or testing stage.