Project portfolio
A project portfolio is the full set of a firm's live engagements, seen together rather than one at a time. The portfolio view answers questions no single project can: where people are concentrated, which work is drifting, and whether the total committed exceeds what the firm has.
Every project reviewed alone looks manageable. That is the reason portfolios exist.
Three things appear only at this level. Over-commitment, where the sum of reasonable plans exceeds the team. Concentration, where one person appears on most of the list. Drift, where a handful of projects have quietly stopped moving and nobody had a reason to open them.
The last one is the most common and the least noticed. A project nobody has touched in six weeks raises no alarm, because raising an alarm is somebody's job and that somebody is busy with the projects that are moving.
A portfolio view earns its place by surfacing the quiet ones. That is a different job from reporting on the active ones, and a view built only from progress updates will never do it, because a stalled project produces no updates to report.
Silence needs a definition before a system can find it. Days since anything changed, or since anyone met the client, both work. What matters is that some measure of nothing-happening exists, because otherwise a stalled project simply stays off every list until somebody remembers it.
Where this shows up in PeopleMuster
PeopleMuster lists projects with status, priority, scores and resource counts, and warns when a project has had no meeting for longer than a configurable number of days.
Questions people ask
How often should a portfolio be reviewed?
Often enough that drift is caught within weeks rather than quarters. Monthly suits most firms, with a quick weekly scan of what has gone quiet.
What is the first thing to look at?
Whatever has stopped moving. Active projects generate their own attention. Stalled ones generate none, which is precisely why they need a view that looks for silence.
Should internal projects be in the portfolio?
Yes, if they consume real hours. Leaving them out makes the portfolio look smaller than the demand on the team actually is.