GitLab
vs
BluePrint Storyteller
Decision Kit
Decision Kit
Blueprint Storyteller is a visual application modeling tool that enables creating process models, design artifacts, and includes workflow to manage the lifecycle events and collaboration of the artifacts.
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. |
|
|
|
Labels
Labels provide an easy way to categorize issues, merge requests, or epics based on descriptive titles as ‘bug’, or ‘documentation’. |
|
|
|
Burndown Charts
GitLab provides Burndown Charts as part of Milestones. This allows users to better track progress during a sprint or while working on a new version of their software. |
|
|
|
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. |
|
|
|
Group Issue Board
Issue board scoped at the group level, so that you can view issues in all projects of that group. |
|
|
|
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. |
|
|
|
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. |
|
|
|
Scrum
Able to support the time-boxed (sprint) approach of the Agile -Scrum software delivery. Specific features would include: Issues, scrum boards, burndown charts, burn up. |
|
|
|
Kanban
Able to support the flow based approach of Agile - Kanban software delivery. Specific features would include: Issues, Kanban boards, burn up, cumulative flow diagram. |
|
|
|
SAFe (Scaled Agile Framework) - Essential SAFe
Able to support the key principles and practices of the Essential SAFe configuration., Agile Release Train, (a combined CD pipeline where multiple projects align to release), Planning Increment (PI) Planning (cadence driven project planning/ vision) |
|
|
|
SAFe (Scaled Agile Framework) - Lean Portfolio Management
Provides support for the key elements of Lean Portfolio Management. Specific features would include: Release Train, Lean Portfolio Management. |
|
|
|
Financial Management
Tracking, managing and reporting on the budget and actual spend of projects and programs within specific portfolios. Able to allocate costs to OPex or CAPex depending on specific organization reporting rules. Time tracking information used to determine labor cost allocations. Specific features would include: budget, spend, time, resource cost. |
|
|
|
Resource/Team Management
Tracks and manages the availability of team members by skill, experience, location, and cost, so they can support both planned and unplanned work. Specific features would include: individual capacity, individual skills, individual assignments, labor cost. |
|
|
|
Work Planning/Management
Able to define, schedule and assign specific tasks to team members and manage the sequence and interdependency of tasks with each other. This form of structured planning is needed when tasks are clearly defined and sequence of execution is critical. Specific features would include: WBS, Gantt Chart, Task Assignment, Scheduling, task sequence, task relationships. |
|
|
|
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. |
|
|
|
Product Roadmap
Establishing the product vision and strategy to organize, govern and shape the effort of the multi-disciplinary team building specific business services. The Product Roadmap is based on specific business goals and objectives, manages high level requirements, prioritizes future features, allocates resources, tracks progress and measures business results linked to the business strategy. Specific features would include: Product Strategy, Idea Gathering, Requirements Management, Resource Management, Feedback Collection, Milestone Tracking, Release Management, Workflow Management, Feature Tracking/Deviation, Roadmap Analytics, Centralized Notes, Report Generation, Imports, API/SDK, Conflict Management, and Customized Alerting. |
|
|
|
Issue Analytics
See issue analytics at the group level. |
|
|
|
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. |
|
|
|
Merge Requests
Create merge requests and @mention team members to review and safely merge your changes. |
|
|
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license
