Atlassian Jira Align (formerly AgileCraft) vs KanbanFlow

• 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

• Project monitoring with detailed management reports.
• Keep the team organized, focused on projects and demonstrate your goals in the tool.
• Simultaneous collaboration of the team in activities.
• Intuitive and user-friendly interface to use. Ease of learning how to use the tool.

Read full review

• 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.

Read full review

• I'm not sure if it has this or not because I've only been using it for about 6 months but we haven't quite figured out how to archive things. We have lots of data on that main page from Q3 and Q4 of last year but we need to figure out how to get it away from our main page so we can focus on new things this quarter
• I know when I was first added there were a few things the admin had to do in order to do that. All I remember is that it wasn't simple for them to get me hooked up. They had to do a few steps and then I was granted access. I don't know what exactly but I had to wait.

Read full review

• It has positively impacted our tech teams, allowing them to better organize the tasks and items they are working on and has greatly improved their ability to communicate & review these tasks with other teams.
• I believe it negatively impacted other departments as lengthy training was required by many associates to attempt using the tool, only to find out it didn't meet our needs, therefore much time was wasted.

Read full review

• Creating visibility of the status of all open work items
• Allowed for self-service ownership of projects by stakeholders

Read full review