MetaScrum Event

MetaScrum Event

Submitted by: Donald Patti
Date Created Date Updated
0

Play Description

Also Known As/Similar To

Product Scrum, PO Sync, Portfolio Sync, Product Manager Sync

Related Patterns

MetaScrum Group, Network of Teams, Cross Team Sync, Scaling the Product Owner

Challenges Addressed

Often, it is hard to align the work being performed by multiple teams with product strategy. This inability to align slows the achievement of product goals and may even prevent those goals from being achieved entirely. MetaScrum events provide an opportunity to align—and realign—the work of multiple teams with product strategy, focusing multiple teams on the most important work, thereby increasing a product’s likelihood of success in the marketplace and speeding the delivery of the most valuable product features.

Definition

(MetaScrum has two meanings: (1) A group of individuals who meet regularly to align the work of agile teams with the product’s (or organization’s) strategy; and (2) An event where a group of individuals aligns the work of agile teams with the product’s or organization’s strategy. This definition describes the event.)

The MetaScrum Event is an event where members of the Product Owner Team meet with stakeholders (e.g., sponsors, subject matter experts, users) to align the work of multiple agile teams with strategy (Scrum Patterns Group MetaScrum). The topics discussed at a MetaScrum may differ depending on whether the MetaScrum is for a single product, a value stream, a product group (portfolio), or an enterprise).

A MetaScrum for a large, complex product requiring multiple teams might cover the following subjects:

  • Progress made toward the product vision, product goals, and release plans since the last MetaScrum.
  • Adjustments to the product vision and product goals * New ideas for the product (additions, changes to the product backlog).
  • Changes to priorities and/or the release plan.
  • Adjustments to the budget.
  • Adjustments team composition.
  • Adjustments to work planned for each team in upcoming Sprint(s) MetaScrum events are typically held at least once per Sprint.

There are different types of MetaScrum events, though they typically all follow the same general pattern:

  • A Product MetaScrum (described above) focuses on product vision, product goals, and product release plans.
  • A Solution/Value Stream MetaScrum focuses on vision, goals and release plans for a large, complex solution or a value stream made up of multiple interconnected products.
  • A Portfolio MetaScrum event focuses on vision, goals and backlog for a portfolio of products (a product group). If needed, it helps to align work across loosely related products.
  • An Executive MetaScrum is a type of MetaScrum for an entire enterprise that focuses on the strategic vision, strategic goals and enterprise backlog, rather than on an individual product.

In Frameworks

In Scrum@Scale, a MetaScrum typically occurs once per Sprint to adjust priorities for product(s) and align the work of teams with these new or adjusted priorities. The agenda described for MetaScrum above (Scrum@Scale Guide).

In SAFe, the MetaScrum is either a Portfolio Sync, Product Manager Sync, or PO Sync depending upon the SAFe configuration the organization has in place. Portfolio Syncs are generally used when an organization has implemented a Portfolio Level (SAFe Portfolio Level); Product Manager Syncs are used when an organization has a Large Solution Level (SAFe Large Solution Level); and PO Syncs are used when an organization has implemented Essential SAFe (SAFe Essential Level).

In LeSS, the LeSS framework places much less emphasis on formal synchronization and much more emphasis on informal techniques for synchronization: “Just Talk” and the use of “Scouts” to exchange information across teams (LeSS Coordination and Integration). In addition, LeSS provides Multi-Team Product Backlog Refinement sessions that help to align the work across multiple teams.

Tags/Keywords

MetaScrum, MetaScrum Event, MetaScrum Group, SAFe, Scrum@Scale, Sync

Challenge Categories

Organizational Vision, Strategic Alignment, Communication and Coordination, Decision-Making, Prioritization, Resource Allocation, Dependencies

Use When…

The MetaScrum Event pattern is best used when:

  • A MetaScrum event is beneficial when the number of people involved in guiding a product, solution, value stream, portfolio or enterprise benefit from building a consensus and the sharing of strategy in an open forum. It helps the individuals involved in Product Ownership understand the thoughts and ideas of their stakeholders and incorporate them into their overall strategy while providing an opportunity for everyone to collaborate and “get on the same page”.

 

Do not use this pattern when:

  • For small products with few stakeholders, it is likely that a MetaScrum is NOT necessary. Instead, the activities can be accomplished organically and informally. Similarly, for products that are NOT a part of a large, complex solution and NOT a part of a portfolio, the other MetaScrum events are unnecessary. Despite this, one common anti-pattern is to create MetaScrums at multiple layers of the organization simply because those layers exist — not because they are helpful or valuable. The result is excessive bureaucracy and a loss of agility. As a result, care should be taken to only create MetaScrums when they are needed.

Play Authors

  • Scrum Patterns Group
  • Jeff Sutherland
  • Jim Coplien

Advantages

When successful, MetaScrum events result in:

  • Better alignment with the organizational vision, the product vision and product goals.
  • Faster delivery of product features most desired by the customer.
  • More rapid achievement of strategic goals and product goals.
  • Less time and effort wasted on low value, unimportant work.
  • Higher levels of satisfaction among stakeholders.
  • Better management and elimination of dependencies.

 

Disadvantages

A MetaScrum requires some upfront preparation and active participation by both stakeholders and Product Owners to be successful. Because of this, a MetaScrum could:

  • Increase the amount of time spent coordinating priorities and work planning across teams unnecessarily.
  • Increase confusion about product goals and the need for cross-team coordination to achieve product goals.
  • Unintentionally discourage the use of more organic techniques, like “Scouts” and “Just Talk”, which require less formal coordination.

 

Additional Notes

Related Links/Resources:

1. (Scrum Patterns Group MetaScrum) Sutherland, Jeff, Coplien, James O., and The Scrum Patterns Group. A Scrum Book: The Spirit of the Game. Pragmatic Bookshelf. 2019.
2. (Scrum@Scale Guide) The Scrum@Scale Guide, Version 2.1 — February 2022. | Scrum@Scale Framework. (2022, April 1). Scrum@Scale Framework. p. 5. https://www.scrumatscale.com/scrum-at-scale-guide-online/#the-hub-of-the-po-cycle
3. (SAFe Portfolio Level) Scaled Agile, Inc. (2024, March 8). Portfolio - Scaled Agile Framework. Scaled Agile Framework. https://scaledagileframework.com/portfolio/
4. (SAFe Large Solution Level) Scaled Agile, Inc. (2023, March 14). Large Solution - Scaled Agile Framework. Scaled Agile Framework. https://scaledagileframework.com/large-solution/
5. (SAFe Essential Level) Scaled Agile, Inc. (2024b, July 15). Essential SAFe - Scaled Agile Framework. Scaled Agile Framework. https://scaledagileframework.com/essential-safe
6. (LeSS Coordination and Integation) Coordination & Integration. (n.d.). Large Scale Scrum (LeSS). https://less.works/less/framework/coordination-and-integration
7. (Multi-Team Product Backlog Refinement) Product Backlog Refinement. (n.d.). Large Scale Scrum (LeSS). https://less.works/less/framework/product-backlog-refinement