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.
Search results
176 termsAcceptance criteria
Acceptance criteria 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 productivityActive work time
Active work time is a developer productivity concept that helps teams understand active work time in the context of software delivery.
Developer productivityActivity measure
Activity measure is a developer productivity concept that helps teams understand activity measure in the context of software delivery.
Developer productivityApprenticeship
Apprenticeship 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 productivityAsync-first work
Async-first work 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 productivityAsynchronous communication
Asynchronous communication 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 productivityBlameless culture
Blameless culture 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 productivityBlameless postmortem
Blameless postmortem 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 productivityBuild feedback time
Build feedback time is the elapsed time between a software change entering a build or validation workflow and the point when useful build or test feedback is available to the team. It includes execution and queueing time when the boundary includes both.
Developer productivityChange adoption
Change adoption 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 productivityChange management
Change management 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 productivityChange scope
Change scope is a developer productivity concept that helps teams understand change scope in the context of software delivery.
Developer productivityCoaching
Coaching 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 productivityCollaboration effectiveness
Collaboration effectiveness is a developer productivity concept that helps teams understand collaboration effectiveness in the context of software delivery.
Developer productivityCompletion predictability
Completion predictability is a developer productivity concept that helps teams understand completion predictability in the context of software delivery.
Developer productivityContext switching cost
Context switching cost is a developer productivity concept that helps teams understand context switching cost in the context of software delivery.
Developer productivityContinuous improvement
Continuous improvement 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 productivityCoordination cost
Coordination cost is a developer productivity concept that helps teams understand coordination cost in the context of software delivery.
Developer productivityCross-functional team
Cross-functional team 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 productivityCustomer feedback loop
Customer feedback loop 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 productivityDecision latency
Decision latency 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 productivityDecision log
Decision log 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 productivityDecision-making
Decision-making 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 productivityDeep work
Deep work 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 productivityDefinition of ready
Definition of ready 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 productivityDelivery confidence
Delivery confidence is a developer productivity concept that helps teams understand delivery confidence in the context of software delivery.
Developer productivityDelivery friction
Delivery friction is avoidable difficulty that slows or complicates the movement of a software change from request to usable result. It can appear as waiting, unclear ownership, repeated handoffs, unreliable tools, difficult environments, or feedback that arrives too late to help.
Developer productivityDelivery slice
Delivery slice 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 productivityDeveloper contribution
Developer contribution is a developer productivity concept that helps teams understand developer contribution in the context of software delivery.
Developer productivityDeveloper documentation
Developer documentation 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 productivityDeveloper effort
Developer effort is a developer productivity concept that helps teams understand developer effort in the context of software delivery.
Developer productivityDeveloper experience
Developer experience is how developers experience the tools, processes, and organizational conditions involved in doing their work. It includes the ease of understanding a system, obtaining feedback, collaborating, and making progress without unnecessary friction.
Developer productivityDeveloper friction
Developer friction is a developer productivity concept that helps teams understand developer friction in the context of software delivery.
Developer productivityDeveloper portal
Developer portal 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 productivityDeveloper productivity
Developer productivity describes how effectively developers turn their time, expertise, and tools into useful software outcomes. It includes the quality and impact of the work as well as the conditions that make sustained progress possible.
Developer productivityDeveloper productivity change size
Change size is a developer productivity concept that helps teams understand change size in the context of software delivery.
Developer productivityDeveloper productivity decision latency
Decision latency is a developer productivity concept that helps teams understand decision latency in the context of software delivery.
Developer productivityDeveloper productivity deep work
Deep work is a developer productivity concept that helps teams understand deep work in the context of software delivery.
Developer productivityDeveloper productivity flow predictability
Flow predictability is a developer productivity concept that helps teams understand flow predictability in the context of software delivery.
Developer productivityDeveloper productivity flow state
Flow state is a developer productivity concept that helps teams understand flow state in the context of software delivery.
Developer productivityDeveloper productivity focus time
Focus time is a developer productivity concept that helps teams understand focus time in the context of software delivery.
Developer productivityDeveloper productivity forecast confidence
Forecast confidence is a developer productivity concept that helps teams understand forecast confidence in the context of software delivery.
Developer productivityDeveloper productivity handoff delay
Handoff delay is a developer productivity concept that helps teams understand handoff delay in the context of software delivery.
Developer productivityDeveloper productivity knowledge sharing
Knowledge sharing is a developer productivity concept that helps teams understand knowledge sharing in the context of software delivery.
Developer productivityDeveloper productivity sustainable pace
Sustainable pace is a developer productivity concept that helps teams understand sustainable pace in the context of software delivery.
Developer productivityDeveloper productivity task switching
Task switching is a developer productivity concept that helps teams understand task switching in the context of software delivery.
Developer productivityDeveloper productivity throughput forecast
Throughput forecast is a developer productivity concept that helps teams understand throughput forecast in the context of software delivery.
Developer productivityDeveloper self-service
Developer self-service is the ability for a software team to complete a supported engineering task through a platform or documented workflow without waiting for another team to perform routine steps. It includes clear ownership, safe defaults, and a recovery path when the standard route does not fit.
Developer productivityDeveloper velocity
Developer velocity is the rate at which a software team turns an idea into a reliable result while preserving a sustainable developer experience. It includes delivery flow, quality, feedback speed, and the conditions that help people do effective work.
Developer productivityDeveloper workload
Developer workload is a developer productivity concept that helps teams understand developer workload in the context of software delivery.
Developer productivity