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 P

20 terms
  • Pair 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 productivity
  • Pairing time

    Pairing time is a developer productivity concept that helps teams understand pairing time in the context of software delivery.

    Developer productivity
  • Paved 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 productivity
  • Peer 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 productivity
  • Plan accuracy

    Plan accuracy is a developer productivity concept that helps teams understand plan accuracy in the context of software delivery.

    Developer productivity
  • Planned work ratio

    Planned work ratio is a developer productivity concept that helps teams understand planned work ratio in the context of software delivery.

    Developer productivity
  • Planning 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 productivity
  • Platform 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 productivity
  • Platform 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 productivity
  • Platform 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 productivity
  • Prioritization

    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 productivity
  • Product 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 productivity
  • Product-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 productivity
  • Productivity baseline

    Productivity baseline is a developer productivity concept that helps teams understand productivity baseline in the context of software delivery.

    Developer productivity
  • Productivity dimensions

    Productivity dimensions is a developer productivity concept that helps teams understand productivity dimensions in the context of software delivery.

    Developer productivity
  • Productivity measurement framework

    Productivity measurement framework is a developer productivity concept that helps teams understand productivity measurement framework in the context of software delivery.

    Developer productivity
  • Productivity trend

    Productivity trend is a developer productivity concept that helps teams understand productivity trend in the context of software delivery.

    Developer productivity
  • Productivity variance

    Productivity variance is a developer productivity concept that helps teams understand productivity variance in the context of software delivery.

    Developer productivity
  • Psychological 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 productivity
  • Pull 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 productivity