Atlassian Jira Align (formerly AgileCraft) vs WORKetc

• 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

• Connecting all the different methods of communicating with our clients into one place is the best part of the application to us. The Google Apps integration lets us update all of our WORK[etc] details directly from our email page which saves a huge amount of time. It lets us move back and forth freely between WORK[etc] tools and our Google Apps email, documents, calendar, etc. with ease.
• Breaking work according to what we are doing helps us group and ungroup things as needed. Since we do tech support and so much more having the ability to connect projects, support cases, to dos, documents, discussions, and more all together makes it easy to work with the relationships of all the different activity.
• We have found the discussion tool to be vital to moving things through quickly. There are many discussions that are just FYI while others really need a decision or answer form the team members. Discussions allows us to quickly note the people we need to answer us and what is there as an FYI. It keeps all that history so our decision process become documented easily and not lost in email chains.

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 one key issue that it doesn't solve is resource utilisation. You are able to add the number of hours that each "to do" will take but you can't allocate that to an employee and then aggregate all that up to show how much capacity you are using or have left.
• One if its great benefits is its flexibility but that is also a drawback because there are multiple ways to do the same thing. This means that to ensure consistency across all employees having your own business procedures on how to use WORKetc is vital.
• Some of the financial processes don't fully reflect UK practice currently. For instance it doesn't deal with VAT on expenditure well. However we have been assured that this is being resolved.

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

• Setting up project templates is time-consuming - if you want to do it right. Nevertheless, it is well worth it! Routine complex projects that used to require at least six people and at least as many "silos of information" are now done with two or three people, and - at most - 2 or 3 silos of information. And that's only because I haven't fully integrated the program with our Accounting programs (and there is an API for Quickbooks). I'd say the initial investment of perhaps 80 hours on my part was saved five or ten times over during our first six months, with better accuracy, accountability, and documentation. Since then, the ROI is at least 20 or 30 times annually of my time...the one thing I can't buy more of.

Read full review