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 termsDiscovery work
Discovery 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 productivityDocumentation as code
Documentation as code 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 productivityEffectiveness measure
Effectiveness measure is a developer productivity concept that helps teams understand effectiveness measure in the context of software delivery.
Developer productivityEfficiency versus effectiveness
Efficiency versus effectiveness is a developer productivity concept that helps teams understand efficiency versus effectiveness in the context of software delivery.
Developer productivityEnablement
Enablement 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 productivityEnablement work
Enablement work is a developer productivity concept that helps teams understand enablement work in the context of software delivery.
Developer productivityEnabling team
Enabling 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 productivityEngineering effectiveness
Engineering effectiveness is the degree to which an engineering team turns time and resources into valuable, reliable outcomes. It considers delivery, quality, collaboration, and developer experience together rather than treating activity as the result.
Developer productivityEngineering handbook
Engineering handbook 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 productivityEngineering output
Engineering output is a developer productivity concept that helps teams understand engineering output in the context of software delivery.
Developer productivityEngineering performance
Engineering performance is a developer productivity concept that helps teams understand engineering performance in the context of software delivery.
Developer productivityEngineering planning
Engineering planning 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 productivityEngineering work mix
Engineering work mix is the distribution of engineering effort or completed work across categories such as features, maintenance, defects, incidents, security, and enablement. It makes competing demands on a software factory visible so capacity and delivery results can be interpreted together.
Developer productivityEngineering-product manager partnership
Engineering-product manager partnership 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 productivityEnsemble programming
Ensemble programming 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 productivityEstimate accuracy
Estimate accuracy is a developer productivity concept that helps teams understand estimate accuracy in the context of software delivery.
Developer productivityEstimation
Estimation 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 productivityEstimation bias
Estimation bias is a developer productivity concept that helps teams understand estimation bias in the context of software delivery.
Developer productivityEstimation uncertainty
Estimation uncertainty is a developer productivity concept that helps teams understand estimation uncertainty in the context of software delivery.
Developer productivityExperiment-driven development
Experiment-driven development 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 productivityExploration work
Exploration work is a developer productivity concept that helps teams understand exploration work in the context of software delivery.
Developer productivityFeature 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 productivityGoal setting
Goal setting 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 productivityGolden path
Golden path 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 productivityHandoff count
Handoff count is a developer productivity concept that helps teams understand handoff count in the context of software delivery.
Developer productivityImprovement 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 productivityKnowledge sharing
Knowledge sharing 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 productivityKnowledge transfer
Knowledge transfer 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 productivityKnowledge work
Knowledge work is a developer productivity concept that helps teams understand knowledge work in the context of software delivery.
Developer productivityLines of code
Lines of code is a count of source lines in a file, change, or codebase. Depending on the tool, the count may include blank lines, comments, generated files, or only executable statements, so the definition must be stated.
Developer productivityMaintenance work
Maintenance work is a developer productivity concept that helps teams understand maintenance work in the context of software delivery.
Developer productivityMaker schedule
Maker schedule 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 productivityMeeting hygiene
Meeting hygiene 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 productivityMeeting load
Meeting load is a developer productivity concept that helps teams understand meeting load in the context of software delivery.
Developer productivityMentoring
Mentoring 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 productivityMentoring contribution
Mentoring contribution is a developer productivity concept that helps teams understand mentoring contribution in the context of software delivery.
Developer productivity