Categories
- Agile (6)
- Architecture (1)
- art (2)
- Big Data (1)
- books (11)
- Cars (1)
- Change (9)
- common sense (3)
- Contracting (1)
- Cool (1)
- Design (5)
- development (1)
- emotions (3)
- entrepreneurship (2)
- google (1)
- great quotes (2)
- happiness (1)
- innovation (3)
- IT (8)
- IT Architecture (3)
- Knowledge Transfer (2)
- leadership (3)
- Lean (1)
- links (1)
- literature (1)
- lyrics (1)
- management (9)
- Media (1)
- Negotiating (1)
- networks (1)
- people (5)
- Personal Improvement (8)
- planning (5)
- productivity (3)
- Programming (1)
- Project Management (23)
- Projects (1)
- psychology (3)
- Requirements (5)
- Risk (2)
- scrum (2)
- strategy (6)
- struggle (1)
- summer (1)
- teams (5)
- Test Automation (3)
- thinking (5)
- Training (2)
- Travel (1)
- waterfall (4)
Tag Cloud
Agile
Architecture
art
Big Data
books
Cars
Change
common sense
Contracting
Cool
Design
development
emotions
entrepreneurship
google
great quotes
happiness
innovation
IT
IT Architecture
Knowledge Transfer
leadership
Lean
links
management
Media
Negotiating
people
Personal Improvement
planning
productivity
Programming
Project Management
Projects
psychology
Requirements
Risk
scrum
strategy
teams
Test Automation
thinking
Training
Travel
waterfall
Theory of Constraints
Posted by Rich Crowley in productivity, Project Management
I’m doing some reading on the “Theory of Constraints” (TOC) as it applies to project and portfolio management. In a nutshell, the jist of this theory is that every system is constrained by some bottleneck somewhere in the system. In a project, we often consider this to be the critical path.
Too often, we PM’s apply rigour everywhere in our PMBOK-centric approach to managing our projects in an optimal way. TOC stands this approach on its head and suggests that optimizing all subsystems in a system is not the best way to maximize outputs. Instead, if we focused more on fixing the primary bottleneck or constraint, we’d improve our overall system.
TOC suggests that in removing the constraint, we will create a new one somewhere else in the system but that’s ok. We just need to ensure we are able to see this and then re-focus our attention on that constraint.
By constantly identifying where the primary constraint is, we’ll improve our system outputs. Ignoring areas that are not operating in an optimal way is ok so long as they are not the primary constraint.