These sources argue that the primary cause of project failure is the widespread neglect of disciplined requirements engineering. The author emphasises that requirements should be viewed as collective wisdom rather than mere documentation, spanning five distinct planes, from strategic intent to technical infrastructure. Central to his philosophy is the 1:10:100 rule, which illustrates how the cost of fixing errors increases exponentially as a project progresses. To manage uncertainty, the author introduces the ARCDI framework, a dynamic chain that tracks the evolution of assumptions into risks, dependencies, or issues. Furthermore, the text distinguishes between project outputs and program benefits, stressing that value is only realized through sustained adoption  ...