3 ms·
> So that’s my productivity measure: value-add capacity. The percentage of engineering time we spend on adding value for users and customers. I think this is a
by yellow_lead 2y ago
> So that’s my productivity measure: value-add capacity. The percentage of engineering time we spend on adding value for users and customers.
I think this is an important metric, but it doesn't mean anything if that time is wasted. Imagine the team has no muda, they are spending all their time on value-add, productivity is 100% right? Well no, you still need to succeed at what you're doing, do it well, and in a reasonable time.
This isn't a measure of productivity, it's a measure of time allocation.
- ec109685 2y agoAgreed, I think. Does his framework include a measure of output too by looking at ROI? So if you are able to deliver more effectively, that should increase ROI independently of whether you reduce the amount of muda time.
- ozim 2y agoIf I code up to the specification given by the business, a feature that annoys customers and makes them switch to the competition, is it my problem? For engineering department amount of "value-add" or how many features they deliver (to the specification of course, if the requirements are bad, it is also on business) is the only measure of productivity. Because that is something they can have control over. Reasonable time is implied by delivering amount of value-add. Don't go overboard with the definition, it should be context of engineering, not the whole company. If business cannot come up with good features that time is wasted for the company but engineering is doing what they are paid for.