RSVP FOR FREE | How Carpe Data Supercharges Roadmap Planning to Deliver Outcomes | Oct 3 @ 9 AM PT

Register

We Need A Portfolio Program Manager Not Just Scrum Masters

A dedicated scrum master is essential for new Agile teams. They are the glue that holds everyone together, ensuring that members adhere to best practices and agreed processes. Much like glue, it will take some time to set. Once everyone understands the makings of a good scrum – from planning to tracking – they are on their way to becoming a well-oiled, self-organizing team.

At this point, the scrum master will no longer require a full-time role because everything works for the most part. So now what? Now, is the time for an up-leveling because

Enabling an Agile engineering team is just the start of an Agile company.

Agile execution via scrum helps build quickly and iteratively. However, it does not automatically enable higher-level alignment of our strategies towards our goals (OKRs). Additionally, it does not enable cross-team cross roadmap collaboration to build synergies or iron out dependencies.

To unlock greater agility, companies need to also practice responsive portfolio program management. Responsive PPM dynamically connects objectives, initiatives, and resources with Agile execution. It also calls for people with the right skills to help move the organization forward.

The Responsive Version of Program and Portfolio Management

Traditional program management focuses on large, cross-functional, and complex programs with many projects. Moreover, the traditional portfolio management focuses on planning, budgeting, and tracking a suite of programs. Both are mostly practiced in large organizations with complex structures.

In small to mid-sized companies, your entire product roadmap is a portfolio.

Many fast-moving companies today may have only a few, if any, large programs. However, they usually have many smaller moving pieces carried out by one or more agile teams. As the agile teams are continuously iterating on product enhancements, there is a missing “glue” to connect them together. This is a recipe for chaos. Promised features go undelivered, support teams are left in the dark, and everyone is sending urgent feature requests filling up the roadmap pipeline.

Solving this takes portfolio management skills.

What Portfolio Program Managers Do

In a nutshell, portfolio program managers ensure the best-desired outcome for an organization over a relevant time period, within the constraints of resources. Scrum master leads scrum cadences while portfolio program managers lead quarterly (or month/ bi-monthly) portfolio roadmap cadence. Their duties can be summed into three key areas:

  1. Quarterly Strategic Planning for Portfolio Allocation
  2. Roadmap Delivery and Trade-Off
  3. Progress Communication

A portfolio program manager works with key stakeholders to create a clear and holistic process for defining priorities responsive to the time-frame. They also lead trade-off discussions between the product areas or teams using portfolio principles to allocate the right resources towards various objectives and initiatives.

Lastly, after deciding the product features and initiatives to undertake, they transition delivery to the agile teams knowing the key-elements of the plan are in place for the team to execute.

Then they track the progress and outcomes, and keep the stakeholders informed.

When changes inevitably happen – for example, when a new high priority feature request comes to the team – portfolio program managers lead roadmap trade-off discussions to minimize the impact on in-flight features while still accommodating new requests in a way that best achieves the company’s desired goals.

In Responsive PPM, We Believe All Factors Are Dynamic

This is precisely where a portfolio program manager comes in to connect the moving pieces in a holistic and dynamic way.

This transition from being a scrum master to a portfolio program manager represents both professional growth for the individual and also a strategically impactful role to every organization.

Responsive PPM

Quarterly Alignment is Replacing Quarterly Planning

Is quarterly planning still relevant in today’s dynamic, fast-changing environment? The answer is a definitive yes, but with a twist. Quarterly planning should not occur only once a quarter, and its deliverable shouldn’t just be a list of projects. Instead, it should be an exercise of continuous alignment on a quarterly horizon.

Some may ask – why do you need a quarterly cadence? With Agile, couldn’t we just continue iterating on the product in sprints? This takes us back to the need for the three separate time horizons of strategy and execution within an organization.

Every organization needs a longer-term, mid-term, and near-term time horizon with their own goals and respective strategies. Quarterly planning focuses on connecting the longer-term vision (e.g. annual) with the mid-term focus (e.g. quarterly), which provides strategic guidance for the next level of iteration (e.g. bi-weekly). Quarterly alignment is for agile leaders to provide context for agile teams.

company quarterly alignment across three time horizons

Here are some of the common challenges for product teams lacking responsive quarterly alignment:

  • Disconnect – Let’s say a product or feature launched from the previous period and hit the market. The resulting business impact may or may not have been anticipated. So, the company must adjust goals and strategies subsequently. However, these strategic changes often won’t reach the team in time or with enough context, resulting in the team continuing to execute strategies from 1-2 quarters ago.
  • Poor allocation – Many companies adopt stable teams or a full-stack team model (think pods or tribes) without adjustment. However, as the business needs change, the previous allocation by team may not support current needs. Some teams end up under water with too many mission critical features while others may not have the same level of delivery pressure, leading them to focus on their locally optimized roadmap.
  • Incongruent UX – Without frequent alignment across teams and functions, silo’d decisions and prioritization happens. Dependencies are exposed. To avoid lengthy delays, teams have to create work arounds. This creates a suboptimal user experience and “products with an org structure”.

Quarterly Planning vs Quarterly Alignment

Traditional quarterly planning aims to address these challenges, but it focuses on the output of a committed list of projects. While there are merits to this deliverable, it does not fit into the fast-changing environment where the list of projects will change through the quarter.

This is why quarterly alignment emerges.

Quarterly alignment is the process of connecting the longer-term vision with sprints and activities responsively via collaboration between executives and leaders and across teams on what we want to achieve and the strategies to achieve them. The outcome is a set of initiatives (aka programs) with defined goals that empower further innovation without misalignment.

How Do You Perform Quarterly Alignment?

Here is a time-tested framework:

  1. Define the top 2-5 goals and target metrics for the upcoming quarter. An OKR framework (Objective and Key Result) is a good way to start.
  2. Brainstorm and prioritize product features, marketing and/or other initiatives to achieve these goals.
  3. Identify gaps and dependencies in achievability and/ or resources (check out how to use MoAR to prioritize).
  4. Iterate between 2 and 3 until a good enough game plan (a list of initiatives enabling your OKR’s) is in place. Learn more about the rock, pebble, and sand method.
  5. Track both work progress and OKR progress to responsively adjust your team’s focus.

Quarterly alignment is not a “build it once and rest forever” exercise. Frequently review (on a bi-weekly or monthly basis) the current trajectory against the desired outcome, and adjust the detailed activities responsively.

Clarity and alignment are critical to the success of any company. Quarterly alignment is a valuable cadence to enable it, giving your company the opportunity to align teams and products against the goals at the OVERALL company level (see the MoAR Method). This way, your teams can innovate and move fast in the same direction.

Strategic Planning Webinar CTA

This site uses cookies. Some of these cookies are essential, while others help us to improve your experience by providing insights into how the site is being used. For more information, please check our Privacy Policy. You can disable or remove cookies in your browser settings at any time. By clicking "Accept" or continuing to use this site, you consent to our use of cookies across the site.