6 PI Planning Tips for RTEs

Five years ago, I had the opportunity to participate in the 5 Things I Wish I’d Known before My First PI Planning video series for piplanning.io. Now, I’m reflecting on those tips and sharing them in this blog.

5 Things I Wish I'd Known before My First PI Planning video thumbnail

My journey with SAFe® started with SAFe 2.5. Since then, I’ve enjoyed coaching and mentoring other coaches and leaders. 

As an RTE, I’ve had the chance to facilitate PI planning and coach others to take over that role. While facilitating and coaching, I identified six key tips that created the smoothest PI planning experience for everyone. 

Here they are:

  • Communicate the core message
  • Plan social activities  
  • Be mindful of the start time
  • Prepare, don’t over-prepare
  • Cleary visualize features
  • Take care of basic needs
6 tips to create the smoothest PI planning experience

PI Planning Tip 1: Communicate the Core Message

In the standard agenda, the first half-day of PI planning focuses on the vision, desired deliverables for the PI, features, and architecture.

A screenshot of a standard PI Planning agenda

As the RTE, it’s important to check that the messages from management, including executives, are inspiring and motivational. These speeches should reflect on achievements from the previous PI, address the current state, and provide insight into the organization’s future, specifically how the organization will contribute to building that future in the next PI. 

It’s helpful to review and rehearse the message while supporting effective storytelling. Think of a traditional story arc. Assign you and your customers to a specific role and place in the story. Are you the hero or is the customer the hero while you’re the fairy godmother? What obstacles have you helped your customers overcome? What happy endings have you or your customers created? Sequencing your presentations in this way (if only loosely) will make it easier for your audience to connect with your organization’s purpose.     

One important ingredient of effective storytelling is an executive who knows the customer and the business. They can create a truly captivating story based on real experience in the field. Put yourself in your customer’s shoes and share the story or problem you’re trying to solve from their perspective. This will capture the audience and show your people exactly what they helped create for your customer or will create in the upcoming PI. 

In summary, follow these pointers to create a core message that resonates with teams. 

  • Do a rehearsal beforehand to ensure smooth transitions between segments
  • Support storytelling from one presentation to the next
  • Share customer success stories or examples from the field
  • Invite executives who know the customer and business to present and tell the story

PI Planning Tip 2: Plan Social Activities

Between days one and two, organize an activity like a fox trail or a bowling night. This unstructured time allows people to connect, converse, and build relationships. 

However, it’s important to remember that there is still a second day of PI planning. Do not party too long!

Social activity ideas:  

  • Bowling night
  • Fox trail
  • Escape room 
  • Team dinners featuring local and international foods

If you don’t want to use outside work hours for social time, you can add icebreaker activities to the PI planning agenda. These are short, no more than 10-minute activities that allow people to learn about each other in a different context than work. However, it’s important to note that icebreaker activities don’t work in all cultural contexts, so use discretion when deciding whether or not to include them. 

Here are some quick icebreaker activities:

  • Chat surveys or questions: Use the survey tool that comes with online meeting applications like Google or Zoom to poll the group on things like their favorite candy 
  • Breakout groups/partners to answer a question or share favorites
  • Rapidfire, round robbin question and answer (better in smaller groups): Ask the group a series of “This or that” questions (for example, horror or mystery?)
  • Get to know you Bingo: Give everyone a card with different traits listed on it, like “Owns a dog” or “Has lived abroad;” during breaks, fill out your card with people who have those traits until someone shouts “Bingo” when they get five boxes checked in a row on their board

You can even get creative and pick an activity that matches your PI planning theme

Because virtual PI planning is here to stay, we need to get creative with social activities you can do from afar. Plan time for structured exchanges and organize remote socials.

During Covid, we had “blind dates” during lunch for those who did not want to eat alone. Participants were assigned to another teammate to dine with. This meant they socialized via video call during their lunch from the comfort of their own kitchens.  

Human interaction is important, and PI planning is a great opportunity to get everyone together, even virtually, to create relationships that make collaboration a seamless and enjoyable experience.

PI Planning Tip 3: Be Mindful of Start Time

During the first half day of PI planning, a lot of conversations take place. My SAFe experience is primarily in Europe, particularly Switzerland and Austria, where many people take public transportation to work. Therefore, it’s important to be mindful of the start time. Beginning at 8:00 in the morning might not be suitable as people often travel by train or bus. Starting around 9:00 A.M. allows for a more feasible and effective schedule.

Additionally, it’s common for fatigue to set in during the first half day, potentially due to cultural factors. Different cultures practice different presentation methods. This means some cultures are more tolerant of longer presentations than others. 

To maintain high energy levels, it’s beneficial to keep some talks shorter and initiate breakouts earlier than the proposed agenda

My remote agenda is different than for on-site PI planning. In remote settings, you’ll need more breaks than you have for on-site PI planning. Plan these breaks. Ask your Scrum Masters/Team Coaches to insist on these breaks. I have 15-minute breaks on my agenda every 60 – 75 minutes. During these breaks, I ask people to stand up and leave their desks to walk around, drink water, and do something physical. Remind your Scrum Masters/Team Coaches to do the same in the breakouts.

PI Planning Tip 4: Prepare, Don’t Over-Prepare

When preparing for PI planning, there are two approaches: A) Going in without stories and focusing on known features, or B) Going in with all the stories. 

From my European experience, starting with fewer prepared stories yields better results.

Over-preparing with excessive detail can lead to wasted time. Imagine if each team spends three days preparing stories for their “assigned” features. They might then complain that two days of PI planning is wasted because they now have nothing to do. 

The real waste lies in excessive pre-planning. What happens if the dependencies aren’t properly identified? Or if the business owner asks to reduce scope during PI planning due to a competitor’s actions? Valuable time would be wasted if the work that took time to plan is then descoped or deprioritized. 

The magic of PI planning lies in the opportunity to learn together and collaborate closely.

PI Planning Tip 5: Visualize Features

It’s important to share planning progress while teams are working. Therefore, it’s good practice to visualize features so they’re accessible to the entire organization. 

There are different ways to visualize features based on whether you plan in-person or virtual. 

In-person

To track progress and provide visibility, pin the features on a board using multiple instances and colors. For example, use two blue slips and one gray slip—all pinned over each other. When a team selects a feature, they remove the blue slips and write their names on the gray slip on the board. 

This allows the RTE, Product Manager, or Business Owner to see the progress visually. The more gray slips, the greater the progress. It also helps the team members understand who is working on what and provides an overview. The blue slips can be kept in the team area, pinned to the iteration where the feature is finished, while the other blue slip goes to the ART planning board.

Virtual

You can accomplish this same goal without physical stickies if you’re working in a virtual environment.  

piplanning.io has a color-coding system for the feature stickies. Once a feature has been assigned to a team, it will change color. It will also list the name of the team assigned to the work.  

This is a simple and easy way to see which features have been planned and which haven’t.

A screenshot from piplanning.io's feature stickies
Feature stickies in piplanning.io

PI Planning Tip 6: Take Care of Basic Needs

Maintaining wellbeing is crucial for a productive session. 

As the saying goes, “A hungry bear makes no tricks,” or as participants in a German implementation training described it, “Ohne Mampf kein Kampf,” which translates to “No food, no fight.” 

It’s impossible to concentrate when you’re basic needs aren’t being met. Food, hydration, and bathroom breaks are essential for productive PI planning. 

Designate someone to organize snacks, coffee machines, water, brain food, and other refreshments to ensure everyone stays energized and focused during the sessions.

If you’re virtual, ensure there’s a lunch built into the schedule and breaks during long meetings, especially during the first day. Encourage people to take breaks as needed throughout.

Conclusion

Now that I have dozens of PI plannings under my belt, I can safely say these six tips will provide you with a strong event that provides the right amount of certainty to an uncertain and challenging, but rewarding, experience.

In addition to these tips, here are some SAFe PI planning resources.

piplanning.io is the enterprise application SAFe teams use to facilitate PI Planning
Learn More

About Nikolaos Kaintantzis

Nikolaos Kaintantzis headshot

Nikolaos has always been driven by improving people’s working lives. As a developer, he wrote UIs that made work easier. As an organizational developer, systemic coach, and SPCT, he has added skills to that ambitious endeavor. In partnership with organizations, he develops them so both the organization and all employees benefit.

Connect with Nikolaos on LinkedIn.

My Release Train Engineer Career Path: Transition from RTE to Enterprise Agile Coach

Enterprise Agile Coach

Recently I’ve transitioned from working as a Release Train Engineer (RTE) to an Enterprise Agile Coach. While the RTE career path isn’t always well defined, this has been a rewarding journey personally for my professional development and collectively for growing our organizational capabilities. 

In this blog post, I discuss:

  • Enterprise Agile Coach as a potential development path for RTEs
  • My personal experience nine months into the role and what an Enterprise Agile Coach does in a SAFe® context
  • Learning paths for RTEs and several key insights

Pointing the Release Train Engineer Career Path toward Enterprise Agile Coach

If you look at the SAFe Big Picture (in any configuration), you can quickly identify Agile coaching roles at the team (Scrum Master) and program level (Release Train Engineer). But beyond these roles, the development path isn’t always clear. 

Release Train Engineer

What are the opportunities for Release Train Engineers?

To start, current Release Train Engineers could look at either a Solutions Train Engineer (STE) or a SAFe® Program Consultant (SPC) role. STE is a good progression, but the role only exists in very large enterprises (typically comprising thousands of people) building large solutions (for example, cyber-physical) that require multiple ARTs for development. SPC is a much more common role because it is required at organizations of any size. SPCs play a critical part in implementing SAFe.

But, because SAFe leverages the concept of a dual-operating system (proposed by John Kotter), SPC is often more a set of responsibilities than a specific position. So although many RTEs become certified SPCs to deepen their knowledge of SAFe and increase their own SAFe transformation capabilities, SPC is their next credential but not their next job title.

Enterprise Agile Coach is a common job title for someone who operates at an organizational level and works across organizational boundaries to coach Agile transformations and enable business agility.

These functions make Enterprise Agile Coach an excellent progression for an RTE whose scope has expanded beyond an ART to a broader role in their organization.

Release Train Engineer

What Does an Enterprise Agile Coach Do? My Experience After Nine Months

After working in my current organization for six months, it became clear the role had grown significantly beyond Release Train Engineer. I found myself increasingly leading a SAFe implementation rather than facilitating an ART. I was also managing an Agile delivery function/department with Scrum Masters working on projects operating outside of SAFe. I was promoted to Enterprise Agile Coach to recognize these responsibilities and to make my role clearer across the organization. 

Some of my new Enterprise Agile Coach responsibilities, which are described in SAFe, include:

  • Delivering and provisioning SAFe training across the business
  • Establishing a Lean-Agile Center of Excellence (LACE)
  • Value Stream identification and onboarding new teams onto our ARTs
  • Extending practices to the portfolio level
  • Leading Communities of Practice

RTEs or Scrum Masters may occasionally do (or directly support) some of this work, but there is an essential distinction between leading and contributing to these activities. Additionally, RTEs and Scrum Masters have program and team-level responsibilities that they need the capacity to focus on.

Turquoise banner

My new role also encompasses leading an Agile delivery function/department, which has a wider scope than our current SAFe implementation. Some of our delivery teams work outside our SAFe ARTs on independent projects with fixed durations. Taking a more complete and integrated view of how we deliver our value streams and projects has allowed us to gain a broader range of perspectives and insights, share knowledge, and apply standard practices across teams when beneficial. 

In my experience, the biggest shift from RTE to Enterprise Agile Coach has been learning to influence across organizational boundaries and starting to more fully apply systems thinking (SAFe Principle #2). This includes partnering with departments beyond Product and Technology (like HR) to examine the impact of policies, consider the working environment, and remove systemic impediments. I’ve also gained a better understanding of how value flows across the organization rather than just focusing on optimizing development activities.

One of the challenges that I had not anticipated was the amount of work needed to develop my own personal leadership capabilities. Here are a few of the practices I’ve found beneficial for building a new skill set:

  • Regular professional coaching
  • Developmental practices such as meditation and journaling
  • Leadership self-assessments
  • Enterprise Coaching Mastercamp

Additionally, I’ve continued reading widely to expand my knowledge in some of the disciplines listed in the next section.

Going Beyond Release Train Engineer Skills: My Key Learnings

Enterprise Agile Coaching is shaped by a wide range of disciplines. If you’re interested in moving to Enterprise Agile Coach, some of the areas you might start exploring include:

  • Systems thinking and complexity theory
  • Organizational design
  • Organizational change process
  • Developmental theory
  • Leadership development
  • SPC certification (for advanced knowledge of SAFe)
Release Train Engineer

Some of the ideas and concepts that immediately resonated with my own experience are:

  • Holons – The concept that something is simultaneously a whole in and of itself but also a part of a larger whole (see Arthur Koestler, Ken Wilber, and Michael K. Spayd). This is a useful way to consider individuals, teams, ARTs, and the enterprise. 
  • Fractals – Patterns reoccur at various scales, and this occurs throughout the organization (Mandelbrot).
  • Developmental stage models – Understanding how organizations can be centered in a developmental stage and how their worldviews and values affect the system and culture (see Clare Graves, Don Beck, Ken Wilber, and Frederic Laloux).

Defining Your Release Train Engineer Career Path: More Resources

Enterprise coaching can be very challenging but is also incredibly rewarding. Working more holistically as an Enterprise Agile Coach across the organization has broadened my perspective and understanding of how systems work. 

My previous work as an RTE gave me access to program-level perspectives and insights invaluable to my current role. For any RTE that wants to move into Enterprise Agile Coaching, I recommend seeking out mentors and peers to help support you in your learning journey, adopting a strong growth mindset, and investing in your own development as a leader. 

Turquoise banner to divide the text

From Our Team

Defining your RTE career path can start now with a few small steps. Below are more resources you can use to improve your daily practice as an RTE and clarify your professional development path:

About Tom Boswell

Tom Boswell is an Enterprise Agile Coach

Tom Boswell is an Enterprise Agile Coach and certified SPC and RTE. He has worked at multiple organizations using SAFe, coaching at the team, program, and enterprise levels. He is passionate about lifelong learning, helping others grow, empowering teams, and co-creating more meaningful workplaces. Connect with Tom on LinkedIn or at www.tomboswell.com.