116
edits
Flow metrics: Difference between revisions
Jump to navigation
Jump to search
→Effectiveness: add explicit implication of gaining experience to become faster in releasing
(add hourly rate explainer) |
(→Effectiveness: add explicit implication of gaining experience to become faster in releasing) |
||
| Line 15: | Line 15: | ||
* Lower IDD indicates higher effectiveness. The ultimate goal would be 0 IDD. | * Lower IDD indicates higher effectiveness. The ultimate goal would be 0 IDD. | ||
Because almost all of our work is being done by people on laptops, we calculate the inventory based on the hours invested into a project, times an hourly rate. The hourly is set in advance and can vary per person. The primary determinant of your hourly rate is your experience level, as we generally expect a senior engineer to be more productive than a junior engineer. | Because almost all of our work is being done by people on laptops, we calculate the inventory based on the hours invested into a project, times an hourly rate. The hourly is set in advance and can vary per person. The primary determinant of your hourly rate is your experience level, as we generally expect a senior engineer to be more productive than a junior engineer, and thus their work to lock up greater value while sitting on the shelf. This implicitly means it becomes more important to get your work into production faster, as you gain more experience. | ||
==Reliability== | ==Reliability== | ||