Atlassian Jira Align (formerly AgileCraft) vs Kanbanery (discontinued)

• 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

• I really like how easy it is for my clients to use Kanbanery. That's the most important thing for me in a project management tool, because I don't want the tool to get in the way of working with clients.
• I can see really quickly what needs to be done, and more importantly, what doesn't need to be done. Having a clear view of all my tasks takes a lot of stress of off me.
• Kanbanery is also good for communication with clients. If I have a task card that represents a component, we can talk about it in comments, or we use the project chat for general stuff. It keeps my email from getting cluttered.

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'd love to see some improvements in the Scrum burn down chart, but it works okay as it is.
• It would be nice if we could adjust the width of the columns. It's fine on most monitors, but on a small screen I have to scroll sideways.

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

• I feel like we're much more efficient. I spend more time working on tasks now and a lot less time digging through tickets.
• Since we can see when there's a problem in our team really easy with Kanbanery, people get help when they need it sooner. That has to be good for productivity.

Read full review