How to correctly estimate the terms for developing a site in a web studio?

Question

Project management

Hello!
I am a beginner developer working in a website development studio. Often I am asked to estimate the terms for developing templates or finalizing the site. I try to set a short deadline so as not to irritate the PMA. However, in practice, it often turns out that in the process of work, pitfalls arise in the form of unpredictable bugs, technically difficult design decisions, etc., which greatly increases the actual time for working on projects. It is especially difficult to evaluate something that I have not yet encountered, even roughly compare it, as a rule, there is nothing (
How can I solve this dilemma?

Answer 1

must be multiplied by three.
underestimating is the dumbest thing you can do. PMU will be more painful if you miss the deadlines.

Answer 2

“When I was young, I asked my boss how to estimate the time to complete a job? And the boss answered me:
- The time that you plan to multiply by Pi in half, plus 2 weeks.
Why Pi in half? I was surprised.
- Because in real life you will never move towards your goal directly, but rather along the arc of a circle.
Why plus two weeks?
“But because when you end up missing all the deadlines, then in two weeks you will have time to do at least something.” (with)

Answer 3

Answer 4

>>> I try to set a short time limit so as not to irritate the PM
Key phrase. You have analyzed your own behavior well. Now all that's left is to fix it :)
You have 2 options:

1. Give a short time and not cause irritation in the PMA. First of all, if your PM gets annoyed by such things, then that's the PM's problem, not yours. Second, if you can't meet deadlines, you'll get more annoyed. And in order to withstand them, you will have to sacrifice, up to your personal life.
   
2. Give appropriate deadlines. If the PM is adequate, he will ask them to justify. If inadequate, then he will begin to resent, stomp his foot and tear. Think about whether you want to work with such a PM.
   

Correctly said above that multiply the term.
Personally, I always multiply the period of work by the "Coefficient of Optimism". It ranges from 20% to 200%, depending on my optimism in the task. If everything is OK and it is clearly clear what needs to be done, then the minimum value. If the task is blurred, hemorrhoids are expected, etc., then the maximum.
The choice is yours.

Answer 5

I said this, I take a week to review the scope of work and identify what to work with directly. If it doesn’t cause any difficulties and I can do everything well in a week, if not, I’ll write off in a week how much more time is needed, there’s no other way.

Answer 6

Evaluate taking into account the pitfalls.
You can give two terms - minimum and maximum, and within this framework, do the task

Answer 7

Yes, do not count.
Say the term, with the note "if everything passes without special dances and nothing pops up"
And let him put it on himself, he thinks. Its' his job.

Answer 8

The most correct thing in estimating deadlines is to keep them.
Let them be big, but you will hand over your task exactly on time. This will be a much greater plus for you than trying to "guess the timing" and deceive people. Don't fool yourself first.
With the observance of the deadlines, on the contrary, it will play a big plus for you, in the future, because you comply with them.
By the way, about the robot with the manager is well described by Robert Martin in the book "The Ideal Programmer". He just writes there that one should not be led by the PM, and one should be able to say "no".
Well, or such an answer))
First, you will fiercely screw up deadlines, tasks. But you will gain experience and you will already accurately evaluate your work. Everyone went through this, everyone who sits on this forum.

Answer 9

The most correct answer is not to work where you are forced to evaluate tasks.
This tiler or finisher can say adequate terms, and in the world of software, terms are a very relative thing.

Answer 10

Looking at how chewed up the tasks are. For me, the volume and unpredictability coefficients from 1 to 5 have the greatest influence, multiplying we get an estimate of 1-25 hours, this is conventionally such 5 tasks per day or 1 task per week.
This estimate will only work on an average of 3 months, so this is not a guaranteed time frame, but rather the most likely outcome.