Everyone reading this is aware of the parallels between writing software and doing legal documents.  As a text creating and handling exercise, software is considerably more demanding than law.  So developers have developed techniques and tools for managing the complexity.  Those techniques are transferrable into the legal domain, sometimes with a bit of adaptation.

This post focuses on a higher level, on an approach to managing the effort of development. 

A “scrum” is a piece of an “agile” development effort.  Agile draws on “extreme programming” thinking developed by Ward Cunningham, a friend of the site.

Agile is part of “lean” start up and related to “lean” manufacturing.  (Anyone who is out there and has read the book, please let me know if “Lean Forward” leans in the same direction.)  

All these respond to the fact that software development (and starting up a company) are non-deterministic.  Planning is essential but plans are soon worthless.  (Eisenhower put it more starkly.)  So, one should do the productive part (planning) rapidly and dispose of the worthless part (plans) often. (Can someone contrast Jack Welch’s complaint that when he took over GE there was lots of planning but no plans.)

The focus shifts from a paradigm of correct thought (orthodoxy) to one of thinking.

Even thinking can be aided by a methodology, especially group thinking that hopes to escape group thought.  In another domain that might be Buddhism. In software it’s a scrum.  This scrum of an idea counts as a post.