41–50 of 182 posts
Earlier quoted context omitted.
Our Github integration is a two-way sync, so that you can import any open GitHub issues into Tara as Tara tasks. If you update the corresponding the Tara task, the corresponding GitHub issues are also updated, so you can certainly keep using the GitHub issues. The main benefit of using Tara is that it provides the team a much better way of plan upcoming sprints, and the system also pulls in GitHub PRs to eliminate an…
does it work with gitlab?
Earlier quoted context omitted.
Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…
Or maybe the problem with Jira is that bringing in an external consultant is the best recommendation.
My experience is that if an org decides to use then they will do it wrong the first time without external assistance. This holds true even for popular tools like Postgres, AWS, Terraform, or even Git.
Anecdotally, I don't know of any tool that is highly configurable that makes it easy for users to set it up and then scale it over time without learning the specific domain knowledge. Jira is no different in that sense. If you have an example of a tool that bucks this trend, please share it, I would love to play with it and see what I can learn about how to better serve users in this type of use case.
Looks awesome and I would love to try it out. Unfortunately I work at a large company which has 'standardized' on Jira + other related tools. Now that the majority of work is being done through Jira, it would take a world ending event to move away, no matter how good of a product the alternative is.
Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…
Earlier quoted context omitted.
Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…
Or maybe the problem with Jira is that bringing in an external consultant is the best recommendation.
External consultants are kind of an organizational hack. In contrast to top management they can take the risk of being wrong. In contrast to the workers they are not part of the inter-department politics.
On premise option?
Hey folks. My co-founder and I started noodling on productivity tools a few years ago. After interviewing 250+ engineers and founders, we discovered that most project management software a) takes a lot of time to configure b) is not built for cross-functional teams and c) takes away focus from the release cycle. The status quo is that engineers spend precious time wading through tickets, and EMs + PMs continue to lac…
Every project management software will have some reasonable defaults that can get you started in no time.
The problem is that every company (and certainly any company with more than a handful of employees), at some point, will want to adjust the tool to their use case and that's where the complexity comes in. If you can't adjust things like statuses and workflows, then you'll have issues with adoption.
All the best, this is an incredibly crowded and competitive scene.
It’s a nice looking tool, but the marketing feels oh so very Enterprise Agile(tm) in ethos. “Run your weekly sprints on time” — as opposed to them taking two weeks? To achieve predictability, something has to give. It’s usually “learning” which is never on the plan. The next release will be done when the right top priorities are met well enough. When’s that? You decide by prioritizing how many priorities are in the r…
As a manager I follow two principles that help me to prioritise tasks for a weekly sprint. First, every project has three levers: budget, timeliness, features. Choose two. So it's not about not trusting the development team. It's about understanding the tradeoffs and how the delivery date will be affected. Second, how well can you predict what you can achieve as a developer in one day vs one hundred days? The estimat…
Team has to include 'the business', as in, voice of customer, features lens, in those tradeoff prioritizations along with what do we engineer, and what's the truth of where we are on the field, for delivering what satisfies the customer and our constraints. // Hat tip Rands in Repose.
As for "Ultimately it's not about trust, it's about accountability and predictability" that's precisely the characterization I reject. Accountability means you earn your keep by being effective. Predictability, well, milestones come and go, the software gets used forever. That's the predictability needed, which goes right back to effectiveness. You won't magic either of those in a Jira.
Earlier quoted context omitted.
Disclaimer: I run an Atlassian consulting company. In most scenarios I run into, "Unfortunately I work at a large company which has 'standardized' on Jira" translates into "Someone set up Jira poorly and now we dislike using it". The thing is that if you replace Jira with any tool you can imagine, the statement will hold true. Jira isn't inherently a better or worse tool than most others out there. If you're at an or…
I think you missed the parent's "+ other related tools". My company uses Jira plus Confluence plus Bitbucket, which are each more or less shitty, but they are more or less interlinked. And that interlinking does actually add value. It doesn't matter whether Jira is inherently better or worse than anything else. It doesn't matter whether an isolated Jira installation could be replaced with something else. The network…
We just moved away from Atlassian to JetBrain's YouTrack. Huuge improvement in usability, system administration, cost.
I couldn't find the pricing anywhere in the site.
It says "free" twice, in colored CTA buttons, in the first ~150px or so.
I don't really care if it's a "pricing" page or not. The question you need to answer before I try you product is "what am I not getting by using the free version?" If there's an enterprise version in the works, tease me a little and "Coming soon" a bunch of enterprise-y features in a feature table. Just don't make me give you my email address, go through a confirmation flow, try out the product, and then tell me "if you need more than 1 user, click here to give us your CC".
It’s a nice looking tool, but the marketing feels oh so very Enterprise Agile(tm) in ethos. “Run your weekly sprints on time” — as opposed to them taking two weeks? To achieve predictability, something has to give. It’s usually “learning” which is never on the plan. The next release will be done when the right top priorities are met well enough. When’s that? You decide by prioritizing how many priorities are in the r…
As a manager I follow two principles that help me to prioritise tasks for a weekly sprint. First, every project has three levers: budget, timeliness, features. Choose two. So it's not about not trusting the development team. It's about understanding the tradeoffs and how the delivery date will be affected. Second, how well can you predict what you can achieve as a developer in one day vs one hundred days? The estimat…
You forgot about quality. It can blow the other 3 out of the water.