Project Management Operational Problem Solving Implementation & Change Management Strategy & Alignment

Frank Patrick's Focused Performance Business Blog
This Focused Performance Weblog is a "business management blog" containing links and commentary related primarily to organizational effectiveness with a "Theory of Constraints" perspective. TOC is noted for its applications in Project Management and Multi-Project Management (Critical Chain) and Operations Management (Drum-Buffer-Rope), as well as in Marketing, Strategic Planning and Change Management (TOC Thinking Processes). If you are on an archive page, current postings are found here.

Monday, December 20, 2004

How Many Projects? -- In addition to the good comments offered when I last considered this question, here's a quantitative way of looking at PM workload. (Hey, once a left-brained Industrial Engineer, always a left-brained Industrial Engineer.) I'm talking here about short-term projects, about 4-8 weeks or so, involving at least some creative aspects, a bit of relatively simple tech implementations, and sometimes a bit of web development.

Let's assume a weekly review with clients (who do play the role of resource in the approval of creatives and concepts, as well as in some software installations on their systems.) -- 30 minutes a week. Then an internal status and update review so we can put an organized, in-control face on for the client -- another 30 minutes. Some prep and post wandering around and an analysis for each of these -- another hour or so. 2 hours per week per active project. (Keep in mind these are relatively simple projects with only 2 or 3 parallel chains of tasks and about 6-8 resources involved, including clients.)

For new projects, kickoffs (internal and client) -- 45-60 minutes each, with a half hour prep for the client kickoff, and an hour for detailed planning once the scope is refined beyond what the salesperson told us in the internal (assumes projects similar to things we've done before.) Let's say 3 hours per. At 2-3 per week, that's about a day.

Assuming 2-3 projects closing out per week (hopefully balancing out the new ones), about couple hours of lessons learned processing.

On top of project work, let's include about 15% of time for administrivia, collegial discussion, process improvement, and general chaos and necessary goofing off...6 hours per week.

So... 40 hours minus 6 leave 34 for project stuff. 34 minus minus 2 for closeouts leaves 32. 8 hours for new projects leave 24 for active projects. At 2 hours per, we're left with 12 projects per PM, more or less. (Sounds familiar.)

Your mileage will vary.

[Whoops -- Forgot those projects for which the PM takes on occasional task responsibility. Oh well...close enough for jazz.]

posted by Frank - Permanent Link - |

Current Posts (Main Blog Page)

Previous Posts

It is a common delusion that you make things better by talking about them. - Dame Rose Macaulay



What's this XML thingie all about?


View Frank Patrick's LinkedIn profileView Frank Patrick's profile


Google
Web focusedperformance.com



FP's Recommended Reading
- From the FP Bookshelf...

...from My AStore

...and some ideas from Amazon...


Best of the FP Blog Archive
- The really good stuff...

Strategic Thinking and Improvement

Enterprise PM - It Starts with Strategic Interdependence

Face Reality

How to Think With Your Gut

Hugger-Mugger and Helter-Skelter

Managing for Murphy, Satan, and Yourself

More of the Same (Local/Global)

PMI Congress Notes: Using Risk Management for Strategic Advantage

Tell Me How You'll Measure Me and Ah, But What to Measure?

What's in Your Strategy?

Why Can't We All Just Get Along?

Why TOC Works
Project and Multi-Project Management
Critical Chain and (not or) XP

Defining Project Success (But for Whom?)

Down 'n Dirty w/TOC and PM (Part 1 of 5 consecutive posts)

End of Project Review

If Project Management is the Answer, What's the Question?

In Defense of Planning

It Ain't the Tools

Lessons Learned, Revisited

Predicting Uncertain Futures

Project Conflicts

Project Determinism (and other myths)

Project Portfolio Management

Promises, Predictions, and Planning

Removing Bottlenecks - A Core Systems Design Principle

Stage Gates and Critical Chain

Ten Top Sources of Project Failure (The Executive Version)

The Meaning of "Schedule"
Leadership and Change Management
Consistent Leadership Behavior

Invisible Dogma - Perpetuating Paradigms

Nothing But Value

On Assumption Busting

Personal Productivity - An Excuse?

The Psychology of Change Management

FP's Blogroll
- Other weblogs and sites I read


FP's Ryze Page


FP's Technorati Profile
- Click the pic



Who links to FP?


For Your Charitable Consideration:

Give Something Back Foundation

Global Virtual Classroom


FP's Link List
- Selected Sites and Resources

Critical Chain Discussion Group

Lilly Software: Visual DBR

Sciforma PS (Critical Chain Software)

Spherical Angle (Critical Chain Software)

Synchrono Supply Chain Planning Software


FP Blog Archives
- All the oldies, but goodies...

Current
11/08 | 10/08 | 09/08 | 08/08 | 07/08 | 06/08 | 05/08 | 04/08 | 03/08 | 02/08 | 01/08 | 12/07 | 11/07 | 10/07 | 09/07 | 08/07 | 07/07 | 06/07 | 05/07 | 04/07 | 03/07 | 02/07 | 01/07 | 12/06 | 11/06 | 10/06 | 09/06 | 08/06 | 07/06 | 06/06 | 05/06 | 04/06 | 03/06 | 02/06 | 01/06 | 12/05 | 11/05 | 10/05 | 09/05 | 08/05 | 07/05 | 06/05 | 05/05 | 04/05 | 03/05 | 02/05 | 01/05 | 12/04 | 11/04 | 10/04 | 09/04 | 08/04 | 07/04 | 06/04 | 05/04 | 04/04 | 03/04 | 02/04 | 01/04 | 12/03 | 11/03 | 10/03 | 09/03 | 08/03 | 07/03 | 06/03 | 05/03 | 04/03 | 03/03 | 02/03 | 01/03 | 12/02 | 11/02 | 10/02 | 09/02 | 08/02 | 07/02 | 06/02 | 03/02 | 02/02 | 12/01 | 11/01 | 10/01 | 09/01 | 08/01 | 06/01 | 02/01 | 01/01 | 12/00


Powered by Blogger

If you are interested in adding an easily updated weblog to your site, I would suggest you look into the free service provided by Blogger.

Who is FP?
Contact Focused Performance