Our process

Not married to the process,
married to our goals

At Refaktory, we want our team to be empowered by all the systems that are in place so that they can direct their attention to delivering quality work at a fast and controlled pace.

We believe in passion, but not in fanaticism. That is why we adapt our processes based on what every individual project or client needs.

Understanding

Discovering your business model and the value we can bring to the table.

Purpose

We get an overall idea of the scope of your application. A general analysis is carried out, allowing us to provide budget and development estimates. The overall software architecture is defined, serving as a blueprint for developing the different modules.

Actors

Software analyst, Lead Developer, Project Manager

Deliverables

Budget estimation, overall software architecture

Duration

1–2 weeks

<!--i18n: process.process.sections.1.title -->Understanding<!--/i18n-->

Planning

Turning the scope into a concrete delivery plan.

Purpose

We translate the architecture into a backlog of development tickets, allocate the team, and set a sprint cadence. Functional specifications are written for the first modules so development can start on a shared understanding of what is being built.

Actors

Lead Developer, Project Manager, Software Analyst

Deliverables

Functional specifications, sprint plan, team allocation, project timeline

Duration

1–2 weeks

<!--i18n: process.process.sections.2.title -->Planning<!--/i18n-->

Building

Crafting digital solutions tailored to your needs

Purpose

Through detailed functional analysis, each module is split into development ‘tickets’ - user or dev stories. The development team picks up the tickets until the module is ready for demonstration. Through frequent (typically biweekly) client interaction, the different functionalities are finetuned.

Actors

Lead Developer, Graphics Expert, Project Manager.

Deliverables

Components 1 to X, version 1 deployed in a testing environment, finalized components 1 to X, version 2.

Duration

Variable — typically 3–9 months

<!--i18n: process.process.sections.3.title -->Building<!--/i18n-->

Quality Assurance

Confidence that the software behaves the way it should — under load and over time.

Purpose

We back every release with automated test coverage and a dedicated staging environment. The client validates each module through structured user acceptance testing, and we run performance tests against realistic data to catch regressions before they reach production.