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 C

11 terms
  • Change 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 productivity
  • Change 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 productivity
  • Change scope

    Change scope is a developer productivity concept that helps teams understand change scope in the context of software delivery.

    Developer productivity
  • Coaching

    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 productivity
  • Collaboration effectiveness

    Collaboration effectiveness is a developer productivity concept that helps teams understand collaboration effectiveness in the context of software delivery.

    Developer productivity
  • Completion predictability

    Completion predictability is a developer productivity concept that helps teams understand completion predictability in the context of software delivery.

    Developer productivity
  • Context switching cost

    Context switching cost is a developer productivity concept that helps teams understand context switching cost in the context of software delivery.

    Developer productivity
  • Continuous 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 productivity
  • Coordination cost

    Coordination cost is a developer productivity concept that helps teams understand coordination cost in the context of software delivery.

    Developer productivity
  • Cross-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 productivity
  • Customer 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 productivity