+++ How to Combine Project Management with JIRA and Microsoft Project +++ Connecting Microsoft Project Server / Project Online with your Work Management System (JIRA or TFS) +++
By Johann Strasser Read article in German
If you are working with Microsoft Project Server / Project Online (PPM), you will already know this. It is a tool for project managers, optimized to plan projects with tasks and work packages in a structured way.
But it does not lend itself well to the detailed depiction of many little and personal jobs below tasks. Tools such as Atlassian JIRA or Microsoft TFS are much better suited for this. With these tools, detailed issues can also be planned in sprints and iterations.
So how can the two worlds be linked up again? And what are the advantages of an integration such as the MS Project-JIRA integration?
Using four classic business cases, this article aims to show what you gain by integrating project and work management.
Please note: The business cases presented here can only be realized with Microsoft Project Server or Project Online (PPM). Moreover, the business cases use the interface product TPG PSLink. It permits the realization of different scenarios. In these scenarios, either the user triggers the data exchange; or automated jobs run in the background.
General Benefits of an Integration
The cross-system data exchange between MS Project and JIRA or TFS will provide the following benefits for all roles involved:
- Each role works with the system that is best for them
- Efficient provision of current information for all involved
- Reliable data as the best possible basis for work and decision-making
- Reduced effort and duration for planning and updating
- Multiple data entry is avoided
- Data consistency is ensured in all systems involved
MS Project-Jira integration is an example of hybrid project management. Find out more.
The ROI of your integration increases with the:
- Number of integrated systems
- Amount of data
- Number of persons involved
- Number of updates
Thinking about introducing a Project & Portfolio Management (PPM) solution? Read about 3 Approaches to the Task.
The following four business cases are described using the example of the integration of MS Project with JIRA. It is also very similar with TFS.
Business Case 1: Transferring the Structure from MS Project to JIRA
Each project manager requires a project structure providing optimal support for project control. It can differ depending on the type of project. IT, service, organizational, or development projects do not have the same structures.
Therefore, you should ask yourself the same question for each business case. How to assign the many small issues from JIRA to the tasks / work packages in the Microsoft Project plan?
Struggling with Program Management? Read these 8 Tips to Increase Success.
A 1:1 link only makes sense at the structural level into which the aggregated values of the detailed issues are synchronized with Microsoft Project.
The customer requirement we encounter most often is the connection of projects to versions and epics. As a rule, phases of the MS Project plan are represented as versions and work packages as epics. Issues are assigned to the epics in this case.
Special Download: Benefits of MS Project Server / Project Online to the MS Project Standard
Please click here to download the PDF and learn why you should prefer the server over the client version.
Further possibilities of structural alignment can be:
- Tasks in MS Project correspond to sprints in JIRA: The aggregated values of issues in the sprints are synchronized with tasks the in MS Project.
- Component-oriented plan in MS Project: The aggregated values of issues assigned to the components are synchronized with the tasks in MS Project.
In the case of changes to the project plan, these need to be transferred to JIRA, too. This applies to the structure as well as the dates and other additional information.
Business Case 2: Automated Population of Issues in JIRA
With standard projects, reverting to standardized issues can be useful in issue management. You should not have to enter these again each time. Ideally, they could be imported.
SharePoint is an excellent tool for providing a list of issues per project type in a simple way. For new projects, a suitable integration tool will allow you to carry this list over to JIRA at the push of a button. This will save you a lot of time.
As part of project control, the project manager needs to be informed on the progress of all deliverables at regular intervals.
He or she needs to know both the progress with regard to content and the efforts recorded. JIRA can provide both automatically when maintained properly.
This requires the team members to maintain e.g. story points on the one hand to illustrate the performance with regard to content. When closing issues, these story points are transferred back to the corresponding structure of the MS Project plan.
You might also be interested in: 7 Crucial Success Factors for Multi-Project Management
On the other hand, the team members enter the hours worked per issue. The result can also be transferred back to MS Project.
Of course, you can also synchronize the status of objects at the structural level. You transfer the status of the corresponding objects in JIRA back to MS Project.
The figure below shows you the:
- sum of the story points of the hitherto completed issues
- corresponding effort
- status of the higher-level epic
Seeing as a MS Project plan should be as lean as possible, we do not recommend realizing a 1:1 link between tasks and issues.
Still, the project manager may be interested in many of the details in JIRA. At the latest when uncertainties arise.
There is comfortable way for him or her to gain this insight without having to look for the details in JIRA. A suitable tool can enable them to display the details within MS Project at the push of a button.
This does not require an import into Microsoft Project Server / Project Online. Hence, the project plan remains lean!
This article has introduced you to four important business cases of MS Project-JIRA integration. Each of them would allow you to exchange data between Microsoft Project Server / Project Online (PPM), JIRA and SharePoint. Or to display data from one system in the other. The four cases concern the:
- Transfer of the structure from Microsoft Project to JIRA
- Automated population of issues in JIRA
- Reporting the progress from JIRA to MS Project
- Displaying issues in MS Project – without import
One Last Recommendation: There are cheap and established solutions only able to connect MS Project and JIRA. But most companies intend to do more than this integration. For them, it is a matter of connecting as many systems as possible in a meaningful way as part of digital transformation. Therefore, it makes sense to use middleware integrating and controlling many systems centrally. Other interesting systems could be ERP or CRM systems as well as further databases.
Do you have experience with integrated project and task management systems, such as MS Project-JIRA integration? How has the integration changed the way you work? Is there anything you would like to add? Please leave a comment below!
Final tip: Subscribe to the TPG Blog Newsletter now and never miss another blog post.