Atlassian Jira Align (formerly AgileCraft) vs ZenHub

• Effective Sprint planning : Sprint planning can be done using Planning Poker in AgileCraft by clicking Team > Manage > Other > Estimation Games very effectively for distributed teams.
• Team Capacity Allocation Report: After tasks are created at team or program level, the report from AgileCraft cab be pulled and can be verified that no team member is under or over allocated. A report can be generated by navigating to Team > Manage > Assign Tasks.
• Effective Requirement trace-ability: To maintain requirements trace-ability follow the steps below:
• Upload test cases against the story/requirement. once uploaded test cases will be visible under that story
• Execute Test cases in AgileCraft and mark them as Pass/Fail based on the actual outcome
• Based on test results, The acceptance criterion's can be marked as “Pass” or “Fail” & if marked failed corresponding defect can be logged & can be attached with the story
• So against each story we can easily see whether all test cases been executed or not & which acceptance criterion's are failed & how many defects are in open or close state.
• Daily Scrum: In AgileCraft, the option to run a daily stand-up is available from Team > Manage > Daily Standups. Selecting the sprint number opens the daily stand-up meeting window in which each team member's tasks are visible and hours can be burned against them. Conduct Scrum meetings in AgileCraft, and burn each associate hour against the tasks created during the meeting. The burn-down chart can be generated & viewed during the stand-up to check whether the team is on track.

Read full review

• Integration with GitHub.
• Great Kanban board functionality.

Read full review

• The only difficult thing is its learning for the beginners.
• Initially, its learning is quite steep but with the passage of time it becomes smooth enough and you will love to use it.
• It is enriched with all latest and powerful features in order to fully satisfy customers.

Read full review

• The software seems to at times have hiccups, and is not accessible
• The software sometimes throws errors that it can't do something, or save, and you can't determine why, and typically need to start over
• The admin type functions/entering values, codes, projects, releases, those sorts of things, do not seem to be logically located

Read full review

• With Jira, it is very easy to track down various bottlenecks in the deliverables further streamlining the development process in the production stage. Running numerous IT projects with multiple bottlenecks and backlogs was the biggest challenge that we ever faced before implementing Jira. Jira made the process more efficient by saving time and money.
• Jira helped to build customized features for different verticals. Rather than investing in different third party tools we were able to perform the same tasks in Jira. This saved us lot of money.

Read full review

• Saving dev time, making it easier to create a process they enjoy and use without issue (intangible)
• Making conversations between developers and product teams/easy to facilitate (intangible)
• Sped up the entire process (intangible)

Read full review