Wivvies are happy to bid on fixed prices, when the customer is capable of defining the project at the detail level needed.
Fixed price projects means you have a well defined goal and Wivvies will guarantee that this goal is reached at a pre-negotiated price - in other words Wivvies takes the risk.
In some cases, it would be beneficial to both parties to co-operate on the demand specification at an hourly rate, and then switch to a fixed price once the demand specification is detailed enough to quote a fixed price.
We create the demand specification, and we give the customer a quote for developing the software.
The demand specification consists of a database description, which means tables, columns and relations between tables.
At the same time forms, reports, and other facilities are described and split up into sprints (see below).
All sprints will have a time estimation and a buffer estimation in case of technical problems.
A sprint in Scrum is a short period of time wherein a development team works to complete specific tasks, milestones, or deliverables.
Sprints, also referred to as “iterations,” essentially break the project schedule into digestible blocks of time in which smaller goals can be accomplished.
Wivvies cuts up their sprints into weekly work.
No amount of planning can guarantee a 100% exact demand specification.
In case a sprint have to be re-defined radically or a new sprint emerges, we re-calculate the project estimation, and the customer will know the financial consequences immidiately - in some situations the changes are however inside the buffer zone, and we aim not to change anything.
We try to make as much of the project as possible within the original sprint scope before applying changes - that way we have to alter project definitions less frequently.