Asana is a web and mobile project management app. With tasks, projects, conversations, and dashboards, Asana lets an entire team know who's doing what by when, enabling workload balancing. Users can also add integrations for GANTT charts, time tracking and more.
$13.49
per month per user
GitHub
Score 9.1 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Jira Align
Score 7.9 out of 10
N/A
A solution to bridge the gap between strategy and execution for portfolio, product, and program management teams, used to manage idea intake, prioritize your feature backlog, and track progress with live roadmaps.
I like Nifty as this has time sheets, however we preferred the clean interface of Asana. Nifty was a bit overwhelming when we tried it. Their app on Android wasn't anywhere near as mature as Asana's app.
Plutio is great and has many features, but we preferred the look of Asana.
As stated before, for my own line of work, I prefer JIRA because it is more powerful; it brings more structure and organization (which might seem as a downside for some people) but provides additional value from it. It provides a better user interface and experience; it has a …
Trello - great but a bit young. Good integration points. I think it could be a good too to integrate with. Some people enjoy the KanBan type view and Asana doesn't have that currently. Basecamp - more project manager focused but also a good integration point. JIRA - Better for …
Bitbucket supports Mercurial VCS in addition to Git. Since it is an Atlassian product, Bitbucket is very well integrated with the company's other tools, like JIRA (which is widely used in the development industry), Jenkins, and Bamboo. It offers many of the same features as …
Jira provides a large advantage over some competitors, such as Harvest which is more of simple time tracking software, but without the connectivity provided between team members. Furthermore, Asana is a close competitor, but does not provide the same level of integration with …
Vice President, Chief Architect, Development Manager and Software Engineer
Chose Jira Align
Atlassian JIRA Align (formerly AgileCraft) has an excellent suite of tools that integrate well with other tools and offers full support for various agile frameworks, including SAFe. It's just a complete integrated package, whereas some other tools seem to be lacking in …
The usability of Asana is broad since it's available in a variety of platforms that are widely used nowadays. I think that it would be great for people who are constantly on the move and switching devices, since it has allowed me to work from my phone, too. I also think that Asana has proven itself to handle a large quantity of work
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
The Atlassian Jira Align (formerly AgileCraft) tools help keep our scrum teams moving in the right direction. It gives Sr. Executives visibility into the progress of our digital transformation efforts. It provides information to our program manager to create the necessary artifacts to justify continued funding of our initiatives. It also supports the SAFe framework, along with some others. And the Atlassian Jira Align (formerly AgileCraft) tools provide integration to other tools that we use in our portfolio.
Through it, we were able to communicate and cooperate with the rest of the team to complete the work in the required manner and at the appropriate time.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
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.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
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.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
It is very user-friendly. Takes a new employee an hour to start figuring out how the system works. That's an important factor. You don't want to encounter the issue where employees need a week to understand how the system works. For example, JIRA, I tried using it for a week and I still don't understand the complicated layout. Asana has a simple interface. Once you see it, you get it type of program.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
As I have mentioned, some older, less tech savvy, team members have not found it as intuitive. I found it the same when I started using it although it quickly made sense. I think this is because there are lots of features we do not use so this can get in the way of what we do use
I haven't had to use their support so I can't rate it. The fact that I haven't needed them reflects the ease of use of the product. I would recommend that any new users schedule a complete demo of the product to ensure that they are using it to it's fullest (there's a lot of useful features).
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
Overall support from Jira team is good. It comes at an additional price but it is very efficient. There are no long wait times, you get a dedicated team to look into your issues. The support is available throughout the year and they keep a record of your issues. Overall we are very satisfied with the support they have provided us over the years, it has been very effective for the price that we pay.
Asana is a top-tier project management software that helps us organize and track projects from start to finish. It allows us to apply tasks/to-dos to multiple projects without duplication, divide complex projects into smaller tasks, and track project progress. It also helps us organize work on Kanban boards or linear lists. It stands out from the crowd in a big way compared to the competition.
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
Microsoft Azure Devops won't have the major functionality of software management like Jira. The customization provided by Jira is having a cutting edge over any project management tool. Adds-on and Plugins feature in the Jira Tool make it as perfect as desired task management tool for any company. One of the best Agile based Project Management Tools.
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.
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.
