Seed Home 2 Continuing Improvement
Continuing improvement refers to all aspects of the build. Interestingly - Continuing Improvement is the best place to document work breakdown structure for large-scale collaboration. Large-scale collaborative development process may be captured in this section - and the continuing improvement aspect leverages global collaboration that makes the product the best possible, leading to the potential of Distributed Market Substitution.
The key to improvement is understanding HOW to break down work in a way that does allow mass contribution, and also mass extraction of value. The typical condition in the mainstream is limited contribution, and limited extraction of value: insiders develop, and reap benefits, of the product. The goal of distributive economic development (collaborative design) is quite the opposite: allowing many people to contribute, and allowing many people to extract value. Not relying on scarcity-based business models.
Thus, an open source, collaborative process has a unique business advantage compared to proprietary development, and it is an obvious proposition that equitable economic cannot happen without such open collaboration. This is not controversial from first principles - but many people will argue this in the 'real world.'
Work Breakdown Structures
By understanding standard development processes - and by understanding how disjointed they are - one can propose a an open, collaborative, and transparent paradigm of development that is more efficient, and effective. The key is transparency - a feature of the process that allows for maximum time-binding- ie, building upon past work. In its limit - any new entrant can orient readily and produce developments immediately - pending rapid-learnign documentation based on part libraries, technology modules, and rapid-learning instructionals with quality information architecture.
The practical product required for continuing is mastery of work breakdown structures- which combine open source tools with modified standard processes. Modifications are those for swarm development, under the principle that genius is 1% inspiration, and 99% perspiration.
As such, transparent easy tasks - when piled upon thousands of such easy tasks - combine to genius, as long as these tasks belong to a well-crafted architecture. The genius to making this work is crafting that collaboration architecture.
At the end of the day, the tasks are palatable and rewarding - simple - and unified by a tranformative goal.