Programmitute

Programmitute is a proposed unit of work in software development intended to describe the smallest schedulable piece of programming activity. It represents a discrete, time-boxed effort that typically lasts several minutes and yields a verifiable increment of software value, such as writing a small function, adding a unit test, or applying a targeted refactor within a controlled environment. The term combines program and minute to emphasize micro-scale tasking within larger delivery workflows.

Origin and scope: The concept has appeared in agile and lean discussions as a theoretical tool for finer-grained estimation and progress monitoring. While not widely standardized, some teams adopt programmitutes to decompose user stories into smaller work units and to calibrate sprint capacity more precisely than traditional story points or hours.

Application and method: Teams define guidelines that specify what qualifies as a programmitute, typical time ranges, and the expected form of the output. Work is tracked by counting completed programmitutes, and velocity is expressed as programmitutes per sprint. This approach aims to surface bottlenecks early and improve forecasting, while remaining compatible with existing metrics.

Advantages and criticisms: Supporters argue that programmitutes promote transparency, reduce estimation bias, and align work with measurable progress. Critics warn that excessive fragmentation can create overhead, distort perceived value, and undermine larger architectural decisions if not used carefully. The method relies on disciplined definitions and consistent execution to be effective.

See also: man-hour, story point, time boxing, task estimation, software metrics.