≡ Menu

Avoid Derailing New Product Pipeline by Managing Resource Bandwidth

In the previous articles in this series you learned how to create governance that weeds out low-impact opportunities and to build project plans that are robust to unexpected variation—critical to giving every project an excellent chance of finishing on-time. Once you’ve created this plan, the next step is to schedule your project to move into execution.

I won’t go into all of the reasons here, but did you notice that projects are planned in isolation from the others? Unfortunately, those same projects have to be executed in the real world—a world where multiple projects compete for shared resources.

Every product development organization has a limited or constrained bandwidth—the number of projects it can run at full speed. And letting in more projects than you have the bandwidth for means each of your projects is going to spend time unnecessarily waiting for resources. And that makes every project take longer—much longer.

Click Here to Read the Rest of the Industry Week Article

{ 0 comments… add one }

Leave a Comment