XP and Normative Good

Extreme Programming (xp) prescribes a dozen practices that reinforce each other so as to allow teams to make software development decisions. We examine the distribution of responsibilities required for, and means to arrive at, good decisions within this framework.

Process based on delivery.

Technique preserves options.

Responsibility over what one knows.

Consensus based on individual and shared experience.

Norms emerge from good decisions.

Velocity provides a rough measure of this complex social process. Achieving and maintaining the process is more important for long term success than any goal one might set for velocity

DOT strict digraph node [shape=box style=filled] node [fillcolor=bisque] rankdir=LR HERE NODE WHERE /^\[\[/ node [fillcolor=palegreen] LINKS HERE -> NODE HERE WHERE /\[\[S\d+\]\]/ node [fillcolor=lightblue] LINKS HERE -> NODE HERE WHERE /^Subset/ node [fillcolor=bisque] LINKS HERE -> NODE

See Core Agile for a more concise description of the responsibility distribution described here.

See Infected with ROI and Marginal Distinction for alternative perspective on velocity.

See Writer's Burden and Writing with Strangers for similar shifts in another creative work.