Atlassian Jira Align (formerly AgileCraft) vs Flow

• 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

• Design: very easy to discern what is important at a glance. The UX just works; it's very well thought out.
• Ease of use: onboarding was a breeze. Was up and running in less than an hour.
• Support: in-app support is great, nice website too to find exactly the solutions we needed.

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

• Better integration with Google Calendar -- it could be a bit clunky
• The mobile app didn't have as much functionality as one would like - you had to download two apps to access the features used on a desktop version

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

• Our biggest issue prior to flow was scrambling at the last minute to meet a project deadline. Flow has helped us manage tasks towards a deadline to execute more successful events and projects.
• Since Flow is being used across our entire organization, the speed at which we can collaborate cross-departmentally has increased. This is especially true of our communication and collaboration with our Marketing team.
• Flow has allowed our leadership team to be able to see the progress of a project at any time just by looking at that projects dashboard. This has both given them confidence as well as let them know when they need to intervene.

Read full review