How to save products in a team. Pt.2

Even experienced developers note that when they look at the task, it seems to them that it will not take much time, and when they start direct implementation, they understand that everything is not so simple.?This is due to the fact that the task was initially estimated superficially.?After all, often creating even a regular form with two fields and a button can take more time to develop than it seems at first glance.

?What do our colleagues think about task assessment?

?When evaluating, I use three main criteria.?The first is the allocated resources for solving the problem: are there all accesses, is the technical specification complete, etc.?The second is the organization of labor: the priority of the task, the need for communications in the process of its implementation, business processes, and so on.?The third is the amount of work.?Then I add another 30% of the time for expenses: urgent calls, additional questions, “falling meteorites”, falling into the eternal Tsukuyomi and more.

?When evaluating new features during development, it is also important to consider the time it takes to make changes to all the necessary parts of the project.?That is, before the assessment, you need to analyze all the places where changes may be required within the framework of this task, communicate with the team leader, PM or team, clarify all the places that will be affected.?Otherwise, you can not do everything, or change where it is not necessary.

?Possible solution for a case for a developer

?To estimate the time to solve the problem, it is necessary to represent the steps of its implementation.?It is important to remember that this process consists not only of coding.?You also need to set aside time for:

?Clarification of details, communication with analysts, etc.

?Debugging code.

?Other possible risks.

?And if there is uncertainty in the assessment, you can always come and consult with a more experienced specialist.

?To help the project manager, team leader, product owner

?How to detect such a situation on your project (alarms):

?The task goes beyond the planned estimate, the performer moves the deadlines.

?Increased communication on the task between the developer and the analyst or the author of the task.

?There are more than two returns of one issue from testing or acceptance by the issue author.

?More than 30% of tasks from the backlog have no description or it is very scarce.

?What to do in this situation??The most popular methods:

?When planning, discuss the pitfalls of the task and ask questions whether everything is clear during implementation.

?Prepare a task template with the minimum information that you need to specify in the task.

?Ask to conduct discussions not verbally and in personal correspondence, but in the task.

IT development outsourcing team.?https://getupit.tech