Please login or join to subscribe to this thread
We are using both. Both are for different proposes.
I would say Jira because I have seen it used in more environments than MS Project. Which would lead be to believe people are more familiar with it.
Good question. May I suggest that you experiment with both using something like Microsoft Teams or Slack as the platform where JIRA is integrated from? Tools such as Teams or Slack have a nice way of integrating tools such as JIRA and Trello with the addins that they would need for something like reporting or collaboration.
I agree with you that it lacks certain things, such as reporting tools, which MS Project already has. But JIRA is geared more towards Agile PM as opposed to Waterfall PM, so its features may be different.
I just noticed that if you go to this website, you might find more of what you are looking for with JIRA: https://www.atlassian.com/software/jira?ad...IwD4w&gclsrc=ds
I prefer JIRA for agile project environments, while MS Project best suits to cascade projects.
Hi Anne, I was the same as Sergio.
In previous organisation, JIRA was implemented as issues tracking tool across multiple teams, around 120users. What I like most is the dashboard gadgets it allows visibility on different dimensions - just need to pick an choose. Overall it fulfilled the project’s objectives. There is data mining capabilities also within JIRA but since this was out of scope for the project, I cannot comment further.
On planing/scheduling/organising tasks, MS project definitely still works best for me, I find it worked well for the team size and when changes are often.
Both of them require a lot of work to ensure all the data is entered for reporting anything meaningful. I've seen Jira tickets that have waaay too many fields. The person using the ticket puts in the bare minimum amount of information which is usually insufficient to be meaningful.
Don't think Microsoft Project is better. Unless you are using Project Server, you will be stuck entering the actual time for each resource and activity. Not a fun job.
You can use both to achieve information presentation needs. MS Project can provide you with schedule tracking and reporting for the overall integration of all work packages whereas JIRA will do a great job of tracking and reporting on the work at the individual sub-team level.
JIRA has good objective dashboards and native reports such as the version report for forecasting when a given release might be ready and control charts for continuous workflows or sprint burndown & velocity charts for sprint-based workflows.
They are really two distinct tools and can both be utilized, but to choose between the two would require an effort to identify the needs of the organization and the tool itself, then match those requirements with the best candidate.
My initial questions are; why does the organization want to move to Jira? What problem do they think Jira will solve?
To remind us, and although Jira has extended its functionality, at its core, it is an issue tracking system.
I like what Andrew said - It is not about the one being better than the other, it is about what problem you want to solve. Answer that question and you have your tool. Oh and just to be clear, the problem I believe is a bit more complex than just tracking a project.
Don't bother with MS Project if it is a software project, JIRA has all the reporting you need. If you need a scheduling tool use LucidChart and paint yourself a nice picture - seriously
Please login or join to reply