Best of Agile — January 2026

1. 1
   Article

   Tech World With Milan·19w

   Software Development Waste

   Waste in software development includes seven classic types identified by the Poppendiecks: partially done work, extra features, relearning, handoffs, delays, context switching, and defects. Modern research expands this to nine categories, adding wrong features, backlog mismanagement, over-engineering, cognitive load, psychological distress, ineffective communication, and AI-generated code waste. Teams can reduce waste through value stream mapping, WIP limits, cross-functional teams, knowledge-sharing practices, rigorous prioritization, and maintaining team morale. The goal is continuous identification and elimination of non-value-adding activities.

   98

   3
2. 2
   Article

   Atomic Spin·18w

   Why I Use HTML for Planning and Spec-Driven Development

   Using HTML for planning documents and specifications offers rich presentation capabilities without extra tooling. The format supports color coding, visual hierarchy, embedded links, and inline UI prototypes that make specs more scannable and actionable. A typical workflow includes defining scope and constraints in a spec section, creating stepwise plans with checkboxes, and maintaining status areas. While HTML requires more authoring effort and produces noisier diffs, the clarity during execution and ability to serve rendered documents through a browser makes it worthwhile for spec-driven development workflows.

   47

   13
3. 3
   Article

   Prince Kumar·20w

   A rare miracle in the Agile universe

   18

   1