The Software Engineering Institute (SEI) Capability Maturity Model (CMM) introduced in “Selecting Software Development Life Cycles” supports activities explained in this section. Software project planning is a key process area for maturity Level 2, the repeatable level. Sizing
Forecasting the "size" of a software system becomes more and more easier as the project progresses. The first time an effort is made, at the front end of the life cycle, little is known except for high-level customer requirements. This is equivalent to requesting a custom-built home,
There are in fact only two ways that tasks and activities are identified for a project: They are part of a pre-existing WBS for a software development life cycle, or they are invented again for a unique development project situation. Either way, customization takes place. We'll
How difficult can it be to identify the work that needs to done for a software project? It's mostly common sense, isn't it? What seems like a straightforward assignment can be riddled with opportunities for poor results. The first thing to deal with is what tasks and activities are.
As explained in "Creating the Work Breakdown Structure" building a product-oriented work breakdown structure (WBS) involves decomposing a large activity (the whole project) into successively smaller activities (top-down approach) until the work is explained in detail to manage
The WBS is the key work product needed to do software project estimating. In many projects, what hurts you the most are not the things that you estimate poorly, but the things that you forget to include at all. In preparation for sizing the work to be done (see "Software Size and
Milestones deserve special mention. A milestone is an important event in a project, generally associated with a major work product or deliverable. They mark passage points in the journey toward completion, and every project should have enough of them, spread evenly
A WBS can be organized in many ways, but it is generally best to arrange the activities around major work products and customer deliverables that will satisfy the customer's requirements. We make a distinction here between work products (anything tangible produced by