Release Train Engineers (RTEs) play an important role in aligning the organization and maintaining it during PI Planning. In this episode, we talk to Kimberly Lejonö and Carl Starendal, both former RTEs and experienced Agile coaches, who share their tips for RTEs just getting started in their role. And we’ll dive into some questions we hear from RTEs in the field around inspiring change across teams and Agile Release Trains (ARTs) and managing the flow of value.
Click the “Subscribe” button to subscribe to the SAFe Business Agility podcast on Apple Podcasts
Release Train Engineers (RTEs) play an important role in aligning the organization. In this episode, we talk to Kimberly Lejonö and Carl Starendal, both former RTEs and experienced Agile coaches, who share their tips for RTEs just getting started in their role. We’ll also dive into some questions we hear from RTEs in the field around inspiring change across teams and Agile Release Trains (ARTs) and managing the flow of value.
Topics that Kimberly and Carl touch on include:
PI Planning preparation and execution
Maintaining alignment during the PI
Supporting cultural change
Metrics, and what not to measure
Hosted by: Melissa Reeve
Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role, Melissa guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework (SAFe) and its mission.
Tapping into her background working as an RTE, project leader, and scrum master, Kimberly brings a high-energy and curious mindset to affect change in others. She loves connecting with the people around her and unlocking their potential to help organizations move in their desired direction. Connect with Kimberly on LinkedIn.
Guest: Carl Starendal
With a background in game development and a decade of hands-on experience at the center of global Lean-Agile transformations across multiple industries, Carl co-founded We Are Movement, an Agile and Lean advisory team based in Stockholm. A highly regarded trainer, advisor, and facilitator, he is a passionate advocate and resource for organizations throughout all stages of the Agile journey. Carl is recognized internationally as a speaker on leadership, Agile, and product development. Find Carl on LinkedIn.
At the conclusion of Program Increment (PI) Planning, we’re always reminded of something one of our colleagues always says. There’s much to celebrate because we’ve created a set of committed plans. But we first have to complete a retrospective of the PI Planning event (cue groans from everyone in the room) and we “start preparing tomorrow” for the next PI (more groans).
Moreover, the critical path for any PI Planning is the creation of the content, suitably refined and prioritized. Without this, we can’t do any planning! But what does this look like in practice?
This blog post is aimed at coaches who need to think about the content preparation for the next PI. By that we mean SAFe® Program Consultants (SPCs) supporting the Agile Release Train (ART) and Release Train Engineers (RTEs). But more importantly, Product Management (PM) and System Architects (SA) need to create, refine, prioritize, and socialize the content supported by Product Owners (POs) and Business Owners (BOs). We will explore each of these roles in turn during the course of this post.
The traditional siloed hierarchy of organizations can engender a ‘this isn’t my job’ attitude. Yet many people and roles need to work together to create a compelling backlog that delivers economic benefits and satisfies your customers.
The visual model below is a high-level view of the intensity of the preparation activity for each of these roles. It isn’t meant to represent the number of hours. That is, high intensity does not mean 100 percent of your time, we just expect more time spent on preparation while recognizing that there will be other things to be done.
Preparation intensity for specific roles.
You will also notice that there is a significant spike in preparation during the Innovation and Planning (IP) Sprint for PM, BOs, POs, and the Teams. This is when PI Planning happens.
Product Management and System Architect
PM and the SA will follow a similar pattern to each other, as their roles are two sides of the same coin—one focused on the outward market and the other technically oriented. They are going to be collaborating and working closely to make sure their respected needs are met and the right balance of the work is correctly scheduled.
Crafting backlog items for an ART, whether they are Business Features or Enabler Features, follow a pattern of Creating, Refining, Prioritising, and Socialising. While overly simplistic, each step could follow the first four iterations of a PI. In the first half of the PI, expect PM and the SA to be looking to the future. This will include looking at upcoming Epics, decomposing existing Epics, and the ART roadmap and associated Architecture Runway.
A common pattern is to see poorly defined Features with weak benefit hypothesis statements and acceptance criteria. It shouldn’t be overlooked how much effort this takes to do well. This is because the work involved isn’t just writing them down in your Agile Lifecycle Management tooling, but working with BOs, talking to a wider stakeholder cohort, including customers, and reviewing market trends. Improving their own understanding of the value proposition and scope enables people on the ART to more easily deliver against it. Through the PI, their effort tapers as other cohorts take the backlog content and prepare for PI Planning.
Business Owners
BOs are key stakeholders and critical friends of the ART. As such, they gradually experience an increasing demand on their time to support creating backlog content throughout the PI—with the most involvement happening during PI Planning. As a cohort, BOs are available when needed by the likes of PM, and actively participate in the System Demos every iteration. Here, they not only get to see the progress of delivery but give feedback to help PM and the POs inspect and adapt the backlog.
We recommend that prioritization be a ‘little and often’ affair. And as it is a team sport, BOs must attend these sessions (these are the little spikes on the BO line in the model).
Product Owners
In a scaled environment, POs serve both the team and the train. In the initial periods of the PI, as you might expect, the PO has both a team execution focus and needs to support PM with Feature creation and refinement. As the content starts to get in better shape for the upcoming PI Planning, PO involvement increases, but with a shift in focus to Feature elaboration and decomposition into drafting user stories to later socialize with the team.
The Team
Through most of the PI, the team is execution-focused, although on hand for those ad hoc, short whiteboard sessions with PM, SAs, and POs. Larger demands on the team’s time should be scheduled like any other demand on their time—after all, work is work! This will be done through the use of exploration enablers in a future PI, or spikes and innovation activities that occur during the IP iteration. Either way, the outcome is gaining knowledge that reduces the uncertainty of future work.
The team’s involvement, however, peaks during the IP iteration when the POs socialize the upcoming backlog of work—the Features and the draft stories they have created. It is during the preparation for PI Planning that the team takes time to understand what is needed and answer questions that need “I’ll look in the code” to find out.
Release Train Engineer and Scrum Master
Hey wait, you didn’t forget about the RTE and Scrum Master (SM), did you? Surely they are just facilitators, we hear you say, what do they have to do with backlog items? But let’s think about this. As facilitators at the train or team level, they are key advocates for the improvement of flow and value delivery. Therefore, it is not unreasonable to expect them to create improvement items that require effort from the teams during the PI. And we know that anything that requires effort from the teams should be planned accordingly.
The items that the RTE and SM will bring to the table for inclusion will likely come from team retrospectives, the Inspect and Adapt problem-solving workshop, or from insight gained from activities like the SAFe® DevOps course.
Creating Content During PI Planning
During each PI Planning session, PM presents the vision, which highlights the proposed features of the solution, along with any relevant upcoming Milestones. While some may feel that at this point in the proceedings the content creation is over for PM, there is actually still work to do. During the planning, there will likely be scope negotiations and prioritization calls needed as the teams get deeper into understanding and scheduling in their breakout sessions.
Similarly, the BOs have a role in adaptive content creation too. Beyond providing the business context in the briefings, they will work with the team to discuss the needed outcomes from the work. And they’ll support PM and the SAs in adapting the scope from what was originally crafted—because tradeoffs need to be made during planning. Discussions with the teams during the assignment of Business Value could influence what gets produced in the upcoming PI too.
While the POs and the Teams need to sequence and plan their stories to maximize economic results, there will almost certainly be variability of scope that will need to be accommodated as new information emerges. This will involve further elaboration, negotiation, planning, and reworking of the content during PI Planning.
In addition, the model shouldn’t be followed religiously, but used to identify who, when, and by how much focus the different roles on the train need to spend to make this happen. While putting an emphasis on the quality of the backlog items is going to help your ART, it alone won’t fix your delivery problems but will act as a key enabler in doing so.
It is important to give a government health warning at this stage: context is king! While we have given our view on the preparation activities and the intensity, your context will provide a different reflection. In fact, when creating this post, we both had a slightly different approach for prioritization based on our respective experiences. Neither is right or wrong but a reflection on the clients that we have worked with. So please treat the model we have created as a ‘mental model’ and something you can use with your trains to frame a discussion.
The pattern, while broadly accurate, will change in some situations, particularly if you are preparing for a training launch and this is your first PI. Here, the cadence may be condensed and more focused, but this will be guided by the quality of the backlog content you already have.
A final thought and back to our colleague who says that “PI Planning starts tomorrow.” So does PI Execution. There’s no point in making a team committed to the plans that you have created and then not executing on them. Otherwise, what was the point of PI Planning in the first place?
If we’ve piqued your interest, check out this post about changing a feature in the middle of the PI. It’s a question we always get asked when we teach the Implementing SAFe® class.
About Glenn
Glenn Smith is SAFe Program Consultant Trainer (SPCT), SPC, and RTE working for Radtac as a consultant and trainer out of the UK. He is a techie at heart, now with a people and process focus supporting organizations globally to improve how they operate in a Lean-Agile way. You will find him regularly talking at conferences and writing about his experiences to share his knowledge.
Someone asked me the other day why Agile teams don’t plan to full capacity. Think about this scenario: during the last PI, a team on the ART achieved 50 percent of its planned business value. Stakeholders weren’t pleased with that result. When the team held its retrospective to examine its performance, several issues came to light. High turnover and lots of team members shifting between teams prevented them from finding their groove. People were experiencing burnout from moving too quickly while trying to correct quality issues.
As a scrum master, I coach my teams to plan to less than 100-percent capacity (see scenario above). But I understand why that doesn’t always make sense to stakeholders. They worry that it will result in even fewer met commitments. Teams need a way to talk to stakeholders about how they need to plan less and yet somehow deliver more. It’s easy to criticize the stakeholders. Of course they’re going to ask for more—that’s their job! They may not understand why agile teams estimate and how they plan agility. They don’t see the burden that agile planning to maximum capacity places on the team.
We need to shift the stakeholders’ perspective. So, here are five key things I’ve learned about capacity and predictability that could be persuasive input.
1. Agree on what capacity means
In a recent iteration planning meeting, I asked the team to give me a number that represents our capacity. There was general consensus that we should plan to 80 percent capacity. It didn’t take long to realize that we all had different ideas about what it means to allocate 80 percent of our capacity. Is it 8 points per person? Or 80 percent of 8 points? Doesn’t SAFe® tell us somewhere?
SAFe doesn’t prescribe a measure. Whether we agree that our team’s capacity is 45 story points or 200 hours, what matters is that the team agrees to some quantitative measure of their capacity for progress.
2. Balance business needs with team capacity
A little pushing outside our comfort zone is a good thing, and can even be inspirational. Often, it’s uncomfortable to try new things, such as setting goals to do more or work faster than we have before. Yet that discomfort can lead to growth and achievement. Think about athletes getting better by pushing themselves to do things they’ve never done before—run faster, lift heavier, jump higher. As a team, we want to win the championship!
But when we push too much, we experience burnout, high turnover, and a lack of creative problem solving because we’re constantly rushing to meet deadlines. Take the athlete analogy—rest, recovery, and refueling via sleep and nutritious meals are essential to an athlete’s success. Otherwise, they risk injury, burnout, and decreased athletic output. Simply put, we need to help the team find its balance so it can thrive.
3. Find confidence in your understanding of the work
Whether your team is developing software, creating marketing strategies, or negotiating a contract, the amount of time required to complete any given task will vary. New teams and ARTs might take more time as they’re forming and storming. Building a new product could take more time during the early development stages because we don’t know how it will be received by customers.
When estimating the size of work, my team uses several perspectives. We assess work based on three criteria: volume, complexity, and our knowledge about the work. We ask ourselves questions like: Have we done this before? How much space do we reserve for the unknowns? Through conversations, we all gain a better understanding of the work. Our certainty in estimating fuels our confidence that we’re pushing ourselves to achieve excellence without the risk of burnout.
4. Protect space for built-in quality and problem solving
I like to keep a monthly budget for personal finance. I know from experience how unwise it is to spend all the cash I earn! I need to be able to respond to life’s unknowns, so I reserve some income for savings. It’s also smart to invest in the future. Early in my career, it was hard to imagine allocating any of my hard-earned salary for investing. (“I’ll start next year!” I’d tell myself.) But every day that went by was a missed opportunity.
The same concepts apply to teams approaching problem solving and innovation. We need “savings” to respond to life’s inevitable unknowns. Innovation can be applied incrementally, like little investments. When the team is constantly rushing to meet an overwhelming list of iteration goals, it’s like living paycheck to paycheck.
5. Slow down to speed up
As a sailor in the U.S. Navy, I learned the saying, “slow is smooth and smooth is fast.” When we were performing meticulous, potentially dangerous tasks aboard naval ships, time was of the essence, and safety and accuracy were paramount. Go too fast and you risk sloppy performance, decreased accuracy, and an unsafe environment. Conversely, go too slow and you risk the mission. As sailors, we lived by “slow is smooth and smooth is fast” to develop awareness and learn to strike the balance between speed and accuracy.
Agile teams are similar. They need time and space to define and automate their processes and to create the environments and infrastructure to ensure built-in quality. Slowing down this PI helps accelerate the next, and with higher predictability.
As I was writing this post, I spotted a conversation about capacity happening in the SAFe Agilists forum on the SAFe Community Platform (login required). Forums like these are great places to ask questions, share your knowledge, and learn something new. I hope you’ll check them out the next time you’re looking for advice.
About Sam Ervin
Sam is a certified SAFe® 5.0 Program Consultant (SPC) and serves as the scrum master for several teams at Scaled Agile. His recent career highlights include entertaining the crowd as the co-host of the 2019 and 2020 Global SAFe® Summits. A native of Columbia, South Carolina, Sam lives in Denver, CO, where he enjoys CrossFit and Olympic weightlifting.
The SAFe program board, or program dependency board, is a key artifact used in PI Planning and execution. The Agile Release Train (ART) teams and stakeholders used it to align, anticipate risks, and adapt the plan accordingly.
This inspection and adaptation of the plan based on insights from the program dependency board is first-loop learning—making changes in the plan based on what we see.
Deeper learning from the program dependency board
What we rarely see, though, is deeper learning from what the program dependency board shows us. It’s like the good old times where you would see a project manager/PMO working their Microsoft Project Gantt Chart, moving things around, but rarely stopping to ask deeper questions around the base structure of their plans and why they’re based on a waterfall model.
Program dependency boards can drive deeper learning about the structure of our ART and its alignment with the kind of mission/vision we’re pursuing, and the backlog of features we’re working on. If we see too much red yarn on our boards, it isn’t something to be proud of. Yes, we can be proud that we identified the dependency and even more that we were able to massage our PI plan to deal with it in a reasonable way. But too much red yarn means too many dependencies. Too many dependencies mean our Value Stream network isn’t configured well. It means we should probably look at ways to reconfigure the network (meaning restructure teams and maybe even the ART).
When to do this deeper learning
I get it. This sort of learning is hard to pursue in the heat of PI Planning. And all too often when PI Planning is done and we have a workable plan in hand, it’s tempting to just move into execution. Resist the temptation. Let the dust settle, but find the time that makes sense to have a deeper retrospective that is based on the patterns you see on the program board. This can be a good discussion in your Scrum of Scrums or with an extended forum that includes the wider ART leadership.
There’s no need to wait for the next inspection and adapt (I&A). It’s fresh now and outcomes from this retrospective might anyhow require a lot of refinement and consideration before they’re actionable. Start the process early in the PI, so hopefully, you’ll be in a position to reconfigure the network going into the next PI as needed.
A typical pattern is when such a retrospective raises the need to rerun a Value Stream identification (VSI) workshop.
Validating the Value Stream design hypothesis—a key but often skipped step
Speaking of the VSI workshop, one key element in it that many practitioners skip is the validation of your Value Stream design hypothesis. After identifying a development Value Stream, run some water through the pipes—take some work in the form of Features or even higher-level Epics/Themes and explore how they will flow through this Value Stream/ART/Solution ART. If the work flows nicely with a minimal number of dependencies, you found a good setup. If even in this ‘dry run’ you already see you have too many dependencies, time to rework the design!
PI Planning dry run
And yes, what this dry run means is that ideally, even in this early phase, before even launching the ART, you should consider doing a light version of PI Planning with the Value Stream design you have in mind to see that it makes sense. You don’t want to train everybody, spend a serious amount of time on preparing to launch the ART, and then find it’s not a self-sufficient ART or that it’s comprised of teams that aren’t self-sufficient.
Summary
I’ve talked about some recommended SAFe best practices here—some are implicitly mentioned in SAFe, and some complement the formal guidance. The key point I wanted to make is how important is it to aim for the right Value Stream network and to continuously inspect and adapt so that value can easily flow with minimal dependencies and slowdowns. And if your Value Stream network is configured well, everything else becomes much easier.
If you’d like to read more about my SAFe experiences in the trenches, I’ve written an e-book. I’ll also be at the upcoming 2020 Global SAFe Summit on the Agile Marketing panel, at the AgileSparks booth in the Partner Marketplace, and at the SAFe Experts Coaching Station. I look forward to connecting with you.
About Yuval Yeret
Yuval Yeret is the head of AgileSparks (a Scaled Agile Partner) in the United States where he leads enterprise-level Agile implementations. He’s also the steward of The AgileSparks Way and the firm’s SAFe, Flow/Kanban, and Agile Marketing. Yuval is a SAFe Program Consultant Trainer (SPCT5), a Professional Scrum.org Trainer (PST), an internationally recognized Kanban Trainer, a thought leader, recipient of the Lean/Kanban Brickell Key Award, and a frequent speaker at industry conferences.
In this ongoing series, our customers and partners share their stories from the field about working with SAFe® ceremonies and SAFe implementations. This episode features Vikas Kapila, SPCT at Enterprise Agility Consulting, who talks to us about the various patterns he’s seen in PI Planning and the impact they’ve had on organizations’ outcomes.
Click the “Subscribe” button to subscribe to the SAFe Business Agility podcast on Apple Podcasts
Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role, Melissa guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework (SAFe) and its mission.
An SPCT5, since 2015, Vikas is CEO, Curator at Enterprise Agility. He focuses on enabling individuals to transform into a high-performing team and realizing how the sum of the team is greater than the sum of the individuals. With more than 20 years in solutions delivery, consulting, and coaching, Vikas has a proven track record in successfully delivering complex solutions (transformations) to multidisciplinary and multicultural teams. He also excels at fostering partnerships between business and IT, starting with a shared vision to create and deliver solutions that delight customers. Over his career, Vikas has worked with companies such as AIG, Bank of America, Capital One, Mercedes, Walmart, and Unisys among others.
Like many organizations, Planview operates globally, with headquarters in Austin, Texas, and offices in Stockholm and Bangalore. About two years ago, we launched a company-wide initiative to rewire our organization and embrace Agile ways of working—not just in product and R&D, but across every department and team, starting with marketing. We developed three go-to-market (GTM) teams, whose goals and objectives centered around building marketing campaigns to create a pipeline for sales. Each team aligned to a different buyer group, with members from the product, marketing, and sales.
The challenge: integrating international teams in our Agile transformation
Like many organizations, we struggled to align and execute our marketing programs across our international teams, defaulting to “North-America-first efforts” that other regions were then left to replicate. As we built out these new groups, we considered how to best include our five-person team of regionally aligned field and demand marketers in Europe, the Middle East, and Africa (EMEA).
At the beginning of our Agile transformation, the EMEA marketers were often misaligned and disconnected from big-picture plans. The EMEA teams were running different campaigns from those in North America. Before forming cross-functional GTM teams, the EMEA team had to individually meet with the different functions in marketing, product marketing, and other departments. The extra complications of time zones and cultures also made it difficult to get things done and stay on strategy.
With team members feeling disconnected, at Planview we suffered lower-impact campaigns and less-than-ideal demand generation. To succeed in our Agile transformation journey, it was critical to properly align the international team through an integrated Agile program management strategy.
The approach: forming and integrating the EMEA team into Agile program management
While the three GTM teams had dedicated cross-functional members representing demand generation, content strategy, and product marketing, it was clear that assigning an EMEA team member to each of these teams wouldn’t solve the problem. Each EMEA marketer is organized by region and language, not by GTM Agile Release Train (ART), so we needed to develop our own EMEA Agile program that would meet the challenges and achieve the needed international alignment.
Working with our Chief Marketing Officer and other stakeholders, we determined that we would continue to align our EMEA team by region/language. Now that the GTM teams were formed (with each team having all the necessary people to deliver end-to-end value), the EMEA team could meet with each team in the context of the prioritized strategic initiatives. Drawing on our local expertise, we could weigh the campaigns from the three GTM teams against each other to determine which would drive the most pipeline and impact in each region. This structure enabled EMEA marketers to opt into GTM campaigns that were regionally impactful, instead of creating standalone campaigns. This approach has been a success. At our last PI planning event, EMEA progressed from just replicating campaigns into co-planning and co-creating the campaigns that were of local interest and fit.
By including the distributed teams in Agile program management, we achieved better alignment as a global marketing team; gave our EMEA marketers the opportunity to leverage fully supported, regionally impactful campaigns; and ultimately, achieved better results for our demand generation campaigns.
Learning 1: When starting the process of shifting to an Agile approach, there is an advantage in letting the GTM team form, storm, and norm before involving the EMEA team. That delay allows for the EMEA team to finish up previously committed (sales-agreed-upon) deliverables. It gives the team and the sales stakeholders time to observe and see the benefits of Agile GTM teams without feeling that they are not getting the support they were expecting.
The practice: virtual, inclusive PI planning
Our model continues to evolve in a positive way. We’ve now been through five PI planning events and have transitioned from a “one EMEA representative” approach to including our full marketing team in a truly global planning event.
What does a global planning event look like in practice?
When our EMEA team started to participate in PI planning, we had one representative join to understand the process and feed the critical milestones into the team’s plans. We then matured to the full team joining remotely, which meant that we needed to create a system that would enable inclusive planning across continents.
We created a process of “continuous planning.” First, our global team would plan “together,” from Austin and virtually via web conferencing for EMEA. Our EMEA teams would log off during the evenings in their time zones, and the US team would continue to plan with recorded readouts. The next morning, while the US teams were offline, the EMEA teams would listen to the readouts, adapt plans accordingly, and provide their own readouts on changes made once the team was back together during mutual business hours. While tricky at first, this process ensured that everyone was engaged and that all teams’ contributions were heard and considered. Most recently, we’ve conducted fully virtual planning in mutual time zones.
Learning 2: The gradual inclusion in PI planning meant the GTM teams were already well-established and well-versed in the process. The maturity of the teams and the process helped a lot in the inclusion of the international team.
The results: greater alignment, faster time-to-market, better campaigns
The impact of our EMEA Agile program can be broken down into three main categories: alignment, time, and utilization.
The collaboration between the EMEA and GTM teams has created significantly stronger connection and alignment, evidenced by both the improvement in campaign quality and our working practices. Our teams have increased visibility into shared and separate work and developed a better understanding of how decisions impact overarching shared goals.
Our Agile ceremonies, combined with the use of Planview LeanKit, have served as a catalyst and a framework to bring us closer together. Communication is easier, more frequent, and more productive, as everyone is aligned to the same goals and plans and has visibility into each other’s progress, needs, and capacity. The greater team can now make conscious trade-offs based on mutual priorities, which enables the EMEA team to focus on the right things and deemphasize asks that are not aligned to the goals. EMEA marketers feel more involved and have an important seat at the table. That is both motivating and effective.
Learning 3: Ceremonies and visual planning tools are absolutely necessary, but only really benefit teams with the right enablement and coaching. To this day we still meet weekly with our Agile coach to refine our LeanKit board and discuss WIP limits, sizing, retros, etc.
From a time-to-market perspective, we’ve seen substantial improvements. Before aligning EMEA to the GTM teams, there were delays in deploying campaigns because EMEA would “find out” about campaigns rather than being part of them from the beginning. Now, the team can give early input and feedback on how a campaign could be adapted to provide the most impact for EMEA, then roll it out more quickly. As a concrete example, we have reduced the time for campaign tactics to go live from three months to three weeks.
The volume and quality of campaigns and campaign materials has increased significantly as well. In the past, the EMEA team often made do with the materials (especially translated materials) that were available, not the assets that were ideal. There were campaign ideas that we could not realize due to a lack of localized material. Without dedicated resources for EMEA, the team had to share creative and translation services with North American providers, who often needed to prioritize programs led by corporate/North America.
Now that EMEA has full visibility into the North American programs, they know what kind of material is in development.
They give input on what is needed to execute campaigns in global markets and when delivery will happen. That means EMEA campaigns can begin at almost the same time as the North American ones, and their marketers can prepare for when translated assets and other materials will be available.
Overall, by transforming our EMEA Agile program, the region went from running one or two campaigns each PI to running five campaigns per PI. EMEA marketing went from approximately four to six new localized assets/materials per year to 18 – 20. We added three translated, campaign-specific landing pages per language. And, most importantly, we’re beginning to see direct indication of pipeline improvements.
Agile program management can be challenging with international, distributed teams. By integrating our global team members into our planning processes from the beginning of our Agile transformation, we’ve been able to achieve measurable benefits across the marketing organization.
About Verena Bergfors
Verena is the Marketing Director for Planview’s EMEA markets. She’s from Germany but moved to Sweden around 10 years ago and has been with Planview for over four years. Prior to living in Sweden, she worked in Shanghai for seven years where she held positions in marketing and sales. Verena’s true passion is languages and she enjoys working on diverse international teams.
In this ongoing series, our customers and partners share their stories from the field about working with SAFe ceremonies, implementing SAFe, and fostering business agility. In this episode, Phil Gardiner, enterprise Agile coach at SAIC (a Scaled Agile partner) talks to us about his coaching experiences in the public sector, including how “business agility” can be applied in government and some interesting a-ha moments.
Click the “Subscribe” button to subscribe to the SAFe Business Agility podcast on Apple Podcasts
Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role, Melissa guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework (SAFe) and its mission.
Phil Gardiner is on a mission to help organizations transform the way they work. Having served as an internal change agent, an enterprise coach, and a ‘coaches’ coach,’ Phil has enabled large-scale Lean-Agile transformations within the telecom, entertainment, finance, cybersecurity, healthcare, and government markets. His current focus is to enable people within the federal government space achieve greater business agility within their agencies and programs.
In this podcast series, we talk to customers about their field experiences with remote SAFe ceremonies and implementations. In this episode, we talk with Rebecca Davis, SPCT at CVS Health and member of the company’s Agile Transformation leadership team, about fully remote, distributed PI Planning at CVS Health.
Click the “Subscribe” button to subscribe to the SAFe Business Agility podcast on Apple Podcasts
This In this podcast series, we talk to customers about their field experiences with remote SAFe ceremonies and implementations. In this episode, we talk with Rebecca Davis, SPCT at CVS Health and member of the company’s Agile Transformation leadership team, about fully remote, distributed PI Planning at CVS Health.
Visit this link to watch the video referenced in the podcast:
Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role, Melissa guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework (SAFe) and its mission.
Rebecca Davis is an iSPCT and leader within the Agile Transformation Office of CVS Health Digital. She helps the people who do the work become empowered, authentic decision makers, while guiding internal SPCs to mature and excel at leading their individual areas.
Program increment (PI) Planning plays a critical role in ensuring cross-team alignment and collaboration. Typically done as a two-day, in-person event, PI Planning brings teams and leadership together to create program plans based on a shared mission and vision. As our marketing team approached its most recent PI Planning, we faced a challenge: how could we execute a successful PI Planning event in a completely virtual way?
The answer: surprisingly well. In our recent webinar, We Survived Virtual PI Planning, event participants shared how we prepared for virtual PI Planning, what went well, and lessons learned. In this blog post, we take a closer look at how the Planview go-to-market (GTM) ART not only survived virtual PI Planning but pulled it off with flying colors.
Before the event: The importance of preparation
All of the webinar panelists emphasized the importance of preparation. “Preparation always matters for a PI event,” explained Agile Coach Steve Wolfe from Peak Agility. “But it matters even more for a virtual event. We wanted to make sure that we covered every possible item and contingency.”
Steve and I (our part-time RTE) began planning for the virtual event several weeks before it occurred, using a T-minus calendar to ensure conversations started early and occurred often. We first decided on communication platforms, selecting existing enterprise channels Zoom and Slack for ease of use and familiarity. With the standard whiteboards and sticky notes off the table for planning itself, we looked to Planview LeanKit as our visualization tool. Next, we considered timing. Two full days felt long even in person, so we elected to spread the event out over four half-days, in the morning in North America, which ended up being a critical component of the virtual PI planning event’s success.
We developed the event agenda with even greater attention to detail than usual. We consciously limited the number of time people spent just listening, added a dedicated number of inter-and cross-team breakout sessions, and cut back on vision and context content while making it more interactive with an executive Q&A session. In addition, we ran orientation sessions before the virtual PI planning event with leaders, teams, facilitators, and scrum masters to set expectations. We sent out recordings to walk people through the structure of the event and detailed process documentation to explain prep work needed and desired outcomes.
At the team level, leaders like the Director of Product Marketing and GTM Head Brook Appelbaum focused on gaining the vision and context necessary to guide PI planning. “We met with leadership early and often to discuss what was going on with our business and customers,” Brook elaborated. “Now that everyone was distributed, what did it mean for our programs? This gave us direction on how to pause, pivot, or persist with our campaigns and shape our collective understanding of our business going into virtual PI Planning.”
Brook and her peers complemented their meetings with executives, sales, and customer success leaders with a metrics deep dive. “We went through the numbers to see where we were from a pipeline perspective and the details of our programs and campaigns, down to the media, tactics, and channels,” she continued. “It gave us greater insight into what was performing well and what needed to be adjusted.” We also held brainstorming sessions, facilitated by panelist Leyna O’Quinn, content strategist and scrum master. The team talked through their ideas, then compared their inputs to their current backlog items and reprioritized accordingly. This allowed them to bring the most current thinking into PI planning.
Leyna helped the team finish work in progress from its current PI as well, so they could prepare for their final demo and review their backlog. They reviewed metrics, within LeanKit, from the current PI to see what worked and what didn’t, including:
Queues, to reflect each work item’s total lifecycle
Lead time and cycle time, to understand how long it takes for work to flow through the process
Throughput, with information like completed cards per day or week and story points for interaction
Cumulative flow, as a visual representation of work in progress as it flows
According to Leyna, “These visual reports and ceremonies allowed the team to have an open dialog and discuss ways to improve processes, tweak our board, and create a culture of continuous improvement.”
During the event: Synchronous engagement and executive commitment
With their thorough preparation behind them, the GTM ART kicked off its fifth PI Planning event—and first fully virtual event.
It quickly became clear that the four half-day approaches was a winner. Head of EMEA Marketing Verena Bergfors described why it mattered to her team. “When it was a two-day event, we couldn’t participate in the whole thing because of the time difference. We had to listen to recordings from the previous day to try to catch up and provide relevant feedback. With the virtual event, we could read out live with everyone listening and adjust and adapt in real-time. It was the first real PI planning that the EMEA team has been able to fully participate in.”
Chief Marketing Officer Cameron van Orman praised the four-day format as well. “Before we went all virtual, we were talking about flying the whole EMEA team out here for face-to-face planning,” Cameron laughed. “There would have been a real cost to that, not just financial but also time and opportunity cost. When we were forced to do it virtually, we saw the power and impact of synchronously planning together across all of our regions.”
Director of Corporate Marketing Leslie Marcotte echoed these sentiments. For her, the virtual PI Planning event allowed for greater collaboration between her shared services organization and the go-to-market teams. The process made work items, like key milestones and deliverables for shared services teams, much more visible and allowed the groups to identify dependencies, increase collaboration, and foster the right conversations. The cross-team breakout sessions were particularly impactful. “It’s much clearer to me how I connect and how I can engage with different teams across the business,” Leslie said.
One of the unexpected benefits of virtual PI Planning played out during the event. During in-person PI planning, executives often pop in and out of sessions, listening to and steering discussions. On reflection, executives and participants alike agreed that this approach could be intrusive and distracting. At the virtual PI Planning event, leaders like Cameron could listen in the background and chime in when appropriate without changing the dynamic of the conversation. It also offered the opportunity for structured time with executives. Planview CEO Greg Gilmore spent 30 minutes with the virtual team communicating his vision while taking questions to create engagement.
The team’s visualization tool of choice also made a big difference to virtual PI Planning. Agile Coach Steve explained, “LeanKit became essential, enabling us to visualize the whole plan across the entire value stream. Each team had a section to develop their plan during breakouts based on a two-week delivery timeframe. We used colors and cards to quickly visualize the work of each team and connected cards to see dependencies. Boards included links to Zoom breakouts and Slack channels, so from one board, you could get to wherever you needed to go. We used LeanKit before, during, and after the event for everything from readouts to the final confidence vote. It is a powerful tool and a key enabler for pulling off a successful event.”
After the event: Hardening, validation, and continuous improvement
Following the successful conclusion of the four-day virtual PI Planning event, the team focused on validation. “We spent the next week on hardening our plan,” Brook said. “We dedicated time to reviewing and overcommunicating our plans to make sure everyone was on board.” This included readouts in numerous business steering meetings, all the way up to the Board of Directors. The team used its LeanKit boards in those conversations to demonstrate its plans and achieve further alignment.
With their plans validated, the GTM ART went into execution ceremonies and cadences. Immediately after the virtual PI planning event, they hit the ground running with an LPM T-minus calendar. They plan to drive continuous improvement through ongoing communication and collaboration with the business and consistent metrics deep dives that show how they are performing mid-flight, not only at the end of the PI cycle.
Top 5 lessons learned
Prepare thoughtfully and thoroughly. Focus on vision, context, and programs during preparation to create the guardrails that help define plans but resist the urge to go too far into tasks and items before the event.
Create a visual collaboration space. Enterprise-class tooling is critical. Rethink how you can use tools like LeanKit to replace whiteboards and sticky notes and enhance collaboration.
Utilize cross-team breakouts. Every participant in the GTM ART’s virtual PI Planning event found tremendous value in the cross-team breakouts, from tactical benefits to greater empathy for their colleagues.
Engage your executives. An engaged but unobtrusive executive presence demonstrated commitment to the process and the people involved in PI Planning.
Respect your team’s humanness. Virtual PI Planning only worked because its leaders thought hard about the experience. From the four-day structure to frequent breaks to mitigating Zoom fatigue to greater inclusion of global teams, all participants agreed that the event worked well because they were intentional about how it was structured.
“If you’re doing Agile and you’re thinking about doing PI Planning, but you’re hesitant because of the virtual workforce, just do it,” concluded Cameron. “Think about the prep work, visual collaboration, and technology enablers. Have clear outcomes, objectives, and roles. As a business, you can’t wait weeks or months hoping that it will go back to the way it used to be; alignment, shifts, and changes are too important. It may be messy, but there are a lot of things that are better in an all-virtual environment.”
About Emily Peterson
Emily Peterson is a demand-gen strategist for Planview’s Lean & Agile Delivery Solution and serves as a part-time RTE for the Go-To-Market Agile Release Train. She uses her professional experience in Agile marketing to leverage new ways of working across the organization, connecting all parts of the business to the overall goals of the organization.
The world is now full-on remote! That is, as non-essential workers, we’re all currently working from home. At least until the COVID-19 crisis is behind us and some sense of normalcy returns, we are working in front of screens and lenses. This post is for SAFe® Program Consultants (SPCs) who are actively teaching SAFe courses, and for SAFe Release Train Engineers (RTEs) who are facilitating remote Program Increment (PI)
.
As a consultant for Agile Rising (a Scaled Agile partner), I spend a good portion of my time teaching formal courses on Lean-Agile topics and practices.
With the onslaught of the virus, we were all left scrambling to prepare for the inevitability of not just consulting and coaching remotely but teaching too!
We want the very best for our clients and always strive to relentlessly improve every aspect of our performance.
As it turns out, we were reasonably well-prepared pre-crisis, as one of our enterprise clients was 100-percent work from home as a workforce already. In the months leading up to the pandemic, we had already been planning and testing various tools and techniques to convert our traditional physical classrooms into collaborative virtual environments. It’s a tall order, given that technology, while fascinating and progressing at a fast pace, doesn’t provide the robust exuberances of a well-prepared training room.
So, we researched. We learned, tested, and continue to do so. This post is all about providing a current state of what we’ve tried and what’s proven to work well for us. You could undoubtedly find all of this information on your own. For the weary, read on and see how we’re conducting our courses. The configuration that we share in this article is for a basic, low-budget, at-home studio. You can amp this up to the limits of your budget and beyond.
Please note that in a short time, our friends and partners at Scaled Agile, Inc. have done a tremendous job of putting together high-quality remote aids, guidance, and new versions of the various SAFe courses to suit our new reality. In this post, I aim to cover the latent individual instructor enhancements that you may consider to take your training production to the next level. As one of my dearest friends, Luke Hohmann, would say, “Go with Super Awesome.”
Exploring Super Awesome
The first thing we have to discuss is hardware. And software. And process. Sound familiar? What follows is not an in-depth technical article. This non-treatise is all about super-awesome instruction enhancements for regular people. Engineers, prepare to be bored out of your mind.
Replacing body language over the wire is a huge challenge. What we take for granted in the real world, we cannot expect to happen over a Zoom or chat channel. Our students and customers expect the best from us, and as exemplars, we would put in our due diligence to give them the most value.
The first thing that I notice in lots of online courses is that the instructor (and students) do not share their video feeds. As an instructor, this faux pas is particularly egregious as our students learn in part from our body language. We each have our unique style and way of teaching, and our body language, our movements, and expressions lend credence and variety to our instructions. Without it, our students are getting only a portion of what they usually would in a physical classroom.
In my opinion, the best tools available today that many people are using—such as Zoom, WebEx, BlueJeans, and Microsoft Teams—need a better interface to clearly show the instructor along with the materials.
Color and lighting
Did you notice anything about the screenshot that appeared earlier in this post? I naturally have a tan complexion (and I don’t spray tan) but I looked pretty dark in it, right? Well, I didn’t turn on the panel lights, only a portion of my lighting setup, to show how adding a little bit of light can make a big difference in your presentation. I’m not a pro or even a regular consumer of photography, but even I can see the difference.
My research led me to some extremes and also reasonable compromises on light choices. I found that you can get away with simple lamps but may wind up having to change bulbs often to suit the specific nature of your at-home studio. I wanted some flexibility, so I purchased these two LED panel lights. These were US$80 each but I can change the color spectrum and brightness—features I wanted for my setup. As a bonus, they come with a great display and simple controls. This capability allows me to adjust the color of the lights to suit my particular skin type. So far, I am super impressed with these lights compared to the other options that I found in the market at the same price range.
I mounted the two panel lights on the wall flanking my primary camera position. Like when I was two years old, I learned quickly that lights create shadows. So, I used a cheap lamp with an LED bulb (5k or more) as a backdrop light to help reduce shadows on my green screen (more on that in a minute).
Notably, the overhead light on my ceiling fan does me no justice—it merely highlights my male pattern baldness to the point of mediocrity. I cried a little, on the inside, when I first noticed it. Key takeaway: unfiltered light is harmful to your video stream (and your appearance).
So, you should experiment with different lighting and positions of the illumination from at least three angles, preferably no unfiltered light from any direction. Use a sheet of printer paper as a cheap filter if you do not invest in a light that comes with a filter.
Natural light, I have read, is excellent, but you need to be able to create distance between your shot and the light source so that you don’t get beams on your face. I have a window in my home office that I covered with easel paper to filter the direct sunlight coming in from the east in the morning. Trust me; you do not want rays of light on your face. Or in an eyeball. Until the end of the story, at least.
Setting the Scene
Once you get the lighting situation wrestled to submission, it is time to tackle pulling all of your content—PowerPoints, video streams, pictures—together into a meaningful presentation. I chose Open Broadcaster Software (OBS)—it’s open and free—as the programming platform on which to experiment. There are commercial software options that you may find on your own, but OBS has worked for me in live events quite well.
Rather than writing a book here to explain the configuration basics of OBS, I created a quick video. I’m not a pro video editor, so please give me some remedial credits for effort.
The Chroma Key (green screen)
Many video teleconferencing software tools have a virtual green screen feature that allows you to choose pictures or videos for a background. They work ok but can be distracting because the AI doesn’t always frame you correctly in front of the background. And I haven’t found a way in Zoom or Microsoft Teams to adjust overlays or scale with the basic features.
You’ll want to set up a green screen in your studio. Thanks to the COVID-19 pandemic, quality structured green screen products are hard to find. So I had to adapt a solution using a 6×10 foot muslin green screen and some old-fashioned handyman ingenuity.
With just one trip to a home improvement store and my garage, I got the parts I needed to build a retractable screen.
I used 10 feet of electrical conduit wrapped in a three-quarter-inch schedule 40 PVC pipe and taped the muslin on with regular packing tape. The pipe fits over the conduit and makes a functional scroll so that I can roll up the screen when not needed.
Multicamera angles
As an instructor, you may want some options for different scenes. Perhaps you would like to stand up for some of your instruction in front of a marker board or the SAFe Big Picture. In OBS, as we learned earlier, you can configure different scenes to suit your instruction scenario. I have a scene for sitting down and presenting slides. I have a standup scene set up in front of the green screen. Also, I can use my third camera (a GoPro Hero4) for a wide shot in front of the open wall in my office where I can place the Big Picture, Implementation Roadmap, marker board, etc.
Depending on what material and desired instruction format you prefer, you’ll want to choose an appropriate scene based on your preferences. The goal is to replicate physical interface benefits while minimizing the negatives and enhancing the presentation and instruction quality with virtual capabilities.
I chose the ~US$200 Canon R800 because of its ability to zoom optically/digitally for scene adjustments. I can set the camera up on a tripod in different scenes and zoom to frame the shot correctly. If you choose a non-webcam-based device, you will need a capture card like the AV.io HD. This expensive tool may be avoided by only using your built-in webcam along with an aftermarket webcam (or two or three) that connects via a USB interface.
Sounds of home, at work
Kids screaming in the background. The neighbor is cutting the grass. We’ve all been there, or at least I have.
I love my iMac and MacBook Pro, but the built-in microphones quickly lose effectiveness. Now, imagine me speaking while typing, and you also get to listen to the clickety-click of my keyboard. In essence, I’m forcing my students to suffer from ‘keyboard-mic-itis.’
Give the world a break and invest in a decent aftermarket USB microphone. After a fair amount of research, I chose a kit that comes with the boom and all the accessories to get great, configurable sound.
Of course, the tips and suggestions I’ve included in this post are what work for me. To see what others are doing, check out the Remote SAFe Training forum on the SAFe Community Platform.
Happy teaching!
About Marshall Guillory
Marshall Guillory is director, professional services and government practice at Agile Rising, and a Scaled Agile SPCT Candidate. He has over 25 years of business experience in software development, information technology, product management, and government fields and sectors. For the past 10+ years, he’s focused on leading digital and organizational transformations.