Some other tools have mechanisms built-in for this. Jira Align does not associate risks to teams which can make it difficult to filter the Risk Grid when presenting team risks for the Draft and Final Plan Reviews. This looks looks great ! Thanks for reaching out. Simple drag and drop is used to create and visualise cross-team dependencies. Thanks Jon, Teagan Harbridge Product Manager - Easy Agile. You've been invited into the Kudos (beta program) private group. There is nothing technically stopping you from scheduling any issue type onto the Program Roadmap such as your custom initiative/feature issue type. I've made sure to add your comments to the stories we have on our backlog around Risks. Program increment planning is the face-to-face event that plans out the … Interested in learning more about Easy Agile Programs for Jira? There are … Real-time Jira Sync. Thanks @RabbitTeagan Harbridge Product Manager - Easy Agile, Hi @Rabbit @Diane Roberts @Samantha Sieverling @Loshy Chandran. Each team’s draft plan is visible to the entire ART in the Increment Overview. I've added your comments to the story on our backlog and I'll make sure to keep you posted here.A few more questions from me: How do you calculate business value? We currently don't. This presentation is not restricted to team members being physically present during planning, and can be referred to throughout the entirety of the planning session. At the end of each day, it becomes someone’s job to enter this information into Jira, and, even after they do that, there is no native way to visually depict dependency relationships like the Spaghetti Board in Jira. However, we want to do away with spreadsheets and use a tool that has these capabilities. Ability to track the progression of the Program with distributed team members after the planning is finished . With Jira Align, everyone participating in PI planning has … Jira is an amazing app with tons of features agile teams can make good use of, but it may not offer the best solution to your specific use case. Physical PI Planning Session:During the tightly time-boxed session, teams present their plan to the ART and discuss scope, cross-team dependencies, and resources. Once work is planned, Product Owners and their development teams identify cross-team dependencies, which are communicated to the ART using string on a physical Program Board (Spaghetti Board). I've made sure to note that on the story on our backlog. (custom issue type, component etc. Check out our documentation here, or get in touch with one of our Atlassian Solution Partners. Teagan HarbridgeProduct Manager - Easy Agile. Each team’s draft plan will be stuck on a wall for all of the ART to see. PI Planning stands for Program Increment Planning. JiraMaximize the true potential of your PI by integrating JIRA with Kendis Azure Boards and TFS Seamlessly Integrate Microsoft Azure Boards and TFS with Kendis to enhance your PI Planning … How do you keep track of whether that business value is delivered (story points delivered, cost of project etc.)? Due to this lack of visibility into dependencies, Release Train Engineers will often roll up the physical Program Board and put it up on the wall outside their office. All changes made to issues in Easy Agile Programs are automatically reflected in Jira. This isn’t to say that … The colour approach is a great visualisation method, and I can see how we would go about implementing that approach.The only question I have then becomes, would you expect/want to be able to pull reports in Jira which looks specifically at PI risks? For specific solutions, such as integrated customer personas or a tool for PI Planning, you’ll need a Jira … Traditionally, we’ve seen this take place in a very physical sense: the 2 day planning session can see anywhere between 100 to 200+ members of an ART travel from all over the world to a single location where they plan out their next Increment of work. The Increment Overview is a digital representation of the physical Program Board created during the 2 day PI Planning session. Here, Product Owners and their teams set the capacity for each Sprint within their Program Increment. The ability for teams to facilitate cross-team planning and dependency management allows distributed teams to participate in digital PI Planning sessions. PI … I'm looking forward to hearing your feedback and insight and sharing it with our team. If we were to use the colour approach, we would not be conforming to a standard Jira primitive (i.e. The efficiency of planning within Jira. With the context of the Feature Roadmap at the top of their planning session, teams are able to pull in existing issues from their backlog or create new issues within the planning board to support Feature completion. Due to this lack of visibility into dependencies, Release Train Engineers will often roll up the physical Program Board and put it up on the wall outside their office. Get answers to your question from experts in the community, Share a use case, discuss your favorite features, or get input from the community, How to Run PI Planning in Jira - Helping make SAFe®, Easy, Try it for free now from the Atlassian Marketplace. Digitising this limits double handling of information, and also means we can track progress towards Feature completion in real time. If you’re reading this, then you’re officially on the train; the Agile Release Train (ART) that is — and you’re attempting to navigate the world of the Scaled Agile Framework® (SAFe®). Keep the benefits of physical stickies and paper boards, but without the hassle of transcribing all the handwritten notes at the end of your PI Planning event! One of the keys to the train running and delivering on time, is the execution of effective Program Increment Planning (PI Planning). I've added your vote and comments to the story on our backlog. We want to make the PI Objectives easily visible and accessible to the Business Owners throughout the PI Planning session.. ... Connect with like-minded Atlassian users at free events near you! Yes, Easy Agile Programs is available on Cloud today via the Atlassian Marketplace. We definitely would like to make the Program Increment Objectives more visible on the Increment Overview. Not ideal — particularly for distributed team members. Thank you too for your patience on this! The Increment Roadmap ensures all teams are aligned on the committed Features for a Program Increment, providing visibility into the direction of the Program for all stakeholders. We also have a story to support each team being able to create their own Team PI Objectives on their Team Planning Boards. Let’s walk through a typical PI Planning agenda and how we can support each agenda item using Jira + Easy Agile Programs, for face-to-face and distributed PI Planning. We are quite interested in your solution, it looks great!!. Currently Easy Agile Programs is only available on Server and Data Center although we do have plans to also make it compatible for Jira Cloud soon. One of the keys to the train running and delivering on time, is the execution of effective Program Increment Planning (PI Planning). During this process, teams identify dependencies, depicting them using pieces of string, stuck between post it notes on a shared Program Board. There are however, common pain points organisations face when conducting physical PI Planning sessions. Next, Product Management will present the current program vision, typically in the form of a list of the next top 10 upcoming Features. Divide and conquer. I will get back to you on. Teams can start the planning by pulling the features from the … One idea is to be able to change the color of the issue on the board. Program Increment (PI) Planning is part of the SAFe (Scaled Agile Frameworks), a regular routined event that occurs with a planning agenda for Agile Release Train teams to align on a shared mission and … Digitising this limits double handling of information, and also means we can track progress towards Feature completion in real time. Traditionally, we’ve seen this take place in a very physical sense: the 2 day planning session can see anywhere between 100 to 200+ members of an ART travel from all over the world to a single location where they plan out their next Increment of work. your questions as soon as I have the chance. Hi @Loshy ChandranThanks for reaching out and expressing interest in Easy Agile Programs for Cloud. Good news: with the right tools supporting you, distributed PI Planning can be successful AND stress-free. PI Planning Preparation The "RTE Cockpit" makes it extremely easy for you as a Release Train Engineer to prepare your PI Planning in a way so that your teams can enjoy a simple user interface during the … Is this tool available on Cloud version already (or going to be anytime soon)? This presentation is not restricted to team members being physically present during planning, and can be referred to throughout the entirety of the planning session. It's not useful to "edit" from the roadmap page and not be able to view that info from the "Overview", to refer to it. There are some current limitations with Next-Gen projects, namely the inability to access the Epic-Link via JQL. Must Product Owners and Scrum Masters be Archenemies? Either to change the color of the whole strip, or to at least have it outlined in red or something. These include: We’ve created a solution using Jira + Easy Agile Programs to digitalise physical PI Planning and ensure your Program Board lives on well after the strings fall off the wall. I would love to share some mockups of potential dashboards for you. The ability to inline edit issue estimates and summaries in real-time makes reworking the plan fast and simple. Thank you for your interest and patience while our team worked to bring you this Cloud compatible version. Hi @Jon FishmanReally appreciate you taking the time to answer my questions. Physical PI Planning Session:In the breakout, teams work individually to estimate the capacity for each Sprint in the Program Increment. We’ve created a solution using Jira + Easy Agile Programs to digitalise physical PI Planning … Business Owners kick off the event by giving a presentation on “the current state of the business and present perspective on how well existing solutions are addressing current Customer needs” (SAFe — PI Planning). Thanks for reaching out and we're excited to hear that you are interested in Easy Agile Programs! Take the practical approach and plan your Program Increments using laptop screens of your distributed team members. Unfortunately there are no Community Events near you at the moment. There is nothing better than having everyone in the same room for Program Increment (PI) planning. The Increment Roadmap ensures all teams are aligned on the committed Features for a Program Increment, providing visibility into the direction of the Program for all stakeholders. I hope that helps answer your question. Certainly helps us flesh out these stories on our backlog, so thank you. Please put me down for interest in the Cloud version once it comes out. Let’s take a quick tour of the PI planning process in Jira + BigPicture. Do you plan on having a feature to have a dashboard or something where velocity and predictability can be measured and displayed for the course of the increment? Are there any available APIs that your customers can make use of? To understand how to create team risks in Jira Align check out the Atlassian Community article by @Tom_O_Connor Create Team Risks in Jira Align. Overall, it's great. Would you expect Easy Agile Programs to take care of that calculation/progress? Hi Teagan, sorry for the delay. How do you currently assign business value to Objectives. Physical PI Planning Session:Next, Product Management will present the current program vision, typically in the form of a list of the next top 10 upcoming Features. Interested in learning more about Easy Agile Programs for Jira? There are however, common pain points organisations face when conducting physical PI Planning sessions. In order to do this, when creating a new Program, select the 3rd option under the Program Roadmap heading (as shown below): You will then be prompted to select your dedicated Roadmap board, as well as your Jira issue link type (that is, how you would like the stories scheduled in the Sprints by your teams to be linked up to your initiative/feature on the Roadmap).