How software doesn’t work

The December 1995 issue of Byte included an article on Why software doesn’t work which makes several points relevant to group projects.

Capability maturity model

No process in place; ad hoc management is the driving force.
Introduces project planning and tracking, and puts project management in place.
Processes become documented and standardized. Includes requirements management, project planning and project tracking.
Measures project status and feeds that information back to project leaders. Project managers set targets, plan for desired quality and create a process to meet those targets.
Continuing improvement. Key focus areas include defect prevention, technology-change mangement and process-change mangement.

Five easy steps toward disaster

Nine ways to write more reliable software