As the Lead Transformation Coach at Aegon Asset Management, Charlene Cuenca presented her story of how AAM began implementing SAFe Agile Architecture out of the gate, the challenges and pitfalls overcome along the way, and the resulting successful Global Architecture Team that exists today.
More often than not, the shift to Lean Portfolio Management (LPM) is not an overnight one. After all, it takes time to pivot from traditional Project Management (PPM) to a lean-agile LPM capability, especially since we want to get the SAFe Essentials established first. But the benefits are clear—better exposing strategy and demand and having a big picture view of capacity and impact on delivery provides better alignment and transparency, which in turn informs better decision making and trade-off discussions at all levels. But where do we begin?
In this presentation, you will learn the context of LPM and view field-tested, practical approaches to get started.
Connecting the Dots Between Goals and Outcomes
In line with the SAFe® Core Values, PI Objectives create a synergistic effect between business and IT, resulting in alignment, transparency, and efficient program execution. This synergy manifests itself during the PI Planning event and continues throughout the PI Cycle as value delivered is demonstarted to the business incrementally. It has the ancillary benefit of increasing the quality of backlog items socialized to teams as part of PI Planning readiness.
Check out Charlene's presentation and gain an appreciation for how Business Value Scoring provides evidence on the amount of synergy acheived.
Program execution is one of the four SAFe® Core Values. To achieve successful program execution, organizations need an efficient system that defines the backlogs of the value to be delivered, the roles that manage them, and the proper timelines for refinement at every level of SAFe. Understanding that we are already doing some form of preparedness today, with our own checklists and timelines being more ad hoc, this article illustrates how to connect the levels to enable ‘continuous Program Increment (PI) readiness.’ This requires contemplating these processes to provide an organized thread aligning them and the people using them to make them more cohesive. To pursue this, we adopt Principle #2, Apply Systems Thinking.