Remote Agile Tips: Transitioning your workplace and teams
For a lot of people, 2020 isn’t quite going as expected.
Maybe you’ve had a conference or two cancelled (like the Atlassian summit 😭). Perhaps your big team planning event is on the backburner. Or maybe your entire workforce has been told to work from home until further notice.
Amazon has stopped all non-essential travel and a number of big tech companies have encouraged employees to work from home, including Apple, Google, Microsoft, Twitter, Facebook, and HP (in some or all regions).
You think you’re disruptive? Well, clearly you haven’t met COVID-19!
The new pandemic has shaken things up. Record numbers of organizations are looking for ways to quickly adapt and transition their teams to working remote. It’s a huge challenge when you consider that agile is typically designed for face-to-face interaction - especially critical events like quarterly PI Planning.
We’ve put together some thoughts to help you quickly transition your team to distributed agile, based on our own experiences and working with big organizations who have been working with remote team members for awhile now. First thing’s first...
1. Don’t panic (about distributed agile)
We’re not qualified to tell you if you should panic about the pandemic (seriously though… you don’t need that much toilet paper). But we are qualified to tell you that a remote workforce isn’t as scary as it sounds. You’re going to be just fine.
Organizations like yours have been doing their thing with a distributed agile team for years now. One of our customers has a large distributed team and only does remote PI Planning. It's possible to pull it off.
2. Lead people on how to work from home
Some of the people on your team probably haven’t worked from home before. At least, not for an extended period. So, offer guidance on what’s expected and how they can make the most from working at home.
You know... like business up top, sweatpants on the bottom, and no one on the conference call will be any wiser.
But seriously, it’s a good idea to share guidance like:
- What equipment they’ll need
- A list of software and apps to download (with licensing info)
- Where to find information and access files (a single source of truth is best at all times, but especially when things are already a bit overwhelming)
- How to communicate virtually
- Ideal environments for focus and productivity
- How to block out noise and distractions
- Expected work hours
- How to switch off and take breaks
But a little guidance will go a long way in helping everyone feel more “at home” with the new work situation.
3. Encourage information sharing
You might already have a distributed agile team who are experienced with working remote. So, encourage the experienced remote workers to champion the practice and lead others.
Create a Slack channel or other environment dedicated to discussions about working from home, so that people can share tips and experiences, and ask questions. At Easy Agile, we've created a #remote channel to share our setups.
4. Get the right tools
If your team is working remote for the first time, they might not have all the bits and pieces they need at home to do their job, attend meetings, or show up properly to a remote PI Planning event.
Depending on their role, they may need:
- Computer - A desktop and monitor setup or a laptop with sufficient processing power for everyday tasks
- Meeting equipment - Webcam, headphones, and working mic
- Your preferred communication apps - Slack, Zoom, Google hangouts, Skype, or Microsoft Teams
- Security measures - Password managers, VPNs, and antivirus software
- Your project management tool - Jira, Trello, Asana, or Smartsheet
- Easy Agile Programs for PI Planning in Jira
5. Look at this as a pilot
More people want to work from home and it makes a lot of sense for businesses to encourage this new way of working. It can save a lot of money (one estimate suggests $10,000 per person per year) when teams stay at home. And you can save hundreds of thousands per PI Planning session when you don’t have to pay for flights, accommodation, and event space for a team of up to 100.
The remote work trend isn’t going away - even after the pandemic dies down. So, look at this as an opportunity to try distributed agile if you haven’t already. You could find it’s a better, more cost-effective way for you to get stuff done and give your employees what they want.
6.Trust your people
Nobody likes to feel watched while they’re working 👀 But especially not while they’re working from home. At home, your employees will probably:
- Face more distractions (like kids!)
- Step away to put a load of washing on
- Grab a coffee (and probably a few other things 😋🍛🍫🧁) from the kitchen
In between all of that, you need to trust that they’ll get their job done, do their best, and be productive - even if it happens outside of regular business hours.
Fortunately, if you’re agile, you likely have built a culture of trust already. So, keep up with regular communication, virtual standups, and transparency. This should be enough to monitor progress and keep your people accountable without micromanaging
7. Stay social
Even if you can’t meet face-to-face, create opportunities for your teams to come together virtually, socialise, and chat. Set up a non-work Slack channel, do regular video calls, and talk about more than just work. People, relationships, and connectedness matter even more when you can’t be in the same room together.
8. Get better at risk management
When all of this blows over (and it will), you’ll come out a much stronger organization than before. If a single team member, a whole team, or your entire organization need to work remote in the future, you’ll be able to easily switch gears with minimal disruption.
Use this opportunity to uncover risks you might not have considered previously. Ask questions like:
- What if half of us get sick and can’t work for a few weeks?
- What backup options are in place for our internet connection, files, and communications?
- What if our building is suddenly inaccessible?
- Become more aware of potential risks to your company so you can be better prepared in the future.
9. Look on the bright side
While a pandemic isn’t an ideal scenario, it’s okay to look for the positives, like:
- Your teams may find they love working from home
- Some distributed agile teams will find they’re actually more productive
- You'll get greater work/life balance
- No commutes
- More quality time with family
- Reduced emissions from cars and planes
- Quieter roads with fewer traffic jams and accidents
And maybe… just maybe… some of these changes will stick around for the better 🤞
Related Articles
WorkflowOnline user story mapping for remote teams
Get ready for remote user story mapping.
Whether you've done user story mapping before (in person) or you're new to user story mapping, there's a very good chance that you'll need to do remote user story mapping for the first time in 2020.
Even before the pandemic, 4.7 million people in the US worked remote, and an estimated 31% of US workers employed in March 2020 were working from home by April 2020.
And after lockdown ends, it’s likely we’ll see permanent changes to the way we work. Surveys show that 80% of employees are keen to work from home at least some of the time. Plus, more organizations are realizing that offering flexible, remote work options can lead to better work-life balance for employees, lower overheads, lower environmental impacts, and improved productivity....which is all to say that remote user story mapping is about to be the norm.
So, what do you need to know before you run your first online user story mapping event? Let's go through 8 things you should consider for successful remote user story mapping.
1. Get the basics right
First thing's first: you need your basics sorted. Make sure your team understands what user story mapping is, why user story mapping is important, and how to do it.
This will help get them onboard - which is critical, because you'll need them to commit two full days to the process.If anyone on your team is new to user story mapping, send them to our user story mapping ultimate guide. It's got everything they need to know 👌
2. Set your agenda
User story mapping should be a scheduled event. You should know what's happening and when to make sure that your team stays on schedule and completes all the steps required to produce a finished story map. Here's a fairly standard agenda:
Knowing your agenda is especially important for remote story mapping, because it's a lot easier to veer off track when people aren't physically in the room.
Sally might head to the kitchen for a long lunch and miss the most important bit. Or Bob might need to coordinate his schedule so that his partner can mind the kids for a solid hour or so while he's involved in estimating the work.Setting the agenda ahead of time will also help your team start thinking about the session and user stories before the event. That way, they’ll feel more prepared and ready to participate in discussions.
By the way, if you’re not familiar with all the items in the above agenda, we talk more about the specific steps and how to do user story mapping in our ultimate guide to user story mapping.
3. Plan your session
When are you going to hold your live online user story mapping session? Most teams need a full two days to work through all the steps, so you'll need to find two days (ideally in a row) when everyone is available.
If your team is located across multiple time zones, you'll also need to consider what times give you the best crossover so that team members aren't working at 2 am (unless they want to).
4. Decide on who
Remote user story mapping could present you with a bit of a conundrum. Unlike in-person events where you're limited on space, you could technically have unlimited people chime into your virtual session. But you definitely don't want that - too many people will make you inefficient (and they could use their time to add value to your business in other ways).
It’s a good idea to cap your numbers at around 12 people. Include team members and stakeholders across multiple departments, along with your product manager, UX designer, and developers.
Also decide who is going to lead the session and who will be responsible for creating the story map.The good news is that online user story mapping makes it easy to record sessions - you'll have a digital record of your conference calls and your story mapping board. So anyone who's curious can easily catch up on the highlights once your event is over.
5. Make some rules
Working and collaborating remotely can feel a bit like the wild, wild west - especially the first few weeks or months. Everyone's still figuring out how to make this thing work - and how to get things done effectively in a new environment.
We've all been to conference calls where somebody didn't know proper etiquette or their audio/video ended up distracting other attendees.
So, with that in mind, here are some rules you might like to share ahead of your remote user story mapping session to make it a little less chaotic and a lot more productive:
- Don’t be late
- Put your camera on
- Save your food for a designated break
- Don’t take your device for a walk
- Close your door, if you can
- Stay focused on the task (no checking emails!)
- One person talks at a time
- Wait until everyone has had a chance to provide input before moving on
- If you’re not talking or participating in the conversion, mute yourself (to avoid interference or background noise that could stop people from focusing)
Of course, be realistic. Your team members are likely working from home in less-than-ideal circumstances, whether they're quarantined with family members, stuck at home with a sick child, or dealing with a bad-mannered house dog.
There will be noise and disruptions - and despite their best efforts, someone will be late. As long as people do their best to hit the mute button at the right time and consider others, your session should run smoothly.6. Get your tech ready
Previously, you might have been able to show up to a user story mapping session with just your brainy self and a pen 🧠🖊️ You'll still need your brain for remote user story mapping, but you can ditch the pen.
Instead, you'll need to make sure you and your team have access to the technology they need to participate and collaborate online. Things like:- Zoom, Google Hangouts, or Skype access - Everyone should have their account ready to go, along with some experience using the platform
- Slack or Microsoft Teams - Set up real-time chat for when you’re not in a video conferencing session
- Headphones & Microphone - These should be working well and tested ahead of time
- Webcam - While not strictly necessary, a webcam will help you replicate the feeling of being in the room together
- Internet - Ask your team to test their connection and make sure it's reliable - and ideally, have at least one backup option (like a local cafe, friend's house, or mobile hotspotting)
The right technology will allow you to adapt the user story mapping process to work for your remote team.7. Get user story mapping software
A physical user story mapping session usually involves a long sheet of paper or cardboard, with hundreds of tiny post-it notes for each story and backbone item, and string to show cut lines.
The good news is, if you're doing remote user story mapping, you won't need to clear out your nearest stationery supply store 🎉 But you will need to equip yourself with some digital tools to replicate the physical story mapping board online.
There are a few user story mapping tools on the market, but we're partial to Easy Agile User Story Maps. It plugs straight into your existing Jira workspace, allowing you to:
- Visually map your customer journey
- Assign stories to epics
- Prioritize and sequence stories
- Arrange stories into sprint and version swimlanes
- Add story point estimates
It’s just like physical user story mapping, but done digitally inside of Jira. That makes it perfect for running a remote user story mapping session.
Okay, so we may be a little biased, but these people aren't:
Want to give it a spin for your upcoming remote user story mapping session? Sign up for our free 30-day trial to see the benefits for you and your team. We’re confident you’ll love what you find!8. Integrate your workflow
Last but not least, make sure that your remote user story mapping session integrates with your workflow
Good news! If you use a digital user story mapping tool (like Easy Agile's), you'll find it much easier to integrate your story map into your workflow. Once your user story mapping session is finished, your user stories are already set up in Jira, and organized into sprints or versions so that your team knows exactly what they need to work on next.
(Although they might want to take a day or two to ease back into it...😴)
Set yourself up for success!
With the right preparation and tools, you'll set yourself up for a relatively smooth remote user story mapping session. And after that? You'll be set to do your future story mapping events in a more streamlined, digital way, whether you're required to work remotely, collaborate with a distributed team, or work from the office.
And based on the way work is changing in 2020 (and beyond), that's a very good skill to have.
WorkflowFrom surviving to thriving: remote PI Planning with Easy Agile Programs
The most efficient and effective method of conveying information to and within a development team is face-to-face conversations.
Agile Manifesto, 2001
As true as this statement was when it was written, the Covid-19 pandemic irrevocably changed the way we work, live and communicate.
As organisations and individuals we found ourselves quickly needing to adapt to an ever-changing environment. Now that we have survived, we have to lean into this new way of doing things in the workplace so that we can thrive.
But what about our agile ceremonies?
One of the main reasons companies transition to agile is to make business processes and outcomes more efficient. So how do we take those principles and practices and preserve their integrity in a remote environment?
If you’re familiar with the Scaled Agile Framework, you’ll know that PI Planning is an agile ceremony that is at the heart of implementing SAFe.
Traditionally a face-to-face event, PI Planning is a scaled cross-team planning ceremony that aims to bring together multiple teams to plan - aligning them around a shared mission and vision for the upcoming quarter or increment.
SAFe still advises that PI Planning is still collocated where possible, and it does have its benefits.
However many teams, even before the pandemic, used PI Planning software to run their planning process and to make it more efficient and accessible to distributed PI Planning. But as with most things we have taken online since Covid, we are at the mercy of the tools we use to determine how effective we can be.
The truth is, unless you can get all members within an Agile Release Train - Business Owners, stakeholders, product management, Release Train Engineers, Scrum Masters, and teams - physically in the one room at the one time, considering alternatives is necessary.
It’s important that everyone is present during PI Planning, but that doesn’t mean they have to be physically present to make PI Planning a success
Remote PI Planning with Easy Agile Programs
We are now beyond the period where we needed to adapt to remote work. Our own business agility has been tested and we have needed to evolve.
Since we first launched Easy Agile Programs, we have continued to build on the capabilities it has to help teams and organizations around the world thrive in a remote environment.
With a simple but powerful tool seamlessly integrated with Jira, the latest version of Easy Agile Programs has a range of features aimed at helping distributed teams through the PI Planning ceremony and to build out a long-lived but flexible digital Program board in Jira.
Moving to remote or hybrid PI Planning doesn’t need to jeopardize yours or your customer’s success. In fact with the right tool, it can enhance it by saving time on context switching, complex configurations and double-handling.
The PI Planning Agenda
Regardless of whether you are following a more traditional 2-day PI Planning agenda, or need to accommodate a split agenda in a distributed environment, the core agenda items are the same. We’ll walk you through each of those and how Easy Agile Programs supports these key features.
Source: Scaled Agile
Setting the business context
PI Planning kicks off with the Business Owner(s) or senior executives giving a presentation where they describe “the current state of the business, share the Portfolio Vision, and present perspective on how effectively existing solutions are addressing customer needs” (Scaled Agile - PI Planning).
In the Program details section of Easy Agile Programs, Business Owners can share a recorded video presentation with all members of the ART, or a Zoom or video conferencing link.
As a result, the presentation isn’t restricted to team members being physically present for this agenda item, and can be referred to throughout the PI Planning session and beyond.
Setting the Product/Solution Vision
Next in the agenda, Product Management will present the current vision, typically in the form of the top 10 upcoming features.
Rather than presenting the top 10 features in a list on a slide or document, Program Managers can access Jira Features (Epics) right within Easy Agile Programs and can schedule them onto a visual timeline for the duration of the Program Increment (PI).
The Program Roadmap ensures all teams are aligned on the committed features for a PI and provides visibility into the direction of the Program for all stakeholders.
It’s at this point in the PI Planning ceremony that Product Managers may also call out any upcoming milestones.According to Scaled Agile, ‘Milestones mark specific points on the development timeline, and they can be invaluable in measuring and monitoring the product evolution and risk.’
Easy Agile Programs enable you to create highly visible milestones on the Program Roadmap to highlight key delivery dates, external events, or business milestones. These can also be created on the Program Board, or at the team level on the Team Planning Board. They are represented by colored flags at the top of the Roadmap that spans the team swimlanes that make up the Program.
Team Breakout Sessions
In the team breakout, teams work individually to estimate the capacity for each Sprint in the PI. Teams create new or identify existing issues from their backlog that will help achieve the set features. The draft team plans are visible to all members of the ART.
To make this easier, Easy Agile Programs has dedicated Team Planning Boards accessible to all who have access to the Program. Simply clicking on a team’s name will take you to their team Planning Board where they are able to set capacity for each sprint within the PI:
Teams have the context of their committed features at the top of their Team Planning Board, both those that are shared by more than one team in the ART or are specific to their team.
To plan the work needed to achieve these features, teams are able to drag and drop existing issues from their backlog or quick create new issues right within the planning board.
During this session, teams also create draft PI Objectives. These are a critical part of linking what the team is working on to broader business objectives, and you don’t need to leave the Team Planning Board to create them.
In Easy Agile Programs you can indicate whether the objective is committed or uncommitted, provide a description, and directly link the Jira issues scheduled to achieve this objective with the objective itself:
During PI Planning, Business Owners will have a discussion with teams about their PI Objectives which provides an invaluable opportunity to align. The Team Planning provides the artefact to facilitate those conversations, and allows Business Owners or stakeholders to assign a business value directly within the tool.
An important part of the team breakout sessions is identifying any dependencies or potential risks to scheduling work. Through drag and drop or create dependencies mode, it is very easy to create and visualize dependencies across teams in the Team Planning Board.
Aside from highly visible dependency lines, our customers also appreciate being able to see the health of those dependencies. If a dependency line is green it means the dependency is healthy, if it’s orange it is at risk, and if it is red it means we are blocked i.e. the work needed to be done to achieve an earlier piece of work is scheduled after it.
And the best bit of all? This is visible to all in the ART in a digitized SAFe Program Board.
On the Program Board, we have the option to have a detailed view with team-level issues visible or to hide them so we can just see features.
Wondering whether Easy Agile Programs could support your organization's PI Planning? With a seamless Jira integration, it takes minutes to set up.
Free trial of Easy Agile Programs
Program Risks
During PI Planning, we need to be able to identify risks and dependencies to assess whether teams in the Agile Release Train are set up for success to reach their PI Objectives.
A digital Program Board provides transparency to all members of the ART during PI Planning and acts as a single source of truth during and beyond planning. A digital artefact enables the Program Board to become more than a plan, and lives longer than the strings and post-it notes on a physical wall.
We know that visualizing feature-level dependencies is crucial to not only understanding but also troubleshooting the health or status of a PI. Not just during PI Planning itself, but also throughout the PI during execution.
The Program Board in Easy Agile Programs is highly visual and also filterable. Colored lines that indicate the health of the dependency ensure we have an at-a-glance view of significant dependencies that pose a risk to our PI.
Additionally, our scheduling conflicts feature surfaces when there is work scheduled outside of its associated feature, to immediately and clearly indicate where there is a risk.
The ability to filter by dependency health and team in Easy Agile Programs helps to focus conversations around risks during PI Planning.
Plan rework
After presenting plans to the ART and discussing scope, cross-team dependencies, required resources, and risks, teams then proceed to a confidence vote.
If needed, a closing part of planning is to rework any plans so that all teams within the Agile Release Train are confident in what they are committing to.
This may involve rescheduling to address dependencies, breaking work down further, adjusting estimations, etc.
Reworking is simple and streamlined within Easy Agile Programs. The ability to inline edit issue estimates and summaries in real time makes any rework fast and simple. Dragging and dropping an issue easily reschedules it and any impact on associated dependencies can be seen all at once.
All changes made to issues in Easy Agile Programs are automatically reflected in Jira.
Find out how Easy Agile Programs can make PI Planning easy for your collocated, hybrid or remote teams.
Join a product tour to walk through Easy Agile Programs
What about beyond planning?
We’ve examined the merits of remote PI Planning using a digital tool like Easy Agile Programs but something that so often gets overlooked is - what happens after planning?
A plan remains just that if it’s not translated into action. A plan isn’t made not to be fulfilled, and this is where a distributed or hybrid environment can be challenging.
Your Program Board may set you up for success, but ask yourself - how will you know if you’re on track to achieve it?
This is where having a digital, user-friendly tool that uses native Jira issues helps. At the end of PI Planning, teams have created a plan in the form of a Program Board in Jira, but they are also ready for sprint one as soon as PI Planning is done.
From there, the Program Board is set up and capable of evolving, not rolled up and stored away. This is what Easy Agile Programs is designed to do - to provide transparency but also flexibility so that the plan can necessarily adapt and be agile while maintaining momentum towards progress.So what’s up next for Easy Agile Programs? Can you help us improve it? Check out our product roadmap and if there is something missing let us know.
Agile Best Practice6 Tips for Setting Up Distributed PI Planning
Is agile now distributed?
It’s no secret that our work has completely changed in the last two years. Today’s work environment has seen companies embracing a hybrid or fully remote business model, with studies showing that only 4% of workplaces are going back into the office full-time.
In the Agile Manifesto, one of the original principles states, “individuals and interactions over processes and tools.” While this may still ring true, we know now more than ever that our tools empower our interactions and facilitate our processes.
Multiple industries that have adopted the agile framework have shown an increase in distributed agile teams. In fact, according to the 15th State of Agile Report, 89% of agile teams are distributed. Only 3% of these teams will return to the office full-time post-Covid. This is because remote workers have better focus and productivity, are less likely to leave their job, and cost the business less.
Distributed agile is no longer a new concept but our lived reality.
How do we prepare for agile ceremonies such as PI Planning, initially designed to happen face-to-face? How do we retain the most valuable element of face-to-face communication without collocating?
The challenges of PI Planning with a distributed team
Traditionally, activities like PI Planning in agile are designed for team members in the same room to interact in person.
PI Planning is a 2-day event that brings all members of an Agile Release Train (ART) together to plan their next Program Increment (PI).
As the 15th State of Agile Report showed, 89% of agile teams are now distributed. For a distributed team, your options are to fly in employees for each PI Planning session or to support a distributed PI Planning session.
While this is nice, it can be a pricey (and disruptive) exercise for any organization, especially if you need to do it 4 or 5 times a year.
Performing distributed PI Planning also brings up a challenge with using a physical program board. Those at home cannot access or contribute to the physical PI Planning board in the same way as their collocated colleagues. As a result, their ideas can go unheard, and their ability to contribute to the program board is limited.
Distributed PI Planning - Best Practice
Instead of flying your remote team to a central location to run PI Planning in person, distributed PI Planning involves using cloud-based tools to plan and run your next Program Increment virtually.
Even if the methods are a little different from distributed PI Planning, the process and desired outcomes are the same:
- A senior representative discusses the current state of the business
- Product Management presents the current program vision
- Product Owners and teams breakout separately to discuss how they’ll achieve desired outcomes
- Teams identify and visualize cross-team dependencies and work to remove blockers
- Everyone comes together to agree on a committed plan via your Program Board
6 tips for setting up distributed PI Planning
Distributed PI Planning is no longer a temporary exception. Whether PI Planning is distributed or not, we need to ensure we maintain the same quality and outcomes that PI Planning aims to achieve - to align all teams within the Agile Release Train.
To help you through this, we’ve prepared the following 6 tips to help you prepare for distributed PI Planning.
These tips aren’t things that we’ve just brainstormed. We’ve learned these things from speaking to our customers by trawling the forums and talking to experts in the field.
1. Get the basics rightThe three basics are communication, preparation, and execution.
Let’s start by talking about communication and preparation. It is essential to provide appropriate tools for online interactions for each stage of the PI Planning process: for product managers to collaborate and facilitators to manage the process-both leading up to and during the event. We also need to ensure team members can access all relevant current information, collaborate effortlessly, and access support.
Scaled Agile recommends having pre-PI Planning meetings scheduled anywhere from 2-6 weeks in advance, depending on the complexity of your solution train.
Lastly, let’s talk about execution. The execution should flow if we are communicating well and are prepared. But we need to be prepared that some things can still go wrong. Technology will fail us. People can still have problems accessing the tools we’ve set up. Execution won’t always be seamless, but iteration is a principle of agile.
2. Set the agenda early, as early as possible
Why is that? Well, think about your employees working from home. They’re working with their pets or family around, and if they know that they have PI Planning, they need to know what is expected of them.
This allows time for employees to inform their families of their commitments for that day, set up a space with no distractions, and be mentally prepared for a few days of planning.
Also, let’s not cram the agenda full of all the events we need to hold. Let’s make sure we have enough time to schedule multiple breaks throughout the day, as studies show that humans are more likely to experience mental exhaustion after a day of video conferencing.
While it’s essential to use the tech, it can get a little bit much. Set up rules about who can talk and when to use the mute button. This will avoid interference and background noise disrupting your team’s focus.
3. Choose your tools wisely
Distributed agile teams can simulate the best of the in-person experience by selecting tools built for distributed and hybrid teams: video conferencing platforms, team chat, virtual program boards, and interactive collaboration spaces.
Whatever tools you choose, the key is finding solutions for colleagues to connect in real-time, whether in the same room or on the other side of the world.
Set up the tools, test them, and introduce them to all participants before the PI Planning session. To avoid overload and confusion, select tools that work together seamlessly.
4. Practice
We’re not going to get this right the first time. We’re going to have to rehearse. We’ll have to work out how we do things like confidence votes. Will we use the poll function on Zoom, or will we use Slack?
Everyone prefers to finish early rather than run out of time. Let’s build some slack into the agenda.
Acknowledge that there’s always room for improvement and build that into our planning. Let’s give our people a chance to communicate back to us, whether by a retrospective or by opening up a channel for feedback. We’re not just getting feedback on how the last planning session went but also on how we are finding working together more generally.
5. Make it accessible
When dealing with different time zones, you should extend the PI Planning agenda from 2 days to 3-4 days to ensure all critical parts of the PI Planning session are placed at a reasonable time for all time zones.
Set up each meeting via Google Calendar or any calendar device your team may already be using. Ensure each meeting is named, followed by a description, so attendees know what to prepare and which tools are relevant for this meeting. Make sure the correct attendees have all been sent invitations to the forum before the event.
We’ll have trouble setting up people on new tools and getting them access to their needed resources. It will be great if tech support is available throughout PI Planning. That will be easier for some people than it is for others. But it’s crucial if things go wrong.
We’re going to need a backup in place. Your tools will need to be reliable, and you will need tech support to help fix them quickly.
We will need more facilitators than we usually do to be able to answer all of these questions throughout the week.
Some people may not be used to using the tools that we’re suggesting that they use. So is there training available to help them get up to speed?
6. Level up the human experience
Seize opportunities to ensure agile teams feel as if they are working together when they are actually apart so that members see themselves as part of a community with:
- Shared understanding – Clarity of vision, mission, purpose, and visibility into what team members are doing, facilitating learning loops among colleagues.
- Shared empathy – Forging human connections with our tribe creates the psychological safety to learn, grow and iterate.
- Shared experience – Creating a sense of team place, identity, and building together.
How to excel at distributed PI Planning with Easy Agile Programs and Welo
The most challenging part of distributed PI Planning is providing the positive aspects of the in-person experience to a distributed team: fluid movement around and between rooms to collaborate, easy ways to contribute to brainstorming sessions and keep whiteboards up to date and accessible, and natural social interactions that build trust and camaraderie.
Easy Agile Programs offers a complete PI Planning solution that makes scaled cross-team planning and execution easy. With a seamless Jira integration, it’s a powerful yet simple-to-use tool to scale planning and maintain alignment across distributed, hybrid, or remote teams during planning and throughout execution.
Welo offers interactive collaboration spaces that amp up the human experience for distributed and hybrid teams. It replicates the in-person experience of fluid interactions, effortless collaboration, and human connections among colleagues–beyond the isolated video. Welo’s visual orientation enables each person to be present in the context of space and to navigate to be with people and groups as they choose.
With these two tools, you can set your Agile Release Train up for success for PI Planning. Here’s how:
Select professionally-designed virtual spaces
Bring online the best of the brick-and-mortar spaces you used for in-person PI Planning–from plenary to break-out rooms to spots for casual socializing.
Rather than feel confined to a static rectangle, people see themselves and others in context, move themselves in and between spaces to connect with colleagues before, during, and after PI Planning events.
Welo spaces also provide PI participants ready access to up-to-date, relevant resources, such as Jira and Easy Agile apps used across all events.
Establish the Business Context
All Agile Release Train members can access information about the program in Easy Agile Programs. For example, in the objectives section below, you could link to a pre-recorded video of the business owner addressing the company-level objectives. Hence, teams know that their team-level objectives must ladder to this. This ensures that all members of the Agile Release Train see your business owner face to face in that distributed way and that they always have access to this video throughout PI Planning.
After viewing the information about the program, the Product Manager can create features in Jira ahead of the PI Planning event to be discussed and broken down in planning. Easy Agile Programs seamlessly integrates with Jira, so there's no need to double-handle the work. They are ready to schedule onto a visual timeline for everyone to see what the team has committed to during PI Planning.
Set up your SAFe Program Board
The SAFe Program Board is a critical tool and output of PI Planning; It is a visual summary of features or goals, cross-team dependencies, and other factors that impact their delivery. Not only does this help with transparency, but it also increases flexibility, which helps minimize delays and unhealthy dependencies.
Ensure you have a digitized SAFe Program Board set up before the PI Planning session. Easy Agile Programs replicates the physical program board. A board that everyone has the same view of and can access. Learn how to set up a SAFe Program Board with Easy Agile Programs here.
Prepare your Team Planning Board
The Team Planning Board represents a scrum or kanban board which is included in the Program. This is where the teams will plan their work in the team breakout sessions during PI Planning.
If you have set up your Program Board with Easy Agile Programs, prepare the team Planning Boards by adding each team to the Program ahead of PI Planning. Once teams are added, Planning Boards are automatically created and ready for team breakout sessions. Teams can create team-level PI objectives, break down features into user stories, estimate issues to understand capacity, and create dependencies with other teams.
Moving forward
With distributed PI Planning a reality for nearly 90% of agile teams, the good news is that new solutions are being developed to work with your current tools–powering employee engagement, fluid collaboration, and efficient processes critical to successful outcomes and career satisfaction.
Equip your remote, distributed or co-located teams for success with a digital tool for PI Planning.
Easy Agile Programs