Formality is not discipline, process is not skill, and documentation is not understanding. was pointed to [Darrell Norton's Blog].
Formality vs. Discipline
“Formality deals with adherence to established forms or rules. Discipline relates to behavior. Defined methodologies have produced document-heavy processes that are formal, but the discipline to actually implement those processes is often missing.”
Process vs. Skill
“Even though process can support and leverage skill, increasing process does not make up for skill deficiency. The essence of skill isn't what we record on paper; it's defined by proficiency, mastery, virtuosity, savvy, and artistry.”
Documentation vs. Understanding
“Recent studies and experience indicate that a typical requirements document, for example, may provide only 15 to 20 percent of the understanding needed for development. Documents provide an essential starting point, but they fail to convey anywhere near the total understanding required to build a software application. Understanding arises from the interaction of people who have the tacit knowledge—customer to analyst, developer to developer, analyst to developer, developer to tester.”
From Agile Software Development Ecosystems, by Jim Highsmith.
9:38:58 PM 
|
