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 T
10 termsTask batching
Task batching is a developer productivity concept that helps teams understand task batching in the context of software delivery.
Developer productivityTask completion
Task completion is a developer productivity concept that helps teams understand task completion in the context of software delivery.
Developer productivityTask completion rate
Task completion rate is a developer productivity concept that helps teams understand task completion rate in the context of software delivery.
Developer productivityTask difficulty
Task difficulty is a developer productivity concept that helps teams understand task difficulty in the context of software delivery.
Developer productivityTask switching
Task switching 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 productivityTeam charter
Team charter 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 productivityTeam interaction mode
Team interaction mode 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 productivityTeam productivity
Team productivity is a developer productivity concept that helps teams understand team productivity in the context of software delivery.
Developer productivityTeam Topologies
Team Topologies 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 productivityTime to first change
Time to first change is the elapsed time from a defined starting event, such as joining a team or creating a service, to a developer's first accepted code change in that environment. The start and completion events must be defined for the comparison to be meaningful.
Developer productivity