Our Methodology

Digital Solutions - Our Methodology

Our Proven Approach to Digital Solutions

At Separate Reality we use tried, tested and trusted methodologies to deliver each of our digital solutions, whether a large or small project.

Our project methodology is a set of guidelines and processes that are used to deliver a project from the initial planning to the execution of a project. Proven effective, our methodology can help reduce risk and take advantage of resources to help deliver a project effectively.

Read on to find out how we use the Rational Unified Process (RUP) coupled with the V-Cycle for documentation and combinations of Waterfall and Agile Scrum for the implementation of projects.

Rational Unified Process

Rational Unified Process (RUP) is a project methodology where the life cycle of a project is divided into four phases: Inception, Elaboration, Construction and Transition. Each of these phases has a core milestone that must be met before moving onto the next phase.

During the inception phase, our goal is to identify the customer’s requirements and specify the project scope. Throughout the inception phase, we work closely with our customer to ensure that no requirements have been missed, analysing and prioritising what they need. This phase is documented by the production of: Business case, requirements spreadsheet, defined roles and responsibilities, an agreed meetings schedule and user acceptance tests.

During the elaboration phase, we delve into the business requirements in more detail. Use cases are used to explore the requirements. These use cases are then applied to drive the solution design. This phase is documented by the production of the following artefacts: HLD (High Level Design) and TOM (Target Operating Model), and execution plan, use cases, interface catalogue, designs (both wireframes and sketch), and functional and integration tests.

During the construction phase, the development takes place. At the end of the construction phase, the solution is ready for functional and integration testing, as defined in the elaboration phase. The artefacts created during this phase are the actual software that makes up the solution along with the unit tests.

During the transition phase, the solution is put through functional, integration and user acceptance testing and includes a stabilisation period following a soft launch, where systems and customer feedback are monitored to identify any issues. In addition, weekly or twice-weekly triage calls are conducted to go through tickets raised and prioritise and assign bugs so they can be fixed allowing for a rapid response to any issues raised.

Once the full range of testing is complete and signed off by our customer and the stabilisation period is complete, the solution is ready for release into production.


The V-Cycle is a model which enables traceability between the specification and development phases of the project, and the testing and delivery phases of the project. The traceability, making sure all artefacts have a test case, is documented in the specification and development phases.

Waterfall Methodology

Waterfall is our methodology of choice for pure integration activities. Driven by Kanban, our waterfall methodology requires real-time communication of capacity and full transparency of work. Clear criteria need to be met for the project to move from one phase to the next.

Agile Scrum

Agile Scrum is our chosen methodology for front-end development. We define our aims at the beginning of the project and work closely with our clients to achieve these. This methodology focuses on a cyclical and iterative model of design → development → feedback → iteration, allowing us to be flexible and reactive to change throughout the process.

Get in Touch

Click Here

Sign up to our newsletter