Find a term
Make sense of queues, work in progress, forecasting, and team capacity. These concepts explain why a busy team can still struggle to finish work.
Terms beginning with S
15 termsScenario planning
Scenario planning is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningSchedule risk
Schedule risk is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningScope buffer
Scope buffer is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningScope change
Scope change is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningService class
A service class is a category of work with a shared policy for sequencing, WIP treatment, and service expectation. Examples include standard, expedite, fixed-date, and intangible work.
Flow and capacity planningService rate
Service rate is the number of items that a stage or system completes per unit of time. It is a measured outcome of capacity, work mix, policies, and variation, not a fixed property of a person.
Flow and capacity planningSingle-piece flow
Single-piece flow is a process pattern in which work advances individually or in very small units through the value stream. It aims to expose problems early and reduce the waiting created by large batches.
Flow and capacity planningSlack time
Slack time is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningSoftware factory bottleneck
A software factory bottleneck is a person, team, policy, tool, or workflow stage whose effective capacity limits the rate at which the delivery system can complete work. It is identified through sustained evidence of constrained flow and queues.
Flow and capacity planningSoftware factory capacity
Software factory capacity is the amount of work a software delivery system can complete during a defined period under stated conditions. It depends on people, tools, queues, policies, work mix, dependencies, and quality requirements, so it is not a fixed count of engineers multiplied by hours.
Flow and capacity planningSoftware factory work in progress
Software factory work in progress is the unfinished software work currently carried by a delivery system. It includes changes being implemented as well as work waiting for review, testing, approval, deployment, clarification, or another dependency.
Flow and capacity planningSpecialist queue
A specialist queue is a set of items that require capability available from only a small number of people or systems. It is a queue caused by constrained expertise rather than by total team capacity alone.
Flow and capacity planningSprint planning
Sprint planning is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planningStandard item
A standard item is work that follows the ordinary pull order, WIP policy, and service expectation of a workflow. It is distinguished from urgent, fixed-date, or other special classes of service.
Flow and capacity planningSustainable pace
Sustainable pace is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.
Flow and capacity planning