Workflow. How do we generate prices for tasks?

Owned by Scrile Manager
Last updated: May 02, 2023 by Lisa Shishkina (Unlicensed)
3 min read

Story points

The price for any development services is formed based on the complexity of the task. Thus, the simplest tasks that take less than two hours of work are estimated at 1 sp; tasks that require a full-time average developer at the middle level - 3 sp, 5 sp; a task that will require about a week of work, as well as its testing - 13 sp, 21 sp

The price for any development services is formed based on the complexity of the task, time it will take as well as the risks and uncertainties associated with the task. This unit of measure is called storypoint (sp). The price of 1 sp is $100. Storypoints are not directly tied to hours, but in our experience, on average, 1 sp might be equal to 2-3 hours of work. We use Fibonacci numbers(1 story point, 2 sp, 3 sp, 5 sp, 8 sp, 13 sp, 21 sp). This allows us to make an accurate assessment, taking into account all the factors that go into the concept of a storypoint. Storypoints are not directly tied to hours, but in our experience, on average, 1 sp equals 2.5-3 hours of development.

Storypoints allow us to avoid estimation bias. Estimation in hours of development is less accurate and can vary greatly due to the difference in time spent on the same task by developers of different levels.

Thus, storypoints system lets us take into account all the factors influencing the final result of the development. The formed price reflects the totality of resources required to complete the task. This estimation is the closest to reality and does not depend on the developer working on the task or the project manager.

The video below has a more detailed explanation of the storypoint concept:

https://www.youtube.com/watch?v=VsSaolMtkKU&t=373s

The stages that each task goes through sprint:

We work on sprints. Each sprint is one week and it is planned in advance. We do not take tasks to work immediately after the ticket appears. Increasing the number of tickets requires more careful planning.


0. Before getting to the queue, each task is discussed and estimated by the entire team;

  1. Team backlog - here the task is waiting for one of the developers to take it;

  2. In progress - the task is under development. The status of your ticket also changes to “In progress”;

  3. Code review - is a code analysis to identify errors;

  4. Test queue - the finished task is waiting for its turn for testing;

  5. Testing on dev - the task is being tested on the developer's server;

  6. Release queue - the task that has successfully passed testing on the developer’s server is waiting for its release queue;

  7. Released - the task is released on your site and tested there;

  8. UAT (User Acceptance Testing) - the manager checks the readiness of the task and gives it to the client for review. In this case the Ticket status changes to Customer Review;

  9. Done - if the task is approved by the client, it goes to Done.