Software Project Management 4th Edition By Bob Hughes And Mike Cotterell !free! -
Unlike general project management texts (like PMBOK or PRINCE2 manuals), Hughes and Cotterell recognized early that software is unique. Software doesn't rust, but it decays through entropy. Software has no physical manufacturing phase; the "construction" is the design. Consequently, traditional Gantt charts and critical path analysis needed adaptation. The 4th edition solidifies this adaptation, offering a blend of traditional "plan-driven" methods and modern "change-driven" (Agile) methods.
A standout feature of the Hughes and Cotterell approach is the . This structured methodology provides a repeatable framework for managers: Unlike general project management texts (like PMBOK or
How does the Hughes & Cotterell 4th edition stack up against competitors? They argue that in software
Before "DevOps" made risk monitoring cool, Hughes and Cotterell dedicated significant space to risk identification. They introduce the Risk Framework : For every risk, you must decide to accept, avoid, reduce, or transfer it. They argue that in software, the greatest risk is usually people risk (staff turnover) or requirements risk , not technical failure. not technical failure.
Unlike general project management texts (like PMBOK or PRINCE2 manuals), Hughes and Cotterell recognized early that software is unique. Software doesn't rust, but it decays through entropy. Software has no physical manufacturing phase; the "construction" is the design. Consequently, traditional Gantt charts and critical path analysis needed adaptation. The 4th edition solidifies this adaptation, offering a blend of traditional "plan-driven" methods and modern "change-driven" (Agile) methods.
A standout feature of the Hughes and Cotterell approach is the . This structured methodology provides a repeatable framework for managers:
How does the Hughes & Cotterell 4th edition stack up against competitors?
Before "DevOps" made risk monitoring cool, Hughes and Cotterell dedicated significant space to risk identification. They introduce the Risk Framework : For every risk, you must decide to accept, avoid, reduce, or transfer it. They argue that in software, the greatest risk is usually people risk (staff turnover) or requirements risk , not technical failure.