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 F
9 termsFeature work
Feature work is a developer productivity concept that helps teams understand feature work in the context of software delivery.
Developer productivityFeedback coverage
Feedback coverage is a developer productivity concept that helps teams understand feedback coverage in the context of software delivery.
Developer productivityFeedback latency
Feedback latency is a developer productivity concept that helps teams understand feedback latency in the context of software delivery.
Developer productivityFeedback loop
Feedback loop is a developer productivity concept that helps teams understand feedback loop in the context of software delivery.
Developer productivityFeedback quality
Feedback quality is a developer productivity concept that helps teams understand feedback quality in the context of software delivery.
Developer productivityFive whys
Five whys 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 productivityFlow state
Flow state 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 productivityFocus time
Focus time 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 productivityFriction log
Friction log is a developer productivity concept that helps teams understand friction log in the context of software delivery.
Developer productivity