Hourly fees is in fact or estimate?

Went with customer for daily work on a long-term project when he realized that all deadlines were derailed due to the fact that technical specifications were not, and what was written on the knee is constantly changing.

Now this arrangement is a special person writes descriptions of the pieces of the project, including the prototype layout and operation. If needed, explain on Skype. Further, the contractor assesses the task in hours, the customer accepts this assessment or rejects. In the case that it is satisfied with the preliminary assessment, then the programmer doing the work.

In fact often it turns out that assessed the task, for example 8 hours, and the task took two or three times longer. In this case, anyway, the customer pays within 8 hours.

I would like to know how modern technologies scrum, Agile or others is customary to do everything?

Personally in 1C were all just. come to the facility to the client - signed timesheet time tracking - record the time of arrival, time of departure. Put the signature when you leave. Is the number of hours that you worked. In these conditions, really close to 40 hours a week.

If you evaluate the job but not get in time then you will not be able to close the 40 hours and the customer have questions why the week is so little done, though in fact you worked 8x5.

I wonder how correct it is necessary to organize work on a long-term project in the case of hourly?
Immediately assess the problem or to activate the timer or if you need to screen your client to share and work and assess the problem after the fact?
April 4th 20 at 13:30
2 answers
April 4th 20 at 13:32
I wonder how correct it is necessary to organize work on a long-term project in the case of hourly?


To begin with - go to a real hourly rate.
This is when you first work then you get paid how much worked.
If you first said 8 hours is approved, multiplied by the hourly rate and got a figure which will pay you for the task - where is the hourly pay? it's just another way to justify the fixed price.
So you worked for a fixed payment and work.

For schemes with a fixed payment, to avoid such problems in the first place we must learn to assess the task correctly, as well as to assess the risks (potential inaccuracy) and all that lay in price.

As long as you experience little or evaluation if the problem is quite new - it is a big risk, so I appreciate the task in 8 hours, the customer say it will take 15-20. Then look at the fact how occupied and learning.
If you say 8 and it takes 2-3 times more, and it happens all the time, it is obvious that you greatly underestimate the time estimation.
Why is another question.
you aptly point.
And you gave me a good idea!
Since the customer insists on Fixed Price, you need to estimate in money, not in hours, and then translate it into hours. Then at least you'll be mentally prepared for the task because you know what will get her the money.

And when you estimate in hours, we try to idealize this world - to cut the number of hours. - Alejandra_Abshire commented on April 4th 20 at 13:35
@Alejandra_Abshire, brad: split the money clock = multiply clock on money. - helen16 commented on April 4th 20 at 13:38
April 4th 20 at 13:34
A year ago, began working on the povremenka. You need to take a large task and break it into a number of small. All this is recorded in task Manager. I first started using Asana, and then have a number of clients appeared Bitrix24 and tasks in their projects, am now in front of them.
For example, the task "to impose the new design." Divide it into smaller: layout of individual pages (main, internal), typesetting adaptive on the same pages, etc.

Next, get a time tracker. They, too, are many and different. I liked the Tmetric. Is there a browser extension in all popular crm and task Manager button appears. At least in Google DOX. There is teamwork, billing for time spent (in paid version) - do you see what amount You have already received the money, and what not.

At the beginning of the run the desktop app or the tab with the tracker. Started - by clicking start in the task, and stopped for a Cup of coffee - was put on pause, went back to work - start again.

With this approach, you need to consider that even when fully clear in the head You have to into account the objectives, switching between them, closing the old, the new will take about +20% of the time. 4 hours in fact working 3.5 hours +/-.

Consider the time for goal setting at the beginning it also takes sometimes a long time, but this is work and work is important. To write this in the report or not - look at the customers. Someone adequately perceive Your workflow, and someone will need to cross this time from the report.

To achieve any amount or upon completion of a number of tasks unload report on time. The tracker itself considers the cost. And send to the customer. Only call the task, very specifically, that six months later You looked and were able to explain WHAT You were doing.

Find more questions by tags Organization of the work