No items found.
3.5/4

8,960 installs on Atlassian Marketplace

Jira apps for agile teams

Visualize workflows and help teams collaborate anywhere. Trusted by more than 160,000 users from leading companies worldwide.

 

Join the 10,000 product teams already using Easy Agile

Features

See Jira like never before

  • Find scheduling issues across teams

    Know when team A is going to impact team B before it becomes a problem with dependency markers that reach across team boards. Maintain alignment and foster collaboration to keep everyone on track.

    UI of Easy Agile Programs showing dependency lines
  • One unified view for epics, sprints, versions and User Story Maps

    Create a single view for teams, and a unified understanding of what really matters. Keep deliverables on track and aligned to user stories.

    UI of Easy Agile TeamRhythm user story map
  • Be ready to rock with retrospective templates

    Keep your retrospectives relevant and work your way with customizable retrospective templates.

  • Run smoother PI planning sessions

    Bring distributed teams together to plan your next increment. Prioritise, and create high-context visual dependency maps and reporting.

    Focussed view of dependency map in Easy Agile programs
  • Make sense of the flat Jira backlog

    Level up backlog refinement and make sense of the flat Jira backlog with visual representations directly in Jira.

    Focussed view of the user story map in Easy Agile TeamRhythm

Testimonials

Don't just take our word for it...

Hear from some of our amazing customers who are making agile easier.

  • You get smart, sexy and colourful displays of workstreams: for us, that was hugely impactful when dealing with an industry that had never seen this type of professional delivery.

    Andrew Ross
    Bluey Merino
  • We’ve improved our communication and team alignment, which has helped give us faster results.

    Casey Flynn
    Adidas
  • Easy Agile apps are intuitive and easy to use. The features perfectly complement the Jira experience and provide our teams with easy ways to organize and scale work.

    Christopher Heritage
    NextEra Energy

Built for teams who work in Jira

All Easy Agile apps sit inside Jira, visualizing and enhancing your Jira data with new views and functionality

Use Cases

We’re making agile easier…

Tools that help people shine in their most important agile ceremonies.

  • PI Planning

    PI Planning is the heartbeat of your agile release train. Take care of it with Easy Agile.

    Learn more
  • SAFe

    SAFe promises much, but also asks much of teams. Reduce the burden of SAFe with Easy Agile's simple, flexible tools.

    Learn more
  • Dependancy Management

    Know exactly what’s coming, and how to master dependency management with high-context visual flags at every stage.

    Learn more
  • User Story Mapping

    Know your user’s journey and ensure alignment with business objectives through User Story Maps

    Learn more
  • Sprint Planning

    Work the way you want with native scrum sprint planning in Jira. Just made faster, smoother, better

    Learn more
  • Retrospectives

    Give remote and on-site teams the structure to reflect on their latest sprint and the processes to identify what worked, and what didn’t with retrospectives

    Learn more
  • Backlog Refinement

    Be ready for your next sprint with intuitive tools to make your review and prioritization of the product backlog a breeze

    Learn more
  • Roadmapping

    Connect teams, groups and your whole organization under one vision for your product future

    Learn more

Webinars

Webinars and events

Join us for an upcoming in-person or online event so we can answer your questions and dive deep on Easy Agile products and agile best practice.

Our Blog

Latest blog posts

Tool and strategies modern teams need to help their companies grow.

  • Agile Best Practice

    Agile Ceremonies: Your Ultimate Guide To the Four Stages

    This guide looks at the four ceremonies that bring one of Agile’s most popular frameworks, Scrum, to life.

    Learn how each agile ritual helps empower teams and drive performance while highlighting some tips to help your organization get the most from your ceremonies.

    At a glance:

    • The four agile ceremonies are Sprint Planning, Daily Stand-Up, Sprint Review and Sprint Retrospective
    • Ceremonies in agile facilitate visibility, transparency, and collaboration.
    • Each ceremony has a clear structure and objective.
    • Clear communication, flexibility, and cultural alignment are the keys to successful ceremonies.

    What are the main agile ceremonies?

    Agile ceremonies refer to the four events that occur during a Scrum sprint. Other forms of agile development, such as Kanban and Lean, also have similar practices.

    The agile ceremonies list includes:

    1. Sprint Planning
    2. Daily Stand-Up
    3. Sprint Review
    4. Sprint Retrospective

    While each ceremony is different, they facilitate the same overall purpose. The ceremonies bring teams together with a common goal under a regular rhythm, and they help teams get things done.

    "With today's enterprises under increased pressure to respond quickly to the needs of their customers and stakeholders, they must bring new products to market faster and accelerate improvements to existing solutions and services." - State of Agile Report

    Why are agile ceremonies important?

    Agile ceremonies help organizations adapt to change and succeed. With work planned in smaller portions and over shorter timeframes, they help teams quickly shift direction and course-correct when needed. They form a key part of the broader agile approach that’s now widely adopted in organizations worldwide.

    With agile ceremonies, teams in your organization can benefit from:

    • Enhanced ability to manage changing priorities
    • Acceleration of software development
    • Increase in team productivity
    • Improved business and IT alignment

    It’s important to remember that while ceremonies are an essential part of Scrum, they’re just one of many rituals that help create agile teams and workplaces. To realize the true benefits of agile, you’ll need to do more than include one or more of the ceremonies into your waterfall project.

    1. Sprint Planning

    The Sprint Planning ceremony sets teams up for success by ensuring everyone understands the sprint goals and how to achieve them.

    StructureAttendeesTimingDurationAgile FrameworkThe Product Owner brings the product backlog to discuss with the Development Team. The Scrum Master facilitates. Together, the Scrum Team does effort or story point estimations. The product backlog must contain all the details necessary for estimation. The Product Owner should be able to clarify any doubts regarding the product backlog. The entire Scrum Team (the Development Team, Scrum Master, and Product Owner)At the beginning of each sprintOne to two hours per week of iteration. So, if you're planning a two-week sprint, your Sprint Planning should last two to four hours. Scrum. Although Kanban teams also plan, they do it less formally and per milestone, not iteration.

    Outcomes

    After some team negotiation and discussion, you should have a clear decision on the work that the Development Team can complete during the sprint by the end of Sprint Planning. This is known as the sprint goal.

    The sprint goal is an increment of complete work, and everyone should feel confident about the commitment.

    The product backlog defines priorities that affect the order of work. Then, the Scrum Master transforms that decision into the sprint backlog.

    Top tips

    • Focus on collaboration rather than competition.
    • Break user stories into tasks to get things more operational for the Development Team. If there's time, assign those tasks during the event.
    • Factor in public holidays and any team member’s time off or vacations.
    • Keep your team’s pace in mind – a track record of the time it took to implement similar user stories would be helpful.
    • Focus on the product backlog and nothing else in terms of work for the sprint.

    2. Daily Stand-Up

    The daily stand-up brings the team together and sets everyone up for the day. The team uses this time to identify blockers and share plans for the day.

    StructureAttendeesTimingDurationAgile frameworkThis is an informal, standing meeting. All members of the Development Team inform everyone about what they did the day before and what they’re doing today. Members discuss any blockages they have and ask for help from the team if required. Due to time restrictions, the updates should be brief.Development Team, Scrum Master, Product Owner (optional) Daily, usually in the morningShort and sharp. No longer than 15 minutesScrum and Kanban

    Outcomes

    The Scrum Master should clear all the blockages that slow down or prevent the Development Team from delivering. As a result, the development process might need to change.

    This daily pulse check keeps the team in sync and helps build trust. Together, the group finds ways to support and help each other.

    Top tips

    • Use a timer to keep this meeting to 15 minutes.
    • Hold your stand-up at the same time every day.
    • Only discuss the work for the day ahead.
    • If the team is distributed, use video conferencing with cameras on.
    • Long discussions should happen after the event.
    • As the stand-up encourages progress, everyone should provide an update, and everyone should feel accountable.

    3. Sprint Review

    The Sprint Review is the time to showcase the team’s completed work and gather feedback from stakeholders. A variety of attendees from outside the team offer valuable insights from different viewpoints. This event also helps build trust with both external and internal stakeholders.

    StructureAttendeesTimingDurationAgile frameworkThe Scrum Master takes on the logistics of event preparation. The Product Owner should ask stakeholders questions to gather as much feedback as possible. They should also answer any of their stakeholder’s questions.Development Team, Scrum Master, Product Owner. Optionally, management, customers, developers, and other stakeholders At the end of the sprintOne hour per week of the sprint. In a one-week sprint, the Sprint Review lasts one hour.Scrum and Kanban. Kanban teams do these reviews after the team milestones, not sprints.

    Outcomes

    After this ceremony, the Product Owner might need to adjust or add to the product backlog. They might also release product functionality if it's already complete.

    Top tips

    • Schedule in time to rehearse before the meeting to help your team present with confidence, especially if external stakeholders are coming along.
    • Don’t showcase incomplete work. Review your Sprint Planning and the original criteria if you’re not sure whether the work is complete.
    • Besides product functionality, focus on user experience, customer value, and the delivered business value.
    • Consider ways you can introduce a celebratory feel to acknowledge the team’s effort.

    4. Sprint Retrospective

    In this final scrum ceremony in the sequence, you look back on the work you’ve just done and identify ways to do things better next time. The Sprint Retrospective is a tool for risk mitigation in future sprints.

    StructureAttendeesTimingDurationAgile frameworkThe teams discuss what went well throughout the sprint and what went wrong. The Scrum Master should encourage the Development Team to speak up and share not only facts but also their feelings. The goal is to gather rapid feedback for continuous improvement in terms of process. It’s also an opportunity to emphasize good practices that the team adopted and should repeat.Development Team, Scrum Master, Product Owner (optional)At the end of the sprint45 minutes per sprint weekScrum and Kanban (occasionally)

    Outcomes

    After this session, the team should clearly understand the problems and the wins that happened throughout the iteration. Together, the group comes up with solutions and an action plan to prevent and identify process problems in the next sprint.

    Top tips

    • Focus on both facts and feelings
    • Gather information that helps you focus on continuous improvement – this might include tools and relationships
    • Be honest and encourage ideas that solve process-related problems
    • Even if everything went well, have this meeting – retrospectives provide ongoing guidance for the next sprint.

    "With the speed of change expected to continue, the need has never been greater for an operating model that keep up." - McKinsey

    Agile lessons to live by

    As a team of experienced agile practitioners, we’ve picked up some key learnings about what it takes to get the most out of your agile ceremonies and create the foundations of a truly agile organization.

    Here are our top tips to make your ceremonies a success:

    • Be deliberately present - During the ceremonies, remember to take moments to pause and remind yourself of why you’re there. Show others that you’re present by giving them full attention and using your body language. In a remote setting, angle your camera as though you’re sitting across from them, look into the lens regularly, and use a distraction-free background.
    • Practice active listening - Think about what the person is saying, who they are, and what they need from you. Are they looking for a soundboard, do they need your help or opinion, or are they looking for an emotional connection?
    • Understand motives - Understand the motivations of your teammates before speaking. Consider why they should care about what you’re saying by connecting your message with their own motivations. Provide context where possible to let them know why your message matters.
    • Be flexible - It's important to remember that there is not a one size fits all approach to agile ways of working. What works for one team may not work for another, so you need to experiment to find out what works then tailor processes to suit your team's needs.
    • Create cultural alignment - The best processes in the world won’t deliver what you need if you don’t have the culture to support their delivery. Agile ceremonies need to be supported by a culture where people are actively engaged, confident to raise issues, and value continuous improvement.

    Agile ceremonies lead to better results

    While it can take time for teams new to agile to adjust to agile ceremonies, they are worth the effort. By providing a clear structure and achievable outcomes, they help align everyone on the product, communication, and priorities.

    The result? Agile teams that provide better quality products faster – and deliver real business outcomes.

    Wherever your organization is on your agile journey, it’s worth keeping in mind that each team and each suite of products are different, so there’s no standard recipe for success. The good news is that by working within the continuous improvement mindset the agile framework promotes; you too can iterate and improve your agile ceremonies over time.

    Ready to get started?

    Easy Agile TeamRhythm supports your team's agile practices in Jira. Supporting your team from planning right through to retrospective, TeamRhythm helps you and your team work better together to deliver value to your customers.

    Features include:

    • Agile sprint and version planning tool - Planning is quick and easy when you create and estimate issues on the story map. View your work under initiatives and epics, and see swimlane stats at a glance, ensuring team capacity is filled but not overcommitted
    • Agile story mapping - Map the customer journey using initiatives, epics, and stories alongside your agile Jira boards. Quickly and easily add new or existing stories inside the story map. Drag and drop to prioritize by value to the customer.
    • Product backlog refinement - Escape your flat backlog and view your work on the story map matrix. Drag and drop issues to prioritize or schedule. Quickly update story summaries and story point estimates with inline editing for a better backlog.
    • Team retrospectives - Celebrate success, gain insights, and share learnings with team retrospective boards for scrum and kanban, encouraging collaboration and transparency, so you and your team are continuously improving.
  • Workflow

    The Ultimate Agile Sprint Planning Guide [2023]

    How do you feel when someone mentions “planning”? Do you look forward to the opportunity or does the thought of making a plan send you running for the hills?

    Sprint planning is a crucial part of the agile sprint cycle. It helps you and your team align around common goals, and sets you up for a successful sprint. Even if planning isn’t one of your strengths, the good news is that you can practice and get better over time with the help of some good advice.

    We’ve combined our best sprint planning tips into an ultimate guide to agile sprint planning, with everything you need to run efficient and effective planning meetings.

    What is agile sprint planning?

    Agile sprint planning is a key ceremony in the agile sprint cycle. It signifies and prepares the team for the start of the sprint. Without this planning, there is a very real risk that the team would lack focus and fail to align on what is most important.

    Effective agile sprint planning has three key parts; a sprint goal, an understanding of team capacity, and a prioritized set of backlog items. Each element depends on the other for success.

    The idea is to align your team around a goal for the next sprint by agreeing on a set of backlog items that are achievable within the sprint and contribute to reaching the sprint goal. Gaining focus and clarity on what you plan to achieve will help your team to work better together and to deliver on objectives.

    It is best to start with an agreed sprint goal. You can then prioritize work on the specific set of backlog items that your team has the capacity to complete, and that will contribute to making your sprint goal a reality.

    How sprint planning fits within the Scrum process

    Illustration of an agile sprint planning guide

    We’re big fans of the Scrum process, and it’s hugely popular with many software development teams. While agile sprint planning can take many forms within the different agile methodologies, for the purposes of this guide, we’ll focus on agile sprint planning within the Scrum framework.

    If your team doesn’t follow Scrum don’t worry — you’ll still find value in our preparation tips, meeting guide, mistakes to avoid, and sprint planning resources.

    💡 Learn more: What's the Difference Between Kanban vs. Scrum?

    Scrum roles: The people

    There are three main roles within a Scrum team.

    1. Product Owner
    2. Scrum Master
    3. Development team

    The Product Owner puts in the work upfront. They help prioritize the product backlog items and decide which should move to the sprint backlog. These important decisions guide the goals of the sprint and determine the tasks the team will tackle over the next sprint.

    The Scrum Master acts as a guide, they lead meetings that help ensure that the Scrum framework is followed throughout the sprint to keep the team on track. The Scrum Master helps the team get the most out of the entire Scrum process and each individual Scrum ceremony.

    The development team is made up of the various people who will complete the work agreed upon during sprint planning.

    There are others that you might refer to during sprint planning, such as stakeholders, users, and customers. While these aren’t technically Scrum roles, they play a critical role in product development. Stakeholders should be brought into the process early and often, and customers should always be top-of-mind when making any development decisions. Some teams find User Personas to be a valuable way of keeping user value in focus.

    Artifacts: What gets done

    Artifacts are the things to get done — different breakdowns of what the team hopes to accomplish:

    1. Product backlog
    2. Sprint backlog
    3. Increments

    Product backlog items are the tasks the team believes they need to accomplish in order to complete a product or specific improvement of a product. It is the big master list of everything that the team thinks they need to accomplish. The product backlog is flexible and iterative, and it will evolve as the team learns more about the product, stakeholder feedback, and customer needs.

    The sprint backlog is more focused than the product backlog. The product owner moves the most important backlog items from the product backlog to the sprint backlog at the beginning of each sprint based on current issues, priorities, and customer needs. The team aims to complete all of the sprint backlog items over the course of the sprint.

    An increment is a concrete stepping stone toward reaching the Product Goal. An increment must be verified as usable in order to provide value, which means that any work completed cannot be considered part of an increment unless it meets the Definition of Done (an agreement among the team of what “done” means). This is a formal description of the state of the increment when it meets the quality standards required of a product. Once the work completed satisfies the agreed Definition of Done, you gain an increment.

    Scrum ceremonies: Where Sprint Planning fits

    There are a number of ceremonies in Scrum that occur each sprint. This is where sprint planning fits within the Scrum process.

    1. Sprint planning
    2. Daily scrum (or standup)
    3. Sprint review
    4. Sprint retrospective

    💡 Learn more: Agile Ceremonies: Your Guide to the Four Stages

    Sprint planning is the first Scrum ceremony — it prepares the team for the sprint. The planning session sets everything into motion, aligning the team on what’s most important for this sprint. This is when decisions are made and key backlog items are moved from the product backlog to the sprint backlog.

    The second ceremony repeats every day of the sprint. Daily standups bring the team together to discuss progress and blockers that might be getting in the way. By getting the concerns out in the open early, the team can avoid the frustration of delays and ensure work continues to flow.

    The final two ceremonies happen at the end of the sprint. For the sprint review, the team comes together to determine the success of the sprint based on the “Done” work completed. It’s also a chance to bring in stakeholders to gather feedback on what's been accomplished so far. The sprint review ensures customer insights are always top-of-mind, stakeholders continually see progress, and guarantees the product never strays too far from what the stakeholders are looking for.

    The sprint retrospective gathers critical insights from team members about how the sprint went. What went well, what didn’t go so well, and what could be improved upon for next time? These valuable insights are what makes Scrum agile — the team is always thinking critically about the process and looking for ways to improve the work and how they work together.

    We’ll talk about these ceremonies in more detail below when we discuss what happens after the sprint planning meeting.

    The benefits of agile sprint planning

    Agile sprint planning is a powerful meeting that should not be overlooked or underestimated. It is an opportunity to:

    • Bring the whole team together and align around common goals
    • Set context by starting the sprint with clear priorities
    • Identify potential roadblocks before they occur
    • Bring stakeholder feedback into the planning process
    • Learn from previous sprints by considering sprint review and retrospective insights
    • Consider team capacity and adjust accordingly to ensure that goals are achievable and that the team isn’t overcommitted in the upcoming sprint
    • Account and plan for dependencies that may impact the flow of work.

    How to prepare for a sprint planning meeting

    We know we said that a sprint begins with sprint planning, but there are actually a few important steps you must take in order to prepare for the planning session. Unfortunately, you do need to do a little planning for the planning meeting.

    Backlog refinement

    Backlog grooming or refinement keeps your backlog healthy, up-to-date, and ready for sprint planning. A refined backlog will help ensure your team’s planning time is used efficiently and effectively since you won't have to waste time adding details to the backlog that could have been completed in advance before everyone came together.

    The product manager should groom the backlog a few days before the sprint planning meeting to make sure it’s ready.

    Tips for maintaining a healthy backlog:

    • Ensure stories are in order of priority
    • Prioritize items that bring the customer the most value
    • Add detail to the highest-priority backlog items
    • Split any user stories that are too big
    • Delete any user stories that aren’t relevant anymore
    • Create new user stories based on new or clearer needs
    • Add items based on new stakeholder feedback
    • Make adjustments based on bug fixes
    • Assign more accurate estimates

    💡 Learn more: Essential Checklist for Effective Backlog Refinement (and What To Avoid)

    Be consistent

    A consistent meeting time that’s scheduled well in advance will ensure that the entire Scrum team keeps the time slot open. Book your sprint planning meeting on the same day and at the same time every sprint so that no one forgets or double books.

    Sprint planning is not a meeting to be shuffled around, delayed, or ignored — sprint planning meetings are essential to the success of every sprint. Ask your team about a specific, recurring time to meet, and ensure it works for everyone.

    How to run a sprint planning meeting

    While the agile method is flexible and collaborative, it isn’t chaotic; everything needs to begin with a plan.

    1. Stick to a set sprint planning meeting duration

    As with any kind of meeting, the team can be easily sidetracked without a timebox. After all, talking about the work that needs to be completed is often easier than actually completing it. It’s the Scrum Master’s job to keep the team on track and make sure the time limit isn’t exceeded.

    Go into the sprint planning meeting well-prepared; a clear agenda and a well-refined backlog mean your team can get straight to planning.

    Set a realistic timebox for the meeting and stick to it. We recommend that you avoid scheduling more than 2-3 hours for a sprint planning meeting, but as you become more skilled in sprint planning, you’ll better understand the length of time that works for you and your team.

    2. Use estimates to make realistic decisions

    You want your team to be as productive as possible, but overloading them can actually hinder productivity and focus. Unreasonable expectations are demotivating and overcommitted team members are more likely to make mistakes.

    You need to understand the effort and time it will take to complete the goals you set out to accomplish for each sprint. Agile estimation techniques and story points provide a better understanding of team capacity, individual capacity, and what a reasonable workload looks like. Reasonable and realistic goals will help your team stay motivated and support a consistent flow of work.

    3. Define clear goals and outcomes

    What does the team aim to accomplish between now and the end of the sprint? Set clearly defined goals and outcomes that everyone understands. Do your goals align with what you learned from past sprints? Do they align with customer needs? Does everyone agree on what the next sprint will (roughly) look like?

    Don’t assume that everyone is on the same page. Ask questions and encourage your team to speak up if anything is unclear. It’s better to clear up discrepancies or misunderstandings now rather than once the work begins.

    Post your sprint goal somewhere that is easily accessible so that the team can refer back to it throughout the sprint.

    💡 Learn more: How to Make the Most of Your Sprint Goals

    4. Decide what it means to be ‘done’

    What does “done” mean for any given backlog item, increment, product issue, or product as a whole? The team and your stakeholders need to agree on what done looks like in order to set realistic goals that meet the expectations of everyone involved.

    As you set goals and choose which backlog items to complete for the next sprint, be clear about what it means to meet and complete the goals you want to accomplish.

    5. Align sprint goals with product goals

    Sprint goals should always align with your broader product goals. Your sprint may take a specific direction depending on current product issues, bug fixes, or customer concerns, but it’s important to keep an eye on the big picture.

    Choose backlog items with care — make sure they relate to the larger product goal and that each works in sync to move development forward. Overlooking product goals in sprint planning could mean that each sprint looks more like a random selection of to-do lists that don’t connect back to customer needs, relate to product goals, or help you reach important increments. The result will feel like a lack of progress, which risks disengaging the team and other important stakeholders, like your users.

    What happens next?

    Now that the planning is done, you’re ready to implement your plan and complete the work. But that doesn’t mean that team members go off and work in isolation.

    Daily scrum (or stand-up)

    The daily scrum or stand-up is an opportunity for a collaborative agile team to maintain progress. It should be a quick check-in at the start of each day.

    The team will discuss what has been done in the past 24 hours, any roadblocks they might have hit, and what the team hopes to accomplish the next day.

    This critical check-in helps the team stay on the same page, helps to ensure the continued flow of work, and keeps the team on track to achieve sprint goals.

    Sprint review

    A sprint review meeting takes place at the end of a sprint. It's a chance for the team to review all of the “Done” issues for that period. The sprint review determines whether or not the goal for the sprint was achieved.

    It’s a chance to demonstrate shippable working product increments to the team, and also an opportunity to bring in stakeholder feedback. This feedback gives you valuable insights to assess if you’re on the right track, or need to make changes in the next sprint. The sprint review is also excellent preparation for the next backlog grooming and sprint planning session.

    💡 Learn more: Introduction to Sprint Reviews

    Sprint retrospective

    While the sprint review looks at what was accomplished and how to move forward, the retrospective examines your processes and how the team is working together.

    What did you learn during the previous sprint? While retrospectives can take many forms, the goal is to discover what worked well, what didn't go so well, and what could be improved upon next time. Your team will use the insights gathered in the retrospective to improve how you work together and deliver value to customers in the future.

    💡 Learn more: 5 Steps to Holding Effective Sprint Retrospectives

    Agile sprint planning mistakes

    It’s easy to fall into bad habits, especially as deadlines and product launch dates approach. Avoid these common agile planning mistakes to ensure your team is always making the most of the agile methodology and the Scrum process.

    Unrealistic expectations

    Choosing unattainable goals sets your whole team up for failure. Failing to meet your sprint goals sprint after sprint is damaging for team motivation and morale.

    Use estimates to set reasonable goals as best you can. Consider team capacity, factoring in your past knowledge of how long tasks take to complete, how the team works, and potential roadblocks that could arise along the way.

    Lack of context

    Your team will benefit from an understanding of how the issues they’re working on fit into the bigger picture.

    Depending on the tool you’re using to plan and manage your work, it can be difficult to see the contextual detail needed to plan and work with clarity. The more items you have, the more difficult and overwhelming it will be to organize and prioritize. Use tools that allow you to add context, depth, and customer insights with clean functionality to adapt your plan to the needs of your team and stakeholders.

    Neglecting your backlog

    We mentioned this point when we talked about what you need to do to prepare for sprint planning. It’s worth mentioning again because it’s a common mistake.

    When you go into a sprint planning meeting without a well-managed backlog, you lack the clarity you need to plan effectively. Your time is valuable, and so is the time of your team, so it should be treated with care and used effectively.

    A well-managed backlog is DEEP:

    • Detailed appropriately
    • Estimated
    • Emergent
    • Prioritized

    💡 Learn more: The 4 Characteristics of a Good Product Backlog

    Not allowing the plan to adapt

    When you plan your sprint, you’ll do everything you can to prioritize the most important tasks for the length of the sprint. It’s important to try to stick to the plan as best you can, but you also need to adapt as you acquire new information.

    Be ready to make changes on the fly should you hit roadblocks or acquire new information about customer needs, concerns, or product issues.

    Failing to understand stakeholders

    You need to understand the goals and priorities of stakeholders to be successful. Just because you’re happy with what you’ve accomplished doesn't mean your stakeholders will too.

    Ensure your stakeholders are brought into your process early and often and help them understand how you work to provide them value. Gather feedback from stakeholders regularly to ensure your goals are aligned. A good time for this is during the sprint review. Just make sure those insights are transferred over to your next planning meeting.

    Not choosing tools with a customer-centric approach

    Successful product development delivers what the customer needs and wants. To build for your customers, it helps to use tools for planning and work management that makes it easy to keep them top-of-mind. Incorporating user story maps and customer personas into your planning helps you and your team prioritize the work that will deliver the most value first.

    💡 Learn more: 10 tips for more effective user personas

    Failing to incorporate retrospective insights into planning

    Retrospectives are the best thing you can do to help your team work better together. During a retrospective, you're asking your team to be open and honest about how things went over the course of the sprint so that you can learn from each other.

    Failing to learn from those insights means that the collective time spent in the retrospective has been wasted, and the feedback that your team has shared is devalued.

    Incorporating the learnings you gain from a retrospective into your next planning session and into the next sprint, will support your team to improve every time, helping them gain work satisfaction and deliver better outcomes.

    Virtual vs. in-person sprint planning

    The advantages of remote work also bring challenges for collaborative planning. No matter the way your team chooses to meet, whether virtually, in person, or a combination of both, it’s important that you choose tools that meet the needs of your team.

    Tips for virtual sprint planning:

    • Be really prepared - communicate plans clearly ahead of time, so that everyone has clear expectations.
    • Use a video conferencing tool that allows for breakout sessions
    • Set up the interactive online resources you plan to use and include links in the meeting request.
    • Online discussions don’t start as naturally as they would in person, so share discussion topics ahead of time, and consider preparing some ice-breakers.
    • Ensure that you’ve accounted for time differences for teams that span time zones.
    • Tech issues arise no matter how much advanced planning and testing you do. Always expect the unexpected.

    Tips for in-person sprint planning:

    • Book a meeting room with plenty of space for your team, and consider separate spaces for breakout sessions.
    • Ensure that your meeting room will accommodate a shared view of your sprint plan - do you need a wall for sticky notes, or a screen to share a digital tool?
    • If some of your team members work remotely, it’s difficult to involve them in the same way, so consider how this might work for your team. They won’t be able to read a whiteboard or sticky notes as easily, so a digital solution may be best.
    • If you choose to plan your sprint ‘on the wall’, be sure to nominate someone to transcribe your plan into your work management tool at the end of the planning meeting.

    No matter where your planning takes place, always remember to prepare your backlog ahead of time so that you can have focused and informed discussions during sprint planning.

    Additional agile resources

    We’re continually adding to our content library, which is filled with resources, how-to guides, product updates, and more.

    📚 Add these to your list:

    Using Easy Agile to improve sprint planning

    Make your sprint planning smooth and effective with Easy Agile TeamRhythm. Transform your flat product backlog into a dynamic, flexible, and visual representation of the work to be done. Seamlessly integrated with Jira, with TeamRhythm you can:

    • View your Jira stories, tasks, and bugs in context, aligned beneath their epics on the story map
    • Drag and drop Jira issues from the backlog into a sprint
    • Create new issues right on the story map
    • Estimate issues on the story map, and gauge capacity with story point totals in each sprint swimlane
    • Publish the sprint goal on each sprint swimlane, so it’s always top of mind
    • Use filters to focus on the stories and issues that are most important now
    • Group epics by a third level of hierarchy, to easily see how the work in focus contributes to the bigger picture

    Easy Agile TeamRhythm also supports team retrospectives, with flexible and intuitive retrospectives boards created for every sprint. You can add retrospective items right from the sprint swimlane, so you don’t forget any important points. And you can turn retrospective action items into Jira issues that can be scheduled for future sprints, so you’re always getting better at what you do, and delivering for your customers.

    Thanks for reading our ultimate agile sprint planning guide! If you have any questions about this guide, our other content, or our products, reach out to our team at any time. We love hearing from you.

    We’ll continue to update this guide as we gain more agile planning insights, techniques, tools, and best practices.

  • Workflow

    The Ultimate Guide to PI Planning

    You may be just starting out, or you may have worked with agile methodologies for a while, but we’re sure you can agree that scaling agile in a large organization can be daunting. PI Planning is key to scaling agile, so we’ve developed this guide to help you run successful planning sessions, and build your confidence for your next scaled planning event.

    We'll cover:

    Let’s start with the basics…

    What is PI Planning?

    PI Planning stands for Program Increment Planning.

    PI Planning sessions are regularly scheduled events where teams within the same Agile Release Train (ART) meet to align and agree on what comes next. Teams will aim to align on goals and priorities, discuss features, plan the roadmap, and identify cross-team dependencies.

    The goal is to align the teams to the mission and each other. Here are the essential elements of PI Planning:

    • 2 full day events run every 8-12 weeks (depending on the length of your increments)
    • Product Managers work to prioritize the planned features for the increment beforehand
    • Development teams own user story planning and estimation
    • Engineers and UX teams work to validate the planning

    Why do PI Planning?

    PI Planning is incredibly beneficial for large-scale agile organizations. PI Planning enables:

    • Communication
    • Visibility
    • Collaboration

    To understand the impact, let’s look at an example of a large organization that hasn’t yet implemented PI Planning. This organization has 250 teams and 6,500 team members. These teams rarely speak to each other, outside of dealing with a critical issue that has forced them to collaborate.

    Alignment across these teams happens at the leadership team level, and they have multiple levels of managers in between who cascade information down with varying success. There is a constant battle for resources, budget, and opportunities to work on the most exciting projects.

    Their projects have a habit of conflicting - one team would release something and then it would break something in another team’s project.

    PI Planning is the first time many big companies get their teams together in a room or on the same call to talk to each other. This is a chance to have important conversations about who is working on what.

    Why is this important?

    1. When you’re touching a system or a code repository, you need to know how it’s going to impact another team
    2. You might need to do some work to enable another team to work on their feature first (and vice versa)

    With proper planning and collaboration, teams can get things done more effectively, release with more predictability, and stay on budget.

    All very good reasons to do PI Planning.

    What is the goal of PI Planning?

    PI Planning is an essential part of the Scaled Agile Framework, a framework that’s designed to bring agile to large companies with multiple teams.

    SAFe PI Planning helps teams in the Agile Release Train (ART) synchronize, collaborate, and align on workflows, objectives, releases, and more.

    Without PI Planning, teams don’t have structured communication. They may not know what the other teams are working on, which can cause a lot of problems. For example, two teams might be working on different features without realizing there’s a dependency, which could hold up the release or require a significant rework of the code.

    The goal of PI Planning is to have all your teams aligned strategically and enable cross-team collaboration to avoid these potential problems.

    Now that we’ve covered off the “why”, let’s dig a bit deeper into the “what”. The best way to get a picture of what happens during PI Planning is to take a look at an agenda.

    What should be included in the PI Planning agenda?

    Here’s a standard PI Planning agenda template:

    Day 1 AgendaDay 2 Agenda8:00 - 9:00 | Business Context8:00 - 9:00 | Planning Adjustments9:00 - 10:30 | Product/Solution Vision9:00 - 11:00 | Team Breakouts10:30 - 11:30 | Architecture Vision and Development Practices11:00 - 13:00 | Final Plan Review and Lunch11:30 - 13:00 | Planning Context and Lunch13:00 - 14:00 | ART Risks13:00 - 16:00 | Team Breakouts14:00 - 14:15 | Confidence Vote16:00 - 17:00 | Draft Plan Review14:15 - ??  |Plan Rework?17:00 - 18:00 | Management Review and Problem Solving?? | Planning Retrospective and Moving Forward

    Source: scaledagileframework.com/pi-planning

    This agenda might be perfect for you, or you might make changes based on the needs of your teams.

    Distributed teams, very large ARTs, and other factors might require you to be creative with the schedule. Some sessions may need more time, while others can be shortened. If you have teams in multiple time zones, your PI Planning agenda may need to go over 3-4 days. If it’s your first PI Planning event, try the standard agenda, get feedback from your teams, and experiment with different formats next time.

    What happens in the first part of the PI Planning meeting?

    The first part of the PI Planning meeting is designed to set the context for the planning that happen next.

    Day 1 usually kicks off with a presentation from a Senior Executive or Business Owner. The agenda allows an hour to talk about the current state of the business. They highlight specific customer needs, how the current products address these needs, and potential gaps.

    After that, the Product Management team will share the current vision for your product or solution. They’ll talk about any changes that have occurred since the last PI Planning session (usually around 3 months prior). They’ll describe what’s coming up, including milestones and the next 10 features that are planned. This session should take around 1.5 hours.

    Why is a confidence vote held at the end of PI Planning?

    The confidence vote is a seemingly small but very important part of PI Planning towards the end of the event.

    It is important the team is confident in committing to the objectives and work that is planned. The Release Train Engineer will ask teams to vote on this.

    Everyone participating in planning needs to vote. This could be via a raise of hands (and fingers) or it could be via the tool you’re using. For example, the Team Planning board in Easy Agile Programs allows each team member to enter their confidence vote.

    If the average vote across the room is at least three out of five, the plan is a go-ahead. If it’s less it’ll need reworking (until it reaches a high confidence level). If anyone votes just one or two, they’ll have the chance to share their reasoning.

    The confidence vote is all about making sure that the attendees are in alignment and that they agree that the plan in its current form is possible within the given timeframe. Speaking of timing, let’s talk about how and where PI Planning actually fits into your company calendar.

    When is PI Planning held?

    Many companies find that 8-12 weeks (which adds up to 4-6 x 2-week iterations) is the right amount of time for an increment.

    Some companies hold quarterly PI Planning, for example:

    • Q1 PI Planning: December
    • Q2 PI Planning: March
    • Q3 PI Planning: June
    • Q4 PI Planning: September

    However, the timing and frequency will depend on how long each program increment is scheduled to last and may need to accommodate holidays.

    The good thing about PI Planning events is that they happen regularly on a fixed schedule, which means you can plan for them well ahead of time. That means teams and Business Owners have plenty of notice to ensure they can show up for the event.

    This means that what happens in preparation for PI Planning can be just as important as the event itself.

    What is a pre-PI Planning event and when is it needed?

    A pre-planning event - separate to PI Planning - is to make sure that the ART is aligned within the broader Solution Train before they do PI Planning. It’s all about synchronizing with the other ARTs to ensure the solution and organization are heading in the right direction, together.

    You’ll need to organize a pre-PI Planning event if you’re operating at the Large Solution, Portfolio, or Full SAFe levels. Essential SAFe is more basic and does not have a Solution Train, so if you’re operating at this level, you won’t need pre-PI Planning so formally.

    Here are a few of the roles that should be invited to the pre-planning event:

    • Solution Train Engineer
    • Solution Management
    • Solution Architect/Engineering
    • Solution System Team
    • Release Train Engineers
    • Product Management
    • System Architects/Engineers
    • Customers

    They’ll look at the top capabilities from the Solution Backlog, Solution Intent, Vision, and Solution Roadmap. It’s really a lot like PI Planning but at a higher level, across the overall solution and not just the individual ART.

    The event starts with each ART summing up their previous program increment and accomplishments to set the context. Next, a senior executive will brief the attendees on the current situation before Solution Management discusses the current solution vision and any changes from what was shared previously. Other things that are often discussed or finalized include:

    • Roadmaps
    • Milestones
    • Solution backlogs
    • Upcoming PI features from the Program Backlog

    In the next section, we'll help to define a few key terms that have been touched on.

    PI Planning in SAFe

    If you’re adopting SAFe for the first time, chances are it will start with PI Planning. That’s because it forms the foundation of the Scaled Agile Framework.

    As Scaled Agile says, "if you are not doing it, you are not doing SAFe."

    Definition:

    SAFe or the Scaled Agile Framework™ is a series of guidelines and practices designed to help bring agility into larger organizations, across all teams and levels of the business. The framework is geared at improving visibility, alignment, and collaboration and should lead to greater productivity, better results, and faster delivery.

    Whether you’re adopting all 5 levels or just essential SAFe, the foundation of your transformation and the driver for everything is the PI Planning ceremony.

    Scrum and Kanban are also agile frameworks (that you may be more familiar with), and these have historically been very effective at the individual team level. SAFe helps to scale agility across teams; to have multiple teams come together to work on the same products, objectives, and outcomes. It goes beyond the team level to include every stakeholder, outlining what should happen at each level of the organization to ensure that scaled planning is successful.

    The purpose of SAFe is to improve the visibility of work and alignment across teams, which will lead to more predictable business results.

    This is increasingly important for organizations as they respond to changing circumstances and customer expectations. The traditional waterfall approaches fall short because they’re slow and inefficient.

    Bigger companies (often with thousands of developers) can’t keep up with the innovation of smaller, more nimble startups. Along with bigger teams, larger organizations often have stricter requirements around governance and compliance, making it more complex to launch a new feature and deliver new value to customers.

    These companies are looking for new ways to organize people into projects and introduce more effective ways of working that use resources more effectively and provide more predictable delivery. If they don’t, they may not survive.

    SAFe is a way for these companies to start moving in a more agile direction.

    PI Planning is a vital element of SAFe. It’s a ceremony that brings together representatives from every team to help them work together, decide on top features to work on next, identify dependencies, and make a plan for the next Program Increment. As a result, there’s greater visibility across all the teams, changes are made more frequently, and teams work with each other - not against each other. From there, these massive companies can speed up their processes, work more efficiently, compete with newer and more nimble companies, and stay viable.

    SAFe and PI Planning are powerful enablers for organizational agility.

    While SAFe is a framework designed for larger organizations, there isn't a reason stopping smaller companies from doing a version of PI Planning, too. All you need is more than one agile team to make it worthwhile.

    PI Planning in Scrum

    You can also use PI Planning as part of a simple Scrum approach.

    Scrum Framework diagram shows when and how scrum teams can implement PI Planning

    Scrum Framework diagram shows when and how scrum teams can implement PI Planning

    Source: Scrum.org

    Scrum is an agile framework that helps teams get things done. It’s a way for teams to plan and organize their own work and tackle user stories and tasks in smaller time boxes. This is often referred to as a sprint.

    If multiple scrum teams want to work better together (but aren’t necessarily operating within SAFe), they could adopt a version of PI Planning.

    For example, these scrum teams could:

    • Meet every 10 weeks and discuss the features they are planning to work on
    • Get product managers to combine backlogs and prioritize together
    • Share resources across the teams, as needed
    • Map dependencies and coordinate joint releases

    The good news here is that there’s no “one size fits all” approach to PI Planning, so think about how you could adopt the ideas and principles and make it work for your organization and context.

    What is the difference between a PI Roadmap and a Solution Roadmap?

    There are different types of roadmaps in SAFe, so it’s important to understand the differences and what each roadmap is meant to do.

    PI Roadmap

    A PI Roadmap is created before your PI Planning event and also reviewed and updated by Product Management after the event is finished. It will usually cover three Program Increments:

    1. The current increment (work that’s committed)
    2. The next forecasted increment (planned work based on forecasted objectives)
    3. The increment after that (further planned work based on forecasted objectives)

    Quarterly PI Planning will outline around 9 months of work. The second and third increments on your PI Roadmap will likely change as priorities shift, but they’re still an important part of the roadmap as they forecast where the product is headed next.

    Solution Roadmap

    The Solution Roadmap is a longer-term forecasting and planning tool for a specific product or service.

    It will usually cover a few years at a time, with more specific details available for year one (like quarterly features and capabilities), and more general information (like objectives) for year two and beyond.

    What is a program?

    A program is where agile teams are grouped together to form a larger group. This is often referred to as the “team-of-teams” level. In simple terms, a program is a group of agile teams.

    When you hear people talking about “team-of-teams” or “scaled agile”, they mean taking agile beyond a single team, and asking more teams to join in.

    For example, there might be 4 teams working on a NASA spaceship mission to Mars.

    NASA decides they want to see if agile can help these teams do better work. So, to start with, the Oxygen team switches from working with traditional Waterfall project management methods to embracing agile principles.

    1. Launch team
    2. Food team
    3. Oxygen team (Agile)
    4. Landing team

    After a few months, NASA decides that the way the oxygen team is working is going well, so the remaining three teams similarly adopt more agile methodologies:

    1. Launch team (Agile)
    2. Food team (Agile)
    3. Oxygen team (Agile)
    4. Landing team (Agile)

    Each of these 4 teams are self-organizing, meaning they’re responsible for their own work.

    However, now that these teams are all working in the same way, they can be grouped together as a program.

    Once you add in the business owners, product management team, systems architect/engineer, and release train engineer, you have all the roles needed to continuously deliver systems or solutions through the Agile Release Train (ART).

    What is a program board?

    Program Boards are a key output of PI Planning.

    Traditionally, they’re a physical board that’s mounted on the wall, with columns drawn up to mark the iterations for the increment, and a row for each team. Teams add sticky notes that describe features they’ll be working on.

    • Feature 1
    • Feature 2
    • Feature 3

    Once all the features are added, they work to identify dependencies (features that’ll affect other features) and mark this up by connecting them with red string.

    SAFe program boards don’t have to be physical, though. There are a lot of advantages to using a digital program board like Easy Agile Programs, which integrates directly with Jira. We’ll talk more about how you can use Jira for PI Planning towards the end of this guide.

    Equip your remote, distributed or co-located teams for success with a digital tool for PI Planning.

    Easy Agile Programs

    Free Trial

    Who is involved in PI Planning?

    There are 5 key roles in a PI Planning event:

    1. Release Train Engineers
    2. Product Managers
    3. Product Owners
    4. Scrum Masters
    5. Developers

    Here are the responsibilities for each of these roles during PI Planning:

    Release Train Engineer

    The Release Train Engineer is a servant leader and coach for the ART. Their role focuses mainly on planning and facilitating the PI Planning event. This means they help:

    • Establish and communicate the annual calendars
    • Get everything ready (including pre and post-PI Planning meetings)
    • Manage risks and dependencies
    • Create Program PI Objectives from Team PI Objectives and publish them
    • Track progress towards expected goals
    • Ensure strategy and execution alignment
    • Facilitate System Demos

    As the facilitator for the 2-day event, the Release Train Engineer presents the planning process and expected outcomes for the event, plus facilitates the Management Review and Problem Solving session and retrospective.

    Product Manager

    A Product Manager’s job is to understand the customers’ needs and validate solutions, while understanding and supporting portfolio work.

    Before PI Planning happens, Product Managers take part in the pre-PI Planning meeting, where they discuss and define inputs, objectives, and milestones for their next PI Planning events.

    In PI Planning, the Product Managers present the Program vision and upcoming milestones. So that they can manage and prioritize the flow of work, they review the Draft plan and describe any changes to the planning and scope based on the Management Review & Problem Solving session. Once the PI Planning event is over, they use the Program Objectives from the Release Train Engineer to update the roadmap.

    Following PI Planning, Product Managers play a critical role in communicating findings and creating Solution PI Objectives.

    Product Owner

    The Product Owners are responsible for maintaining and prioritizing the Team Backlog, as well as Iteration Planning. They have content authority to make decisions at the User Story level during PI Planning Team Breakout sessions.

    Product Owners help the Team with defining stories, estimating, and sequencing, as well as drafting the Team’s PI Objectives and participating in the Team Confidence Vote. They’re also responsible for conveying visions and goals from upper management to the team, as well as:

    • Reporting on key performance metrics
    • Evaluating progress, and
    • Communicating the status to stakeholders

    Scrum Master

    The Scrum Master is a servant leader to the Product Owner and Development team, which means they manage and lead processes while helping the team in practical ways to get things done.

    They facilitate preparation for events (including PI Planning) and prepare System Demos. They help the team estimate their capacity for Iterations, finalize Team PI Objectives, and manage the timebox, dependencies, and ambiguities during Team Breakout sessions. The Scrum Master also participates in the Confidence Vote to help the team reach a consensus.

    Developer

    Developers are responsible for researching, designing, implementing, testing, maintaining, and managing software systems.

    During PI Planning, they participate in Breakout sessions to create and refine user stories and acceptance criteria (alongside their Product Owner) and adjust the working plan. Developers help to identify risks and dependencies and to support the team in drafting and finalizing Team PI Objectives, before participating in the Team Confidence Vote.

    Do you have a key role in PI Planning? See how the right tool can help you manage your release train or program better.

    Watch an Easy Agile Programs product demo

    How to prepare for PI Planning

    If you want to succeed at PI Planning, you need to prepare.

    Every PI Planning event relies on good preparation so that your organization and attendees get the most out of the event and achieve your planning objectives.

    The first step is to ensure that everyone involved properly understands the planning process. All people participating in PI Planning (along with key stakeholders and Business Owners) must be clear on their role and aligned on strategy.

    Any presenters will also need to get content ready for their presentations.

    To ensure that the PI Planning event runs smoothly, make sure that the tools you need to facilitate planning are available and working properly. Be sure to test any tech that you are relying on ahead of time (including audio, video, internet connectivity, and access to PI Planning applications), to ensure that your distributed teams can participate in the PI Planning event. Don’t forget to plan for enough food for everyone, too (planning is hungry work).

    What happens after PI Planning?

    After PI Planning, teams do a planning retrospective to discuss:

    • What went well
    • What went not-so-well
    • What could be better for next time
    • There will also be a discussion of what happens next, which can include things like:
    • Transcribing the objectives, user stories, and program board into your work management tool (like Jira)
    • Agreeing on meeting times and locations for daily stand-ups and iteration planning
    • Making sure that everyone has their belongings and leaves the event rooms clean when they go

    The other thing that usually happens after PI Planning events is a post-PI Planning event.

    What is a post-PI Planning event?

    These are similar to the pre-PI Planning events we looked at earlier. A post-PI Planning event brings together stakeholders from all ARTs within the Solution Train to ensure they’re synchronized and aligned.

    Post-PI Planning happens after all the ARTs have completed their PI Planning for the next increment. They present the plans, explain their objectives, and share milestones and expected timelines.

    Like PI Planning events, post-PI Planning involves using a planning board, but rather than features, it outlines capabilities, dependencies, and milestones for each iteration and ART. Potential issues and risks are identified, discussed, and either owned, resolved, accepted, or mitigated. And similar to regular PI Planning events, plans go through a confidence vote to ensure they meet the solution’s objectives, and are reworked until the attendees average a vote of 3 or more.

    Remote or hybrid PI Planning

    PI Planning in person was once standard, but with teams more likely to be distributed, gathering everyone at the office isn't always feasible. This doesn't have to be a barrier.

    The most important principle is to ensure that the teams who are doing the work are able to be 'present' in the planning in real-time, if not in person.

    This may require some adjustments to the agenda and timing of your planning, but with forethought and support from the right technology, your PI Planning will still be effective.

    Tips for remote PI Planning

    Remote PI Planning is ideal for organizations with distributed teams or flexible work arrangements. It’s also a lot cheaper and less disruptive than flying folks in to do PI Planning every few months. If you have the right tools and technology, you can run PI Planning and allow everyone to participate, whether they’re in the same room or on the other side of the world.

    Here are a few tips for remote PI Planning:

    Embrace the cloud

    Use online shared planning tools to allow your team to access and interact with information as soon as possible - ideally in real-time. Ensuring that all participants have instant access to the information simplifies the process of identifying dependencies and maintaining a centralized point of reference for your planning. This helps prevent errors that arise from working with different versions and transferring data between sources.

    Livestream the event

    Live-streaming audio and video from the PI Planning event is a viable alternative to in-person planning. Actively encourage your remote team members to use their cameras and microphones during the event. While it may not fully replicate the experience of having them physically present, it does come remarkably close.

    Record the PI Planning event

    Ideally, everyone will participate in the PI Planning live. But if your teams are distributed across multiple time zones or some team members are ill, it’s a good idea to record the event. Having a recording to refer back to could also be useful for attendees who want a refresher on anything that has been discussed.

    Be ready to adapt

    Some teams will change the standard PI Planning agenda to fit multiple time zones, which could mean starting the event earlier or later for some, or even running it across 3 days instead of 2.

    Set expectations

    A common issue that can arise from having distributed teams tune in remotely is too much noise and interference. Before your first session kicks off, communicate about when it’s acceptable to talk and when teams need to use the mute button. That way, your teams will avoid getting distracted, while still ensuring everyone can participate.

    For more tips, check out our blog on how to prepare for distributed PI Planning.

    Whether distributed or in person, if your team gets PI Planning right, it makes everything in the upcoming increment so much easier.

    📣 Hear how PNI media have embraced virtual PI planning

    Common PI Planning mistakes

    PI Planning doesn’t always run smoothly, especially the first time. And the framework itself may present a challenge to some organizations. Here are some common mistakes and challenges to keep in mind (and avoid):

    Long, boring sessions

    Avoid starting your PI Planning event with long sessions filled with dense content. Think of creative ways to make these sessions more engaging, or break them into shorter sessions. Consider different formats that help to involve and engage participants. And be sure to make room for team planning and collaboration.

    Tech issues

    Any event is vulnerable to technical mishaps, but if you’re streaming audio and video to a distributed team, this can really impact the flow of the event. It’s a good idea to carefully test all the equipment and connections ahead of time to minimize potential problems.

    Confidence vote

    Some PI Planning participants struggle with the confidence vote concept. People may feel pressure from the room to vote for a plan to go ahead, rather than speaking up about their concerns. Failing to address issues early only increases the risk of something going wrong during the increment.

    Time constraints

    When you have a large ART of 10 or more teams, there are a lot of draft plans to present and review, so less time is allocated to each team. Chances are that the feedback will be of poorer quality than a smaller ART with 8 teams.

    Not committing to the process

    PI Planning isn’t perfect and neither is SAFe. However, the process has been proven to work for many organizations, when the organization is committed. Start with the full framework as recommended; you can adapt the framework and your PI Planning event to suit your organization, but be sure to commit to the process that follows. Anything that is half-done will not deliver full results.

    Sticking with the same old tools

    If something is not working, fix it. For example, too many teams stick with traditional SAFe Program Boards even though they’re not always practical. If the post-it notes keep escaping, the data entered into Jira seems incorrect, or you have a distributed team who want a digital way to be part of your PI Planning event… it’s time to upgrade to a digital program board like Easy Agile Programs.

    Using Jira for PI Planning

    Jira is the most popular project management tool for agile teams, so chances are you're already using it at the team level.

    When you need to scale team agility as part of an ART, it can be difficult to properly visualize the work of multiple teams in Jira. The only way you can do that in the native app is by creating a multi-project board, which is rather clunky.

    Traditional PI Planning on a physical board using sticky notes and string may achieve planning objectives for co-located teams, but what happens next? After the session is over, the notes and string need to be recreated in Jira for the whole team so that work can be tracked throughout the increment. This is a cumbersome and time-consuming process that is open to error as sticky notes are transcribed incorrectly, or go missing.

    The best way to use Jira for PI Planning is to use an app like Easy Agile Programs to help you run your PI Planning sessions. The integrated features mean you can:

    • Set up a digital Program Board (no more string and sticky notes!)
    • Do cross-team planning
    • Visualize and manage cross-team dependencies, create milestones
    • Identify scheduling conflicts to mitigate risks
    • Get aligned on committed objectives for the Program Increment
    • Visualize an Increment Feature Roadmap
    • Conduct confidence voting
    • Transform Jira from a team-level tool to something that’s useful for the whole ART

    Join companies like Bell, Cisco, and Deutsche Bahn who use Jira to do PI Planning with Easy Agile Programs (from the Atlassian Marketplace).

    Looking for a PI Planning tool for Jira?

    We’ll continue to revisit this guide in the future. If you have any questions about PI Planning or you notice there’s an aspect we haven’t covered yet, send us an email 📫

Text Link

The problem with Agile estimation

Estimation is a common challenge for agile software development teams. Story points have become the go-to measure to estimate...

Text Link

The problem with Agile estimation

Estimation is a common challenge for agile software development teams. Story points have become the go-to measure to estimate...