Craft.io vs. Jira Align

Craft.io is well suited for medium to large digital product teams that have some experience with the tools and features of the agile and lean models. Users that are new to those methodologies can have some difficulties understanding the platform. It is less appropriate for small projects too. It's a great tool but I think you can shape a project management tool to your needs in theses cases and it will work better.

Incentivized

This product is useful for a team/company working with multiple customers. Employee count anywhere larger than fifty or sixty will be benefited [from] this. Considering this product is expensive(as I’ve heard) this will not serve [many] purposes to smaller companies and startups who are having a very less customer base and [fewer...] employees.

• 'Sync' usually works flawlessly in syncing my artboards to Invision. Once you set up the plugin, I can easily forget about tinkering with any of the settings - it just 'works'.
• 'Library' is pretty great for generating a style guide from my design doc. Clicking one button makes magic happen, and creates a super succinct document for me to share between teammates and other teams.
• 'Data' also works wonders when trying to approximate 'real' data into a static design. It turns the painful job of having to fill in designs with 'real-world' data a piece of cake. It helps me validate rough designs using an actual approximation of real content.

Incentivized

• Jira is a great project management tool when it comes to tracking the progress of deliverables and milestones. Each member of the team can track individual deliverables and milestones. Jira comes with filters and search functions to perform these tasks.
• Jira is highly flexible when it comes to maintaining tasks and deliverable backlogs. You can plan and organize your sprints in such a way that you include your previous backlogs in them.

Incentivized

• It has a great workflow, but it is very little customizable.
• The tool is not so easy to use, so you have to take a time to get to know it.

Incentivized

• The initial ticket creation screen lacks some important features, such as assigning "point values" (a measure of effort needed for the ticket).
• The browser needs to be manually refreshed to see new tickets, which can make things confusing when several people in a meeting are simultaneously creating tickets.
• The interface on some smaller portions of the software are sometimes difficult to understand.

Incentivized

There is nothing that can be better than Jira but it needs to keep improving certain areas especially the attachment size area.

Incentivized

Most of the things are easily manageable except certain things that are hidden and you need to ask teammates who are aware of how they can link attachements in the comment section and so on.

Incentivized

Responsive chat with founders to answer any questions you have.

Incentivized

It is average. It needs to improve overall if you are paying the amount of money it costs. For now, it does the job, but with so many new features being added it would be very helpful to kick this up a notch.

Incentivized

Craft has a completely unique tool set that has functionality that really is not duplicated any where else in the industry. It cannot really be compared to any other tool I have had experience with, especially with the larger cloud infrastructure that Invision has built around their plugin and their platform.

Incentivized

Atlassian JIRA Align (formerly AgileCraft) has an excellent suite of tools that integrate well with other tools and offers full support for various agile frameworks, including SAFe. It's just a complete integrated package, whereas some other tools seem to be lacking in different areas. Several plug-ins can be integrated to help with pro serv invoicing and integration with GitHub, Jenkins, Confluence, and other tools that we use.

Incentivized

• It was good for tying end-user feedback on the app store to feature requests and help justify investments.

Incentivized

• Able to forecast & plan releases well using agilecraft leading to quality on time delivery.
• Distributed teams are able to collaborate well, be it be daily scrum, retrospective, estimation though this. Also team members love the gamification part & they have fun using this tool. Earlier we use to face challenges due to distributed teams but after AgileCraft, collaboration & communication was no longer a challenge & we are able to see improvement not only in team velocity, but also team satisfaction.
• Simplest tool to implement safe, scaling is always a problem with most of the agile tools but agilecraft helps in smoother implementation of safe practices & principles.

Incentivized