Digital.ai Agility vs. Git vs. Plastic SCM

Scenarios where it works well: 1) Retros can be very well facilitated & notes/action items
can be captured against the sprint. 2) Product Owner can effectively track the story
progress with all the test-cases, design etc. 3) Being good scaling support, it provides good visibility
across multiple teams, programs and agile portfolios, providing a centralized
environment where all our stakeholders can easily work together regardless of location. 4) It provides easy tracking all of your epics,
stories, themes, defects, tasks, tests and issues 5) I like its intuitive UI as for moving stories
around, burning hours. 6) It allows top leadership to visualize
and report their strategic plans, giving all stakeholders the relevant data
that they need to stay dedicated to the project priorities. 7) It can be easily integrated with slack
so for few teams we used slack for collaboration Scenarios where it did not work well: 1) Test Management need improvement in
terms of tracking tests, team had hard time tracking regression test cases. 2) Version one comes with lot of features like
Rally but here we don’t get customizations which is there in Jira where from workflow
to issue everything can be customized based on your team/program/portfolio
requirements. 3) Lot of navigation to access basic
stuff. Example I want to go to bug attachment , there are lt of clicks &
navigation need to do which should be pretty straightforward I feel.

Incentivized

GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.

Incentivized

Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously. Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient

• Automated saving of changes, no records can be lost because all items are saved in real-time.
• The watch function, optional but beneficial when managing multiple teams or projects.

Incentivized

• Ability to create branches off current releases to modify code that can be tested in a separate environment.
• Each developer had their own local copy of branches so it minimizes mistakes being made.
• Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
• Conflicts are displayed nicely so that developers can resolve with ease.

Incentivized

• Version Control
• Organizing Workflow
• Transparency

Incentivized

• Although Digital.ai Agility supports customizations, they can be somewhat cumbersome to set up and maintain
• The Analytics engine's user experience for digging into the data does not have the same feel as the rest of the system and, as a result, can be hard to work with

Incentivized

• There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
• Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
• Many different GUIs, many people (including myself) opt to just use the command-line.

Incentivized

• Interface
• Documentation
• Learning curve
• Unity integration

Incentivized

Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.

Incentivized

Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.

Incentivized

VersionOne provides outstanding training. They have Product Owner training that I recommend every Product Owner attend. They have scrum master training and other agile training that was well worth the money paid because it made the teams more productive. And the support for the tool is incredible. These people live and breathe Agile and are evangelists and enthusiasts.

Incentivized

I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.

Incentivized

It's easy to set up and get going.

Incentivized

JIRA appears to be more extensible with the ability for Scrum, Kanban, bug/incident tracking, and the ability to customize dashboards. However, VersionOne's performance over the same teams is extremely fast in comparison and therefore allows users to be more productive over the same amount of time.

Incentivized

I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.

Incentivized

Plastic has best integration with unity - zero issues, native, straightforward. GitHub feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as gitkraken, gitlab, Sourcetree, fork, etc. it is really easy to develop games this way.

Incentivized

• It has made it easier to implement Agile processes. Since our team is fairly new to Agile, this has been extremely helpful.
• Our organization is quickly growing, and V1 has made it easier for new hires to look at everything that our team has in the works.

Incentivized

• Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
• Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
• Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.

Incentivized

• Easy to use
• Cheap
• Better than git for us
• Artists love it

Incentivized