A reference from Weave

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 R

11 terms
  • Relative 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 productivity
  • Retrospective 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 productivity
  • Review 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 productivity
  • Review iteration count

    Review iteration count is a developer productivity concept that helps teams understand review iteration count in the context of software delivery.

    Developer productivity
  • Review participation

    Review participation is a developer productivity concept that helps teams understand review participation in the context of software delivery.

    Developer productivity
  • Review quality

    Review quality is a developer productivity concept that helps teams understand review quality in the context of software delivery.

    Developer productivity
  • Review responsiveness

    Review responsiveness is a developer productivity concept that helps teams understand review responsiveness in the context of software delivery.

    Developer productivity
  • Rework avoidance

    Rework avoidance is a developer productivity concept that helps teams understand rework avoidance in the context of software delivery.

    Developer productivity
  • Rework burden

    Rework burden is a developer productivity concept that helps teams understand rework burden in the context of software delivery.

    Developer productivity
  • Roadmap 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 productivity
  • Root 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 productivity