Wivvies are happy to bid on fixed prices, however some projects simply do not have a demand specification that is clear enough to estimate a price.
In this case, Wivvies needs to charge per hour for the project.
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 as detailed as we can, and we always give the customer a "ball park" amount.
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).
In case we do not have all details, we will define "other sprints" where we estimate what is plausible in terms of work not yet defined.
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.
Sprint Reports are designed to help you understand your team’s performance across active & completed Sprints.
Sprint Reports are a handy tool to conduct successful Sprint Retrospectives, help organize future sprints better and improve the agile quotient of your team.
You can quickly understand the work that has been completed and the ones that were returned to the backlog with the Sprint Reports.
A Sprint Report will provide you with a list of all associated tasks of the Sprint and their status. You can clearly see how many of those tasks weren’t completed and were pushed back to the backlog or reprioritized and/or sent to another active sprint.