<Table> <Tr> <Td> </Td> <Td> This article needs additional citations for verification . Please help improve this article by adding citations to reliable sources . Unsourced material may be challenged and removed . (December 2008) (Learn how and when to remove this template message) </Td> </Tr> </Table> <Tr> <Td> </Td> <Td> This article needs additional citations for verification . Please help improve this article by adding citations to reliable sources . Unsourced material may be challenged and removed . (December 2008) (Learn how and when to remove this template message) </Td> </Tr> <P> The Project Management Triangle (called also the Triple Constraint, Iron Triangle and "Project Triangle") is a model of the constraints of project management . While its origins are unclear, it has been used since at least the 1950s . It contends that: </P> <Ol> <Li> The quality of work is constrained by the project's budget, deadlines and scope (features). </Li> <Li> The project manager can trade between constraints . </Li> <Li> Changes in one constraint necessitate changes in others to compensate or quality will suffer . </Li> </Ol>

What is the iron triangle in project management