Date Added: Jan 2009
Solving complex problems with teams of people requires planning. For enterprise software systems, some of the most important planning is highly technical (i.e. planning system architecture). Planning generates artifacts, but planning (as an activity) is much more important, than project management plans, the typical artifacts. By this, the author means that document-driven processes, which focus on paper artifacts, are often ineffective, whereas the real product of any software development project is software. Instead, the author views planning in a broader context, with multiple levels of formality and technical detail. For example, architecting is planning, and so is requirements analysis, design modeling and generating plans. The level of formality should be tied to the document audience's needs, including the longer-term usefulness of the documentation.