GitLab
vs
Broadcom Rally
vs
Decision Kit
Decision Kit
Broadcom Rally is an agile project planning and management tool designed to help enterprise teams adopt and implement agile methodologies. Based on the acquisition of Rally Software, Agile Central enables teams to manage their backlog of user stories, estimate and plan the work to deliver the user stories and then manage the actual delivery. Rally supports multiple agile methodologies from sprints, where the delivery work is timeboxed to kanban, where the focus is on flow.
Feature Comparison
| FEATURES |
|
|
|---|---|---|
|
Issues
Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects. |
|
|
|
Description Templates
By adding a description template to your issues or merge requests, users who create a new issue or merge request can select a template to help them to communicate effectively. |
|
|
|
Labels
Labels provide an easy way to categorize issues, merge requests, or epics based on descriptive titles as ‘bug’, or ‘documentation’. |
|
|
|
Issue Weights
GitLab lets you manage issues using Agile practices by setting the weight of an issue. |
|
|
|
Milestones
Create and manage milestones at both the project and group levels, viewing all the issues for the milestone you’re currently working on, representing an Agile program increment or a release. |
|
|
|
Iterations
Create and manage iterations at the group level, view all the issues for the iteration you’re currently working on within your group or project, and enable all subgroups and projects to stay in sync on the same cadence. |
|
|
|
Issue Due Dates
In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline. |
|
|
|
Multiple Issue Assignees
Assign more than one person to an issue at a time. |
|
|
|
Confidential Issues
Keep your information secure with Confidential Issues. With GitLab, you can create confidential issues visible only for project members with Reporter access level or above. |
|
|
|
Linked Issues
Mark issues as related to one another. |
|
|
|
Move Issue to Another Project
You can move issues between projects in GitLab. All links, history and comments will be copied and the original issue will reference the newly moved issue. This makes working with multiple issue trackers much easier. |
|
|
|
Mark Issue as Duplicate
Mark an issue as a duplicate of another issue, closing it. |
|
|
|
New Issue via Email
Create an issue from email by sending in the issue title and description. |
|
|
|
Burndown Charts
GitLab provides Burndown Charts as part of Milestones and Iterations. This allows users to better track progress during a sprint or while working on a new version of their software. |
|
|
|
Hill Chart Status reporting
Hill charts make it simple to report the general status of a work item, issue, or project. Where before the top of the hill, the item is full of uncertainty and unknowns, and after the crest of the hill, execution is clear sailing with fewer risks and unknowns. |
|
|
|
Project Issue Board
GitLab has Issue Boards, each list of an Issue Board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user-friendly way. |
|
|
|
Multiple Project Issue Boards
Large companies often have hundreds of different projects, all with different moving parts at the same time. GitLab allows for multiple Issue Boards for a single project so you can plan, organize, and visualize a workflow for a feature or product release. Multiple Issue Boards are particularly useful for large projects with more than one team or in situations where a repository is used to host the code of multiple products. |
|
|
|
Multiple Group Issue Boards
Multiple Group Issue Boards, similar to Multiple Project Issue Boards |
|
|
|
Issue Board Label Lists
An Issue Board is based on its project’s label structure, therefore, it applies the same descriptive labels to indicate placement on the board. GitLab issues can appear on multiple issues and they still have meaning without the context of a particular board. |
|
|
|
Issue Board Configuration
Associate a board with a milestone, labels, an assignee, and a weight |
|
|
|
Issue Board Focus Mode
Get more information at a time with the Issue Board focus mode, which removes all unnecessary elements from the screen to show your Issue Boards. |
|
|
|
Add Multiple Issues to Project Issue Board
From an Issue Board, you can add multiple issues to lists in the board by selecting one or more existing issues. |
|
|
|
New Issue in Issue Board List
With GitLab Issue Boards, you can create issues directly from the board and assign multiple labels allowing them to appear on multiple boards. |
|
|
|
Issue Board Types
Issue boards/dashboards reflect an organizations flow for processing work items. These boards can reflect individualized workflow or follow established patterns. Issue board types with established patterns (such as Scrum and Kanban) can make setup of new boards easier. |
|
|
|
Issue Board Configuration with Advanced Logic
Define what issues show in an issue board using advanced Boolean logic. |
|
|
|
Time Tracking
Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests. |
|
|
|
Advanced Time Tracking
Able to capture individual time reporting for specific assigned tasks and then to allocate labor costs to the appropriate project. Specific features would include: estimate, actual, cost, reporting. |
|
|
|
Single level Epics
Plan and track features and work group level epics that collect issues together. Easily create and assign Issues directly from the Epic itself |
|
|
|
Multi-level Epics
Plan and track strategies, initiatives, and features with multi-level epics that collect issues together. Manage multiple children epics and their issues within the Epic Tree by dragging and dropping them to organize and prioritize the work. |
|
|
|
Confidential Epics
Organize a collection of related confidential issues into a confidential epic, allowing you to manage sensitive work more efficiently. |
|
|
|
Roadmaps
Visualize multiple epics and milestones across time in a roadmap view. |
|
|
|
Portfolio-level Roadmaps
Visualize multiple parent and child epics across time in a Roadmap view to gain insight into how your portfolio of work is progressing. Establishing the product vision and strategy to organize, govern and shape the effort of multi-disciplinary teams building specific business services and features. |
|
|
|
DevOps Pipeline
Able to establish visibility into the end to end DevOps pipeline so the entire team is aware of pipeline status and can contribute to overall success. |
|
|
|
Out-of-the-box Agile Reporting
Teams have access to more than a dozen out-of-the-box reports with real-time, actionable insights into how their team is performing sprint over sprint. Example reports are sprint burndown, epic burndown, cumulative flow diagram, velocity chart, burn up chart, and sprint report. |
|
|
|
Requirements Management
With Requirements Management you are able to gather, document, refine, and track approval of business and system requirements. Manage and track the relationships between requirements and other requirements, requirements and code, or requirements and test cases for each version of requirements. Specific features will include definition, traceability, and requirement hierarchy and dependency. |
|
|
|
Satisfy Requirements from CI/CD pipelines
This powerful feature uses the GitLab single-application model to allow testing run in the CI/CD pipelines to satisfy your requirements. This automates the cumbersome task of identifying satisfied requirements, and enables your organization to focus on delivering value. |
|
|
|
Import & Export Requirements
To better collaborate with external groups and organizations, requirements can be imported and exported in CSV format. This allows teams to use a single interface for development and testing against requirements. |
|
|
|
Quality Management
Able to support test planning, definition of test cases, results of test execution and corresponding backlog of work resulting from failed tests. Specific features would include: Test case planning, test execution, defect tracking (backlog), severity, priority. |
|
|
|
Create test cases from within GitLab
Create and view test cases from within GitLab. This allows for seamless collaboration between contributors. |
|
|
|
Service Desk
Allow external users to create issues in your GitLab instance without an account and without access to anything except their issue. Manage tickets from the GitLab interface. |
|
|
|
Service Desk Custom Branding
Allow customization of incoming issues and response emails, including the service desk user name to allow for a cohesive branding experience for your customers. |
|
|
|
Portfolio Management
Plan and track work at the project and portfolio level. Manage capacity and resources together with Portfolio Management. |
|
|
|
Create, search and view issues from chat
Quickly create, view and search for issues straight from chat. |
|
|
|
Mattermost integration
Mattermost can be automatically installed and integrated using GitLab Omnibus |
|
|
|
Multiple integrations
GitLab can integrate with Authentication and Authorization (LDAP / AD) mechanisms, multiple 3rd party services, CI/CD, and other tools such as ALM, PLM, Agile and Automation tools. |
|
|
|
Automatically close issue(s) when a merge request is merged
With GitLab, you can use specific keywords to close one or more issues as soon as a merge request is merged. |
|
|
|
Configurable issue closing pattern
Define your own specific keywords to close one or more issues as soon as a merge request is merged. |
|
|
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license
