Dinesh Kashyap

Dinesh Kashyap

Tactical or Strategic PPM

Fundamentally, portfolio management is about strategic execution and maximizing value to the organization through important project investments. Through various processes, leadership teams can determine how well their project investments align to key strategic goals. Optimization techniques can further enhance the value of the portfolio, ensuring that organizations get the biggest bang for their project buck. Nevertheless, some organizations turn to portfolio management to merely help at the tactical level—getting projects done—and are less concerned with using portfolio management for strategic execution. Organizations should be mindful of their portfolio management approach—is it strategic, tactical, or both?

Tactically, portfolio management as a discipline can help organizations execute projects through better portfolio planning which includes: short-term resource capacity management, managing dependencies, and sequencing projects.

1) Resource capacity management from a short-term tactical perspective (less than six months) enables organizations to minimize over-utilization and unnecessary multi-tasking, both of which increase the risk of failed project delivery. By protecting organizational capacity, projects are more likely to have key team members available when needed to accomplish project work. In addition, fewer projects usually means less multi-tasking which is a known killer of project success.

2) Managing dependencies at the portfolio level starts with identifying all the upstream and downstream relationships to each project in the portfolio. More dependencies means more complexity and increases the overall risk to portfolio success. This is not merely a program management function, but is part of portfolio planning because such dependencies can span across the entire portfolio. When organizations understand the dependencies between projects, the portfolio management team (PMT) can make better tactical decisions to ensure that upstream projects do not negatively impact downstream projects.

3) Project sequencing is another part of portfolio planning because it is related to managing dependencies. Some dependencies affect project schedules (finish-to-start, finish to finish, etc.) and in order for these projects to be successful, project sequencing needs to be managed. The PMT should understand these relationships in order to initiate projects at the right time otherwise projects could be launched too soon only to find out that other work needs to be completed first (resulting in delays and likely re-work).

Although project portfolio management (PPM) has been traditionally performed to support strategic execution, some organizations may use a sub-set of the portfolio processes and adopt a more tactical approach to portfolio management. While this may seem less than ideal to seasoned portfolio management practitioners, it still yields benefits for existing projects and programs, and can ensure greater success than if no portfolio processes were utilized.

Tim Washington

Senior Associate at Point B

SHARE THIS POST

LinkedIn
Twitter
Facebook

Related Blog​s

Blogs
Dinesh Kashyap

Top 4 challenges facing CIO’s and IT Leaders in 2019

The arrival of game-changing technologies like mobile apps, social media, cloud computing has brought forth a new standard in the operational & decision-making process for many businesses. The CIO’s and IT Leaders role continues to undergo a transformation that is driving business leaders closer to customer demands and

Read More »
Blogs
Dinesh Kashyap

Strengthen Talent Management With PPM

When people refer to the “war for talent” many discussions center on talent acquisition and try to answer the question “how do we hire the best people?” Although talent acquisition is important, talent development and retention are also very important (you want to keep those great people you hired, correct?).

Read More »
Blogs
Dinesh Kashyap

How to Determine Resource Pool Available for Your Project Portfolio?

So, here is an example of a “back of the envelope” calculation of total project resources bucket at a company that has proven to be extremely robust.
Imagine that there are 250 employees working at the head office. It has been estimated via survey or questionnaires that approximately 30% of their time is spent on project work and 70% on business as usual, i.e. normal daily non-project tasks. Based on that information we can assess the size of the total project resource bucket at the company:

Read More »

©2020 Cloudbyz Inc. All Rights Reserved.