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 S
10 termsSelf-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