THANK YOU Henrik! I needed some knowledge of TFS and Jira for tomorrow morning and I found your video making a huge difference for me. So Henrick, you should be proud of your work making this idea providing basic understanding of these 2 tools. Thank you.
switch to 2x speed guys, you can still follow clearly. Thank you Henrik for saving me a ton of time! Your effort in putting this video up has helped me a lot.
Thanks for the video! I have to choose between them for my job in a few weeks. I have always worked with Azure DevOps and I don't like to much Jira but in my job they use Jira for the ticketing system and makes more sense to use JIRA Softare instead of Azure DevOps. What tool do you choose now (having in mind that the video is a little bit old and maybe some changes have been implemented in those systems)?.
We use TFS and IMO it sucks at the work planning/tracking. We spend so much time hunting for lost work items and trying to make sure everything is up-to-date. What I want to know is whether the Jira UX is better. Or does it suck too ... probably in totally different ways. From your video you imply the two are more similar than different.
Excellent,do you have more videos on tfs,as i am starting new project soon and company is using tfs .if you have any detailed explanation please do let me know
Would have liked to see how each system manages traceability. Linking and traceability is very poor in JIRA, curious how it is in TFS. The ability to do impact analysis, gap analysis and understand how requirements link to tests, link to test executions, link to defects, link to source code is the foundation of a good ALM system.
Great video. However a mistake was said. In TFS, You can change a work item type to any type. docs.microsoft.com/en-us/azure/devops/reference/add-modify-wit?view=vsts
I think TFS is far superior than JIRA. I have used JIRA for over 10 years and TFS for under 2 years. TFS provides DevOps functionalities like integration with Jenkins, Maven, Code Coverage tools, Code review, Test Management, Build and Deployment. Haven't seen those with JIRA. TFS is a complete Application Life Cycle Management tool. It provides great support for Java stack not just Microsoft stack
Its not necessarily a "better" thing to integrate the project management tool with technical assets. Its arguable that in an agile project the tool used to store a product backlog should have as a primary objective to be tightly integrated with a technical solution. JIRA is a much better business oriented product, especially with confluence and gliffy integrations. IMO its doing a better job at describing a product from a business and architectural standpoint. Not saying that Continuous Integration & DevOps features are useless. You can have them on JIRA, probably with a bigger effort. But again, its all about the project context and what you want to prioritize.
Jira has no out-of-the box capacity planning and the existent plug-ins for it are poor. TFS rocks in capacity planning. In other hand, time-tracking in TFS is inexistent. JIRA rocks on it.
I would strongly warn people away from Jira. I have been using Jira since 2007 and have been an administrator for a number of years and have seen the mess that people have got into and the difficulty of configuration in Jira. If you go one way in Jira it is amazingly hard to change direction and fix problems. I have seen large customers in a total pickle. Also every integration point is either a cost or lots of work and most of the integration either crude, an additional cost. The querying language is non-standard and poor unless - yes you guessed it - you buy a plug in. I would only consider TFS or YouTrack and would never recommend Jira.
Cannot agree on this one. I'm working as a JIRA system administrator and as a PM since 2014, and most of the time reconfiguring boards, workflows, screens, issue types etc. is a very quick thing to do. Also, JIRA is _very_ flexible. Even without adding plug-ins you can configure quite anything in JIRA - but you don't have to if you like the default settings. In our agile team, we like to improve our task boards from time to time, and with JIRA, this is no problem at all. But there's more. What's not in the video, is that with JQL (JIRA Query language) you have a very powerful tool for easy filtering. You can add quick filters to your board - and you can use queries not only for filtering but also other things - like e.g. to specify a card color. And this is rad: Ever encountered an issue that had been closed without being merged? Now, our cards are marked red if they are closed without being merged. Or they're yellow if they have a due date within the next 3 days. Also, the Release Hub in JIRA is a great thing. You always have a quick overview on all releases, see what's changed and can access the issue list for each release (and see the code change for each issue if you have Bitbucket linked). There's another 'also': Some feature is missing? Something isn't working right? You can check back with the boards at Atlassian, request, comment on or vote for new features in JIRA (and other Atlassian tools). And there are tons of 3rd party plug-ins. And if need your own plug-in, you can simply write it yourself. My personal summary is: Pros: + JIRA is very easy to setup, very powerful and very flexible + Strong community + SDK for 3rd party plug-ins + Integrates very well with Confluence (very good wiki) and Bitbucket (Git store) + Project Managers get more and more power over configuration of their projects + Transparent feature (and bugfix) request boards at Atlassian Cons: - If you dive down to the deepest config area, it gets harder to keep grips on how all the configurable modules work together. But the approach is most of the times consistent, at least. So, once you got the point, you're good to go - Before Jira 7.x, you couldn't configure much at project owner level. For most things you had to be system admin. But they're changing this with the latest releases. - JIRA Server (runs on your own hardware) and JIRA Cloud seem to walk different paths, and JIRA Cloud seems to be the favourite child, nowadays. Which isn't that good if you have restrictions that prevent you from storing your data in the cloud.
THANK YOU Henrik! I needed some knowledge of TFS and Jira for tomorrow morning and I found your video making a huge difference for me. So Henrick, you should be proud of your work making this idea providing basic understanding of these 2 tools. Thank you.
switch to 2x speed guys, you can still follow clearly. Thank you Henrik for saving me a ton of time! Your effort in putting this video up has helped me a lot.
You made my life easy by comparing these two. I am Jira user till now and have to use VSTS from now.
Thanks for taking the time, that was really useful and presented in a very informative way!
Thanks Henrik. I am just starting an evaluation between JIRA & TFS so this was really helpful.
Thanks Henrik. I am just starting an evaluation between JIRA & TFS so this was really helpful.
Did you finish your evaluation, I am working for one as well
Hi, I am involved in the same type of task. So what was the end result?
Very nice feature in Jira, where you initially log everything as an issue and as things become clear you convert it to specific issue type.
A useful overview of the current state of these tools.
Thanks for the video! I have to choose between them for my job in a few weeks. I have always worked with Azure DevOps and I don't like to much Jira but in my job they use Jira for the ticketing system and makes more sense to use JIRA Softare instead of Azure DevOps.
What tool do you choose now (having in mind that the video is a little bit old and maybe some changes have been implemented in those systems)?.
unbiased and intelligent comparison. Thank you Henrik.
Very well done Henrik, thanks for sharing.
Superb stuff Henrik. Its really helpful :)
We use TFS and IMO it sucks at the work planning/tracking. We spend so much time hunting for lost work items and trying to make sure everything is up-to-date. What I want to know is whether the Jira UX is better. Or does it suck too ... probably in totally different ways. From your video you imply the two are more similar than different.
Very good Explanation,Thanks so much
I fail to understand why would VSTS keep extra layer of Features. Why it can't directly map the Epic to user story/product backlog item?
Great video. Lots of helpful information. Thanks!
excellent comparison well done henrik
Thank you Henrik. Great video.
Im wondering if TFS can do checksum or generate an MD5?
Great comparison. Thanks!
Excellent video Henrik Yillmo
Video is horrible, and terribly inaccurate. Issue and subtask are NOT the same level. :-D
Excellent,do you have more videos on tfs,as i am starting new project soon and company is using tfs .if you have any detailed explanation please do let me know
Would have liked to see how each system manages traceability. Linking and traceability is very poor in JIRA, curious how it is in TFS. The ability to do impact analysis, gap analysis and understand how requirements link to tests, link to test executions, link to defects, link to source code is the foundation of a good ALM system.
Great review. Factual without too much opinion! Thanks
Wow! Thank you for this video!
Great video, this has helped a lot to understand the relation in JIRA as compared to TFS. Thanks you
Nice, thank you
Great video, Thanks!
nice comparison, thank you
Cool comparison
great video thanks
Good comparison
very nice video . Thank u
helpful video!
I will just mention that installing Atlassian products is a pain in the .... :(
Great video. However a mistake was said. In TFS, You can change a work item type to any type. docs.microsoft.com/en-us/azure/devops/reference/add-modify-wit?view=vsts
I think TFS is far superior than JIRA. I have used JIRA for over 10 years and TFS for under 2 years. TFS provides DevOps functionalities like integration with Jenkins, Maven, Code Coverage tools, Code review, Test Management, Build and Deployment. Haven't seen those with JIRA. TFS is a complete Application Life Cycle Management tool. It provides great support for Java stack not just Microsoft stack
Its not necessarily a "better" thing to integrate the project management tool with technical assets. Its arguable that in an agile project the tool used to store a product backlog should have as a primary objective to be tightly integrated with a technical solution. JIRA is a much better business oriented product, especially with confluence and gliffy integrations. IMO its doing a better job at describing a product from a business and architectural standpoint. Not saying that Continuous Integration & DevOps features are useless. You can have them on JIRA, probably with a bigger effort. But again, its all about the project context and what you want to prioritize.
Nice explain indeed. Thank you for sharing it with us.
Jira has no out-of-the box capacity planning and the existent plug-ins for it are poor. TFS rocks in capacity planning. In other hand, time-tracking in TFS is inexistent. JIRA rocks on it.
Jira is G@RBAGE. For example workflow diagram is static withou following the history of states changes.
"jeeera"
I would strongly warn people away from Jira. I have been using Jira since 2007 and have been an administrator for a number of years and have seen the mess that people have got into and the difficulty of configuration in Jira. If you go one way in Jira it is amazingly hard to change direction and fix problems. I have seen large customers in a total pickle. Also every integration point is either a cost or lots of work and most of the integration either crude, an additional cost. The querying language is non-standard and poor unless - yes you guessed it - you buy a plug in. I would only consider TFS or YouTrack and would never recommend Jira.
Thanks, We are looking for an alternative product and I'm glad you brought up the admin issue, its a nightmare to work with.
Cannot agree on this one.
I'm working as a JIRA system administrator and as a PM since 2014, and most of the time reconfiguring boards, workflows, screens, issue types etc. is a very quick thing to do. Also, JIRA is _very_ flexible. Even without adding plug-ins you can configure quite anything in JIRA - but you don't have to if you like the default settings.
In our agile team, we like to improve our task boards from time to time, and with JIRA, this is no problem at all.
But there's more. What's not in the video, is that with JQL (JIRA Query language) you have a very powerful tool for easy filtering. You can add quick filters to your board - and you can use queries not only for filtering but also other things - like e.g. to specify a card color. And this is rad: Ever encountered an issue that had been closed without being merged? Now, our cards are marked red if they are closed without being merged. Or they're yellow if they have a due date within the next 3 days.
Also, the Release Hub in JIRA is a great thing. You always have a quick overview on all releases, see what's changed and can access the issue list for each release (and see the code change for each issue if you have Bitbucket linked).
There's another 'also': Some feature is missing? Something isn't working right? You can check back with the boards at Atlassian, request, comment on or vote for new features in JIRA (and other Atlassian tools).
And there are tons of 3rd party plug-ins. And if need your own plug-in, you can simply write it yourself.
My personal summary is:
Pros:
+ JIRA is very easy to setup, very powerful and very flexible
+ Strong community
+ SDK for 3rd party plug-ins
+ Integrates very well with Confluence (very good wiki) and Bitbucket (Git store)
+ Project Managers get more and more power over configuration of their projects
+ Transparent feature (and bugfix) request boards at Atlassian
Cons:
- If you dive down to the deepest config area, it gets harder to keep grips on how all the configurable modules work together. But the approach is most of the times consistent, at least. So, once you got the point, you're good to go
- Before Jira 7.x, you couldn't configure much at project owner level. For most things you had to be system admin. But they're changing this with the latest releases.
- JIRA Server (runs on your own hardware) and JIRA Cloud seem to walk different paths, and JIRA Cloud seems to be the favourite child, nowadays. Which isn't that good if you have restrictions that prevent you from storing your data in the cloud.
From tester perspective Jira is way better than microsoft TFS
TFS is expensive... you get what you pay for basically...
TFS is free for team of upto 5 people
Fantastic video ... Thank you