Rwork

Rwork is a term used in project management and software development to describe a metric intended to quantify the amount of work required to complete a task. It aims to provide a more holistic view than traditional time-based estimates by incorporating not only the nominal effort but also factors such as risk and dependencies that can affect delivery.

Definition and components: Rwork typically combines three elements. Required effort represents the baseline work needed under normal conditions. The risk multiplier accounts for uncertainty, technical volatility, and potential rework. Dependency overhead captures the additional work caused by prerequisites, coordination, and blocking tasks. In practice, teams may compute Rwork as a function of these elements, often using simplified scales or calibrated constants.

Calculation and usage: In planning sessions, teams assign values to each component (for example, a baseline effort score, a risk adjustment, and a dependency overhead) and derive an overall Rwork score for the item. This score is used to inform prioritization, sprint planning, and capacity allocation, helping distribute workload more evenly and anticipate potential delays. Rwork can complement other estimates such as story points or hours, offering a cross-check on planning assumptions.

Criticism and variants: Rwork is not a standardized metric and its definitions can vary between organizations. Critics caution that it can introduce subjectivity and calibration challenges, especially across diverse teams. Variants include risk-adjusted effort measures that separate risk from base work, or using Rwork as a paired metric alongside traditional estimates.

See also: Story points, estimation, velocity, project management, agile planning.