Atlassian Jira Align Formerly AgileCraft vs Jira Service Management (Jira Service Desk)

• 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 many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

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

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

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

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Read full review