Effective Project Management: Traditional, Agile, Extreme, Sixth Edition

What Is Traditional Project Management?

TPM is firmly rooted in the 1950s and has been around longer than any other approach to project management. In fact, I don't recall it even being called project management in those early days. Process Control System (PCS) was the label I recall. I think the name came from an old IBM program by the same name. In its most elementary form, PCS was nothing other than a sequence of phases such as define, plan, execute, and close with tasks identified within each phase. PCS depended heavily on crude programs that generated Gantt charts based on dependency relationships among tasks that the project manager defines from a functional specification, an earlier form of what we now call a requirements document. Estimates of duration allowed a schedule to be calculated and the critical path identified. These Linear approaches date back to the decades of the 1950s and 1960s. Until the early 1980s, this was the overwhelming choice of software developers. There were few alternatives at that time. Because of its longevity, it has become habit with many developers. Even though there are a number of alternatives today, developers don't give second thoughts to changing. They would rather force-fit the old when the new would be the better choice. Old habits die hard! That is unfortunate, because all of the developer's attempts to modify the Linear approach to accommodate software development projects that don't fit the conditions ultimately lead to failure or ...