Category: Tips & Tricks

Scrum Master Stories: Resolving Conflict within Agile Team

Posted on
Scrum Master Stories: Resolving Conflict within Agile Team

I’m the scrum master for the marketing team at Scaled Agile. In the time that I’ve been here, we went from one team to two, and now three, adding new roles along the way.

What I find most useful in my everyday work are my conflict resolution skills. Communication, vulnerability, working through challenges—these all take a lot of time and effort. Being able to coach it and stick through it with teams on their journey to innovation is where we as scrum masters have a chance to shine.

Conflict isn’t just about fighting and yelling; it’s about collaborating and understanding different perspectives, so that the team can come up with something nobody’s ever thought of before—and Agile is so much of that, too. 

In a past life on a team I worked with, there were conflicts between people who had been on the team for a long time and people who were newer, but were very advanced in their skills and fields. Figuring out how to collaborate and how to share those ideas without forcing one path or another was really challenging for a team to achieve agility. When we’re experiencing that and struggling to find our place, we often want to avoid having that hard, one-on-one conversation.

So, I did some one-on-one coaching with the people who were struggling and got them to a point where they understood I didn’t want to step in for them; I wanted them to have the confidence to talk to each other and build trust. I coached both of them on what it means to be vulnerable. It’s actually opening up and showing your team that you’re human and that you can collaborate. They were then able to solve the problem themselves and worked together for a long time afterwards very successfully. They started having those conversations more openly—and not just between the two of them but between the whole team and others they worked with regularly.

I love this article about vulnerability and bringing human connection into the workplace. Just remember to lean into conflicts of all shapes and sizes, and recognize that it’s a journey, much like the team formation lifecycle, that cannot be rushed or avoided.

About Lieschen Gargano Quilling

Lieschen Gargano is an Agile coach

Lieschen Gargano is an Agile coach and conflict guru—thanks in part to her master’s degree in conflict resolution. As the scrum master for the marketing team at Scaled Agile, Lieschen loves cultivating new ideas and approaches to Agile to keep things fresh and exciting. She also has a passion for developing best practices for happy teams to deliver value in both development and non-technical environments. Fun fact? “I’m the only person I know of who’s been a scrum master and a scrum half on a rugby team.”

View all posts by Lieschen Gargano Quilling

Share:

Back to: All Blog Posts

Explore more Blog Posts

Next: Your Burning Questions: PI Planning

Read the Blog Post

Your Burning Questions: PI Planning at an Agile Organization

Posted on

At the end of the regular episodes in our biweekly SAFe® Business Agility podcast, we answer questions submitted by listeners. In this post, we feature two on the topic of PI Planning, one of which is especially relevant for anyone working at an Agile organization that has restricted travel to limit exposure to the coronavirus.

What’s the best way to conduct PI planning with remote employees?

PI Planning

For many companies with a remote workforce, especially those with a global presence, conducting PI planning can be a challenge. While face to face is always best, it’s not always possible or financially feasible. There are some things you can do if you’re faced with this dilemma.

First, whenever you have remote team members, whether it’s during PI planning or other work-related activities, it’s important to pick times that work for everyone. This means finding meeting times where overlap may exist between work hours for local team members and work hours for remote team members. It can be difficult, but it’s possible.

When work hours don’t overlap, consider times that are a compromise for everyone. That often means some members will end up working late while others will begin their day earlier than their usual start time. Try to keep the compromise to less than four hours either way. Anything more and team members may not be at their best.

That said, one thing that you shouldn’t compromise on is trying to keep whole teams together. For example, don’t have the scrum master in one location and the product owner in another. Keep them all participating together if possible.

Next, let’s discuss how to accommodate remote team members during the PI planning event. While Scaled Agile is a tool-agnostic company, we do have some Gold partners that offer some very helpful tools. One of them, piplanning.io, has a great tool that runs on multiple different platforms that people can use to share information around PI planning. 

Also, think about how to address other logistical challenges, like how to keep remote team members engaged when the room is noisy or during a breakout session. We’ve found that it’s helpful to assign a room buddy to a remote team member. The room buddy is responsible for making sure that the remote team member has everything they need to be an active participant in the session.

It’s important to remember that preparation will take longer with remote PI planning. There’s a lot to consider and you may have to make some tradeoffs. However you end up solving this challenge, make sure to always be respectful of your team members—it’s one of the core pillars of Lean.

Fast forward more than three years and a move to another company, I’m still part of a number of informal learning networks with many of my colleagues from that organization. Every time we learn something new that we feel would be beneficial to the others in the network, we share it. And we learn more every time we share in these moments.   

In this video,  the teams at Travelport share how they successfully coordinated PI Planning across three different time zones, and the benefits that they realized.

For even more details read this advanced topic – tips on distributed PI Planning.

Why is it important to assign business value during PI Planning and how is it helpful to the business?

One of SAFe’s core values is alignment. . Another is transparency, which is critical in an organization’s execution phase. PI Planning and assigning business value is an important component of that. Assigning business value isn’t necessarily about prioritizing things, changing your directions, or shifting responsibility. It’s simply the business owners telling you what they feel is most important, and aligning around that. The business owners may not understand all of the technical nuances that go into building a product but that’s OK. But they do understand why teams are building the product and why their customers want it. The ability to communicate that to the teams that are doing the development work—whether hardware, software, cyber-physical systems, or a business solution—is paramount.

Assigning business value is symbiotic. And Agile is about bridging the silos between the business and IT. When you have those silos, oftentimes the business floods IT with requests. Getting the business owners to assign that business value is that hard prioritization work, and something IT teams can use to ask, “Do we understand your priorities, are we doing things in the right order, and is this of the highest value to our customer?”

Predictability is another important element and there’s a tool in our PI Planning toolkit called the PI predictability measurement that uses the assignment of business value to measure the predictability. That helps you answer the critical question, “Did we do the things that we said we would?” This is a critical part of why companies use SAFe if they want to improve their predictability.

PI Planning

If you haven’t heard the SAFe Business Agility podcast before or want to listen to new and previous episodes, check it out.

If you’ve got a question for us to answer on air, please send it to podcast@scaledagile.com.

Happy listening!

About Melissa Reeve

Melissa Reeve is the Vice President of Marketing at Scaled Agile

Melissa Reeve is the Vice President of Marketing at Scaled Agile, Inc. In this role, she guides the marketing team, helping people better understand Scaled Agile, the Scaled Agile Framework (SAFe) and its mission. Melissa received her bachelor of arts degree, magna cum laude, from Washington University in St. Louis. She currently resides in Boulder, Colorado with her husband, chickens and dogs.

View all posts by Melissa Reeve

Share:

Back to: All Blog Posts

Explore more Blog Posts

Next: 5 Reasons to Attend the European SAFe Summit

Read the Blog Post

Have Fun During PI Planning – Practicing SAFe

Posted on

PI planning,  a vital component of SAFe® is integral to the Agile process, and the meeting can be an intense experience. Sitting in one big room for two full days, with potentially over 100 team members across the organization, can be taxing. Once the breakout sessions begin, the environment can become stressful for some.

The importance and complexity of the work to be done and the pressure of time can make these sessions challenging. Adding to the stress, there are often many conversations going on at the same time, causing the volume in the room to grow increasingly louder until people are yelling just to talk. All of this adds up to people feeling overstimulated and overwhelmed, causing them to grow weary and disengage. With the high cost and critical nature of these sessions, it’s imperative that organizations keep team members engaged and productive.

Because the stakes are so high, you want to use all the best practices available to you in order to maximize valuable time. Our experience has taught us that making your PI planning events fun can turn the stress of a two-day planning event into excitement about what’s ahead. Setting up a lively environment primes your audience for engagement and creativity.

First, we start all of our PI planning sessions with 10 minutes of gratitude. We take the time to encourage planning members to acknowledge and appreciate other team members. Using a mic runner, we have an open mic and find that once the praise gets started, our 10 minutes goes pretty fast, leaving everyone smiling, primed for positivity and ready to get down to business.

PI Planning

Next, we use a chosen theme and incorporate it into slides, written materials, props in the room, snacks, and even stickers, toys, games, and prizes. If you need ideas for your own theme, do some online research for themed parties. Recently, we used an Oktoberfest theme where team members dressed up in traditional costumes, like lederhosen and dirndls. We passed out beer steins (without beer of course) for drinking, and had snacks including pretzels and mustard (be sure to offer gluten-free snacks too). We put up Oktoberfest flags, props, and background scenes—we even had an Oktoberfest backdrop and created a photo booth that the teams enjoyed using.

I’ve learned through trial and error that themes need to be relevant to the times, relatable to the audience, and provide an environment that people want to experience and be a part of.

For example, it’s not enough to say that your theme is “baseball” without also providing the environment to give people an opportunity to interact with the theme. This includes setting expectations in advance, especially if you are asking people to take risks like wearing costumes or using props in front of their coworkers.

It helps with engag

It helps with engagement if the PI planning event organizers and release train engineers (RTE) serve as models, participating in the theme as a way of making it safe for others. Our RTE wore lederhosen and our CEO and founder wore Bavarian hats during the vision statement portion of PI planning.

PI Planning

Another idea is to include games or gamify aspects of PI Planning. Word Bingo is a fun way to keep people engaged over the two long days. Hand out cards with some common and not-so-common words that are likely to be said (or intentionally said) throughout the planning. You could have a single winner, but even better, everyone can get a prize once their card is complete. Prizes should be simple but fun, like themed socks or small desk toys. Treasure hunts and scavenger hunts are other fun ways to get people working together. Give each team member a list of things to find or do, like visit another team to find program risks and dependencies and determine whether or not they impact the plan being created. This gets teams talking to each other, improving relationships, and finding common goals.

Since we started bringing fun into our PI planning processes, I’ve heard more laughter, I’ve felt the positive energy in the room increase, and I’ve seen teams improve how they work together. People seem more energized and less drained by the end of the event. Contrary to what you might think, incorporating fun doesn’t take up more time and make the sessions last longer. In fact, the sessions are more inclusive, engaging, and productive, with better outcomes and fewer surprises down the road. I encourage you to give it a try.

About Deb Choate

Deb Choate is a scrum master at Scaled Agile

Deb Choate is a scrum master at Scaled Agile with loads of experience leading and supporting successful SAFe transformations, technical teams, and projects. She’s passionate about applying her background in psychology and neuroscience to create high-performing Agile teams, environments, and cultures.

View all posts by Deb Choate

Share:

Back to: All Blog Posts

Explore more Blog Posts

Next: A Framework, Not a Prescription

Read the Blog Post