#1 Mistake When Estimating a Project's Time

preview_player
Показать описание
Follow for more Android & Kotlin tips 🙌
Рекомендации по теме
Комментарии
Автор

I learned this the hard way, It was the most stressful week of my life.

picassoofai
Автор

This is a common business practice. Inexperienced developers try to be accurate on their estimates for large tasks and think it is good to ask as little time as possible. Experienced developers adds more time than they think for the unforeseen issues. For example, if a large task takes 30 hours, ask for 50 hours. I learned this hard way unfortunately. Very good video.

littlebitofeverything
Автор

Managing expectations, its the same thing in company coding. Manage the expectation of the manager. That way you also do not burn out. You code better and longer when you have joy and your body still work ( sleep well exercise )

TheBlackManMythLegend
Автор

Currently in my 3rd month of a project which was supposed to take 1 month

kobbykolmess
Автор

As an Android developer, do you hire someone to handle your backend development? Because I'm sure the client doesn't care how the app works

derricklamptey
Автор

I thought I'm the only one who can't complete work in expected time. It usually takes 2 to 3 times more time than what I actually thought. Is it normal?

yatik
Автор

While you're right in general, the overhead of change requests - of all things - actually falls on the customer, not on you.

If it's change requests that will take you longer, the need for a re-estimation goes without saying, because they're changing the specification/requirements that were originally agreed upon.

vibovitold