Would you like to see some example uses for the PI Integration for JIRA? We did, so we made a video.
The PI Integration for Jira
This integration allows each team to live in the application that's right for them. This video offers several examples of rolling up JIRA data into Project Insight, so your PM team gets oodles of project data in PI. Let's bring this graphic to life:
You can skip ahead to the minute mark on your screen to see the specific example. We'll look at the following example uses.
- Building a Task List and Work Breakdown Structure in PI to make JIRA issues
- The other way around, pushing JIRA issues into a PI task list
- I'll show you what it looks like while the Dev team works in JIRA and how that shows up in PI
- Finally, you'll see some examples of how PI becomes the system of record through reports
So let's start by building a task list in Project Insight. That is a sweet Task List. It has work hours, duration, predecessors, and resources - all those PMBoK best practices! Meanwhile, back in JIRA, build a project shell and give it a name. I'll need that project shell in JIRA to sync the two projects and make them talk to each other.
So in this example, I can go to the Project Views and select "PI Integration Connections". Once there, select the project to sync from your "Available JIRA projects:" drop down and click Connect to JIRA.
I'll see that my tile switches to the JIRA project options. There is a link to the JIRA project, and JIRA to PI Project Options. Let me draw your attention to "Create PI Summary task called JIRA issues"... In this example, I chose this option because I already have a project plan. I want visibility into those new issues created over on the JIRA side, but I don't need them integrated into my plan. I would rather see them at the bottom of my plan in their own summary task.
On the JIRA side, the project settings over in JIRA look like this: Visit the Summary section of your JIRA project to see you've sync'd this project over on the PI side. The owner of the JIRA project does have options to add new PI tasks automatically. We recommend these settings for maximum communication and visibility.
Putting it all together, here's my neat WBS in Project Insight on the left, and you see the mirrored list of JIRA issues on the right.
An example of the JIRA summary task setting: If I add something to my JIRA project, example here is "I found something else". You'll see the JIRA issue becomes at PI task underneath the JIRA summary task called "JIRA Issues". This keeps those tasks visible to the PM, but separate from the project plan unless I hook them into my plan using predecessors and drag/drop options.
NEXT: Building the project in JIRA first, so if I'm on the Dev side and I've build this project called "Dev's Hard Work". It's easy to create that project in PI because all I have to do is
go to the Summary view of this JIRA project, and click the Add to PI button. That's it. We create the project in PI according to your global app settings. You'll see the Project Insight - Options section to display the link to PI's project, and I can make any changes to the JIRA settings here.
Over on the Project Insight side, I can see that the project view that once was "PI Integration Connections" has now defaulted to JIRA as an option. I have the same ability to make PI project options. Since I am using JIRA as my primary source for this project, I have chosen to select the option to "Maintain the JIRA hierarchy, epics, etc in the PI task list". I want this PI project to reflect any changes to the JIRA project, line for line.
You'll see the Dev's Hard Work list in JIRA on the left mirrored over in Project Insight on the right.
Now for the integration points, while working in your system of choice. Here I am working in JIRA and I add a comment, for example. JIRA shows me I added a comment in their running list of notifications. And the JIRA resource moves on.
Meanwhile, in Project Insight, those comments sync over in real time to show the PM. These comments behave like PI comments - the only difference is the author will be JIRA if the JIRA/PI users are not sync'd correctly.
Similar example, if I make a change in JIRA to the Progress or Done buttons. JIRA shows me you've updated the task.
Over in Project Insight, I'll get the Work Status to change (as long as I've mapped my PI Work Statuses and JIRA work statuses) and it will populate the actual end date based on today's date. Although, I have not show the example of time entries visually, time entries come over from JIRA to Project Insight in the same way. Each update to the hours in JIRA makes an individual time entry in Project Insight.
Because the data automatically shows up from JIRA and into Project Insight in real time, you can run your typical PI reports with data populated from your users in JIRA. You can still see Resource Allocation based on the scheduled dates and level of effort recorded in JIRA.
You can track "Actual Hours vs. how far along in the project vs the planned hours" using data provided by the JIRA users.
Or another example is the month by month breakdown of how many hours we thought we'd work on our projects vs actual hours recorded against these projects. All of this information can include projects primarily managed in JIRA alongside projects managed in Project Insight - because we're syncing that data and providing that visibility through the PI Integration for JIRA.
So what's your call to action here? Download the PI Integration for JIRA today - it's in your Admin section right now under GET APPS AND ADD ONS. It's free, so go get started.