How we work

Estimation and proposal


The product draft allows us to move to the next part of the product development - the Estimation and Proposal phase. Estimation entials predicting the amount of effort and time required to deliver the product. The proposal contains an estimated duration and costs of the project.

An accurate estimation, which requires experience, involves:

  • Dividing the project into User Stories
  • Defining the technology stack
  • Determining the team size and composition.

Defining User Stories

The first step of this phase is dividing the project into User Stories. A User Story is a description of one or more features of a product told from the perspective of the end user. It is focused on the value it will hold for the end user, not on its technical implementation.

Defining the Technology Stack

The next step in the estimation process is defining the initial technology stack. The technology stack is the combination of software and programming languages that will be used to develop the product.

Determining Team Size and Composition

After defining user stories and the technology stack, the optimal team size and composition should be determined as well. The optimal team size depends on the project complexity (the number of user stories and the chosen technology stack) and the skills and experience of the team members.

Based on previously gathered information, an estimation of every user story is done during this stage. This leads to the cumulative Estimation of the entire product. As a result we can create the Proposal.

Estimation example

The Proposal should present estimated time and costs based on the gathered requirements, the chosen technology stack and the team size.

Proposal example

When we send this proposal to the client and after we get the approval, we are ready to start the Project Preparation phase.