You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Many experts and experienced people in the Agile world are sceptical of tools like JIRA which are used in so many companies these days. I support most of their points too. Some of them for a discussion here (If there is a user voice list where we can request for features, please let me know). I'm posting here for now :
What do you all think ?
Well, TBH, It seems to be more excuses to me - considering the time that JIRA has existed now and the size of the market and the number of users (my current project has more than 15000 users in JIRA - you may calculate the money involved).
The chief complaint remains - that Atlassian has not tried to move more towards supporting the Agile principles while claiming lip service in their documentation and marketing materials.
The worse thing is that they don't seem to have any goal to move in that direction. The marketplace licensing thing is a total disaster. We have to buy 15000 licenses for an app which will be used by 25 people. It doesn't help us either on that front. JIRA may be better than some other tools in the market but being a market leader by a long distance, I expect them to Improve and show some leadership instead of blaming the past.
Not excuses, just an explanation of how Jira has ended up this way. They're not blaming the past either, they're just not explaining it much when they do new stuff, because they're focussed on improvement, looking forwards, not back.
>The chief complaint remains - that Atlassian has not tried to move more towards supporting the Agile principles
Um, no, if you re-read the answer I gave, you can see that it's the opposite - they've actively persued all the principles (to varying extents), but while trying to avoid building software that blocks people who are not (or don't really understand) Agile from using it. More importantly, they've built Jira to support Scrum and Kanban properly, not bodge it like others.
I know people grumble about the marketplace "we only want 25 people to use this", but that exposes a problem in its own right - if only 25 people need the function, then why are they not being Agile? Agile means having a common understanding of what you're doing, so surely ?if those 25 people need it, the rest of your users do?
Nic, Love the thorough answers and agree with your position. It is better than the others I have seen. I am not a project manager or scrum master with a ton of experience so I may also be wrong but I agree with you all the same!
I've got another question for you. I am new to the Atlassian tools and the community but a small software company owner of 22 years. I don't write code or operate in the development process as far as owning a job or function so pardon my ignorance. I am looking for a project manager, app developer, and AWS admin and was wondering if you have a place to post part-time gigs or know of a great place to look for this type of consultant?
It's not designed as a job posting or recruitment site, but the community does have an area for this sort of thing - post something in https://community.atlassian.com/t5/Jobs-Careers/gh-p/JobsCareers
Your Jira admin can add "Group Picker" custom fields to your issues. Groups represent many users.
Another way to solve it is for your Jira admin to add a "User Picker (multiple users)" field to your issues.
Why - not sure. That's how Atlassian's decided. There are many good QA apps on the Atlassian Marketplace. Alternatively, your admin can add a "Test Case" issue type and you can create tables in your "Description" field. This will be cumbersome, but won't require an app. In the long run, you'll benefit from a QA app.
Try Jira integrations with existing tools that do this. Jira provides a framework for your worklfows, but user needs are so diverse that it's unable to do everything. That's why Atlassian Marketplace exists and that's why Jira integrates with tools also from outside of the marketplace.
Your Jira admin can add "Single Select" custom field called, say, "T-shirt estimate" having values like "S, M, L, XL". Jira's functionality won't take this field into account, though, so no automatic sprint planning based on it will be there to measure capacity.
True, but there are many apps on the Atlassian Marektplace that can do this.
Marketplace is not an option for us because we have 15000 users in our JIRA instance due to customers also being a part of that. Atlassian makes everything dependent on the number of users in the Instance which does not make sense in anyway. Most other tools can differentiate between the Individual projects for calculating the number of users instead of the whole Instance of JIRA.
There is a possibility that you may need license optimization that would lower your license costs, so that marketplace becomes an option. If your customers are a large part of these 15000 users then you may benefit from converting some of your customer-facing projects to Jira Service Management-type projects where customers are served for free (yes, they do not require a license and still can do much). They interact through a simplified UI called the customer portal.
You can either reach out to an Atlassian Solution Partner near your to learn more about it or contact us (Deviniti) and we will try to help. There may be options that you just aren't aware of yet.