Search results
Results from the WOW.Com Content Network
Like Goldratt's book The Goal, Critical Chain is written as a novel, not like a project manager's how-to guide. This book is a story about a professor trying to attain his tenure at a university's business school. The plot is used to maintain interest in the subject and provide a real life feel to the book. It provides plenty of real-world ...
The project management triangle. 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. [1] It contends that:
The theory of constraints is an overall management philosophy, introduced by Eliyahu M. Goldratt in his 1984 book titled The Goal, that is geared to help organizations continually achieve their goals. [1] Goldratt adapted the concept to project management with his book Critical Chain, published in 1997.
Eliyahu Moshe Goldratt (March 31, 1947 – June 11, 2011) was an Israeli business management guru. [1] [2] He was the originator of the Optimized Production Technique, the Theory of Constraints (TOC), the Thinking Processes, Drum-Buffer-Rope, Critical Chain Project Management (CCPM) and other TOC derived tools.
The Goal is a management-oriented novel by Eliyahu M. Goldratt, a business consultant known for his theory of constraints, and Jeff Cox, the author of several management-oriented novels. [1] The Goal was originally published in 1984 and has since been revised and republished. [2]
Some project managers feel that the earned value management technique is misleading, because it does not distinguish progress on the project constraint (i.e., on the critical chain) from progress on non-constraints (i.e., on other paths). Event chain methodology can determine the size of the project, feeding, and resource buffers.
Key project management responsibilities include creating clear and attainable project objectives, building the project requirements, and managing the triple constraint (now including more constraints and calling it competing constraints) for projects, which is cost, time, quality and scope for the first three but about three additional ones in ...
Brooks's law is an observation about software project management that "Adding manpower to a late software project makes it later." [1] [2] It was coined by Fred Brooks in his 1975 book The Mythical Man-Month. According to Brooks, under certain conditions, an incremental person when added to a project makes it take more, not less time.