Fixed price

[Fixed price]

Based on an initial, in-depth first project discussion we will make a detailed estimation of the cost of development. As this approach requires a clear analysis of every element of development, unknowns are to be kept to a minimum.

During the development, changes will also be minimal, and will be effected as ‘change requests’. This is the best solution for clients who have a clear overall understanding of their project requirements and an agreed number of deliverables.

Time and material

[Time and material]

For projects whose scope requires more flexibility we recommend the time and material approach. Here, we agree with the client an overall general budget to develop the application, and refine the precise requirements and functionalities during the development process.

This gives the customer greater freedom to change the scope during the development lifecycle, as well an earlier working minimum version of the app for market testing.


[Getting to
know eachother]


Drinking coffee


First meeting & project
discovery workshop


High level scope
First wireframe sketch
Legal requirements
Next steps

[Getting
into detail]


Brainstorm session


Workshops
wireframing


Low level scope
Second wireframe sketch
Next steps

[Getting the
job done]


Workshops
wireframing


Final release
Fully tested
Waranty period
Quality assured

[Giving
support]

Support
New feature requests
Change requests

[Scrum methodology - our work approach]

The Scrum methodology we use to organise and manage development projects prioritises communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities to plan and schedule releases.

In Scrum, projects are divided into succinct work cadences, known as sprints, which are typically one, two or three weeks in duration.

At the end of each sprint, stakeholders and team members meet to assess progress and plan next steps. This emphasis on ongoing assessment of completed work is largely responsible for Scrum’s popularity with managers and developers.

Scrum’s simple set of roles, responsibilities, and meetings that never change make it an appealing option, offering a stability that supports a project’s structure at every stage of development.