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 termsMob programming
Mob 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 productivityNotification fatigue
Notification fatigue 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 productivityNotification load
Notification load is a developer productivity concept that helps teams understand notification load in the context of software delivery.
Developer productivityNovelty of work
Novelty of work is a developer productivity concept that helps teams understand novelty of work in the context of software delivery.
Developer productivityObjectives and key results
Objectives and key results 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 productivityOutcome orientation
Outcome orientation is a developer productivity concept that helps teams understand outcome orientation in the context of software delivery.
Developer productivityOutcome-oriented roadmap
Outcome-oriented roadmap 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 productivityOuter loop efficiency
Outer loop efficiency is a developer productivity concept that helps teams understand outer loop efficiency in the context of software delivery.
Developer productivityOutput quality
Output quality is a developer productivity concept that helps teams understand output quality in the context of software delivery.
Developer productivityPair programming
Pair 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 productivityPairing time
Pairing time is a developer productivity concept that helps teams understand pairing time in the context of software delivery.
Developer productivityPaved road
Paved road 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 productivityPeer mentoring
Peer 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 productivityPlan accuracy
Plan accuracy is a developer productivity concept that helps teams understand plan accuracy in the context of software delivery.
Developer productivityPlanned work ratio
Planned work ratio is a developer productivity concept that helps teams understand planned work ratio in the context of software delivery.
Developer productivityPlanning poker
Planning poker 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 productivityPlatform adoption
Platform adoption is the extent to which the intended software teams use an internal developer platform or one of its capabilities in their regular work. Adoption includes usage and continued use, but meaningful evaluation also asks whether the platform improves the outcomes it was built to support.
Developer productivityPlatform engineering
Platform engineering is the practice of building and operating internal platforms that give software teams self-service ways to provision, develop, test, deploy, and run applications. It treats the platform as a product for internal developers and aims to reduce unnecessary cognitive load.
Developer productivityPlatform team
Platform 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 productivityPrioritization
Prioritization 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 productivityProduct discovery
Product discovery 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 productivityProduct-engineering collaboration
Product-engineering collaboration 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 productivityProductivity baseline
Productivity baseline is a developer productivity concept that helps teams understand productivity baseline in the context of software delivery.
Developer productivityProductivity dimensions
Productivity dimensions is a developer productivity concept that helps teams understand productivity dimensions in the context of software delivery.
Developer productivityProductivity measurement framework
Productivity measurement framework is a developer productivity concept that helps teams understand productivity measurement framework in the context of software delivery.
Developer productivityProductivity trend
Productivity trend is a developer productivity concept that helps teams understand productivity trend in the context of software delivery.
Developer productivityProductivity variance
Productivity variance is a developer productivity concept that helps teams understand productivity variance in the context of software delivery.
Developer productivityPsychological safety
Psychological safety 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 productivityPull request waiting time
Pull request waiting time is a developer productivity concept that helps teams understand pull request waiting time in the context of software delivery.
Developer productivityRelative estimation
Relative 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 productivityRetrospective action
Retrospective action 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 productivityReview capacity planning
Review capacity planning is the practice of matching expected code review demand with the people, ownership, time, and knowledge needed to provide timely and effective review. It treats review as a delivery capability rather than spare work performed after implementation.
Developer productivityReview iteration count
Review iteration count is a developer productivity concept that helps teams understand review iteration count in the context of software delivery.
Developer productivityReview participation
Review participation is a developer productivity concept that helps teams understand review participation in the context of software delivery.
Developer productivityReview quality
Review quality is a developer productivity concept that helps teams understand review quality in the context of software delivery.
Developer productivityReview responsiveness
Review responsiveness is a developer productivity concept that helps teams understand review responsiveness in the context of software delivery.
Developer productivityRework avoidance
Rework avoidance is a developer productivity concept that helps teams understand rework avoidance in the context of software delivery.
Developer productivityRework burden
Rework burden is a developer productivity concept that helps teams understand rework burden in the context of software delivery.
Developer productivityRoadmap alignment
Roadmap alignment 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 productivityRoot cause analysis
Root cause analysis 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 productivitySelf-service
Self-service 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 productivityService catalog
Service catalog 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 productivityShared understanding
Shared understanding 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 productivitySmall batch
Small batch 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 productivitySoftware factory change size
Software factory change size is the amount of code or delivery scope included in a software change as defined by a chosen unit. It is a context signal that can affect review effort, feedback speed, failure isolation, and queue behavior.
Developer productivitySPACE framework
The SPACE framework is a multidimensional approach to understanding developer productivity across Satisfaction and well-being, Performance, Activity, Communication and collaboration, and Efficiency and flow.
Developer productivityStakeholder alignment
Stakeholder alignment 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 productivityStory points
Story points 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 productivityStream-aligned team
Stream-aligned 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 productivitySynchronous communication
Synchronous 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 productivity