Find a term
Explore output, effectiveness, and the conditions that help engineers do useful work. Learn to read productivity measures without confusing activity with impact.
Terms beginning with I
7 termsImprovement hypothesis
Improvement hypothesis is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.
Developer productivityInclusive meeting
Inclusive meeting is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.
Developer productivityIndividual productivity
Individual productivity is a developer productivity concept that helps teams understand individual productivity in the context of software delivery.
Developer productivityInner loop efficiency
Inner loop efficiency is a developer productivity concept that helps teams understand inner loop efficiency in the context of software delivery.
Developer productivityInternal developer platform
Internal developer platform is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.
Developer productivityInterruption cost
Interruption cost is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.
Developer productivityInterruption rate
Interruption rate is a developer productivity concept that helps teams understand interruption rate in the context of software delivery.
Developer productivity