The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
| Stage | Plan |
| Maturity | Viable |
| Content Last Reviewed | 2021-09-15 |
Large enterprises are continually working on increasingly more complex and larger scope initiatives that cut across multiple teams and even departments, spanning months, quarters, and even years. GitLab's vision is to support organizing these initiatives into powerful multi-level work breakdown plans and to enable tracking the execution of them over time, to be extremely simple and insightful. In addition, GitLab should highlight which opportunities have higher ROI, helping teams make strategic business planning decisions.
GitLab supports popular enterprise Agile portfolio and project management frameworks, including Scaled Agile Framework (SAFe), Scrum, and Kanban.
During FY22-Q2 and FY22-Q3, we will pause new feature work on epics and focus on converting epics to issue types.
To drive our vision for Epics and how they support our overall strategy for Product Planning, we are continuing to develop the building blocks for deeper more expansive program and portfolio functionality. Currently we are validating and tracking the following big ticket items :
Recently Completed:
Now that our users can properly build out epics as a collection of associated issues, we are focusing on developing advanced functionality to make Epics more powerful planning artifacts. To begin, we will be pursuing multiple enhancements to the current Epic planning artifact and how it relates to Issues, Milestones, and our Roadmaps:
GitLab's multi-level work breakdown planning capabilities will include related epic support and issues, allowing enterprises to capture and manage:
This category is currently at the viable level, and our next maturity target is complete by 2021-10-30.
We are tracking progress against this target via this epic.
We are also tracking our progress toward lovable via this epic.
Leveraging Epics as a building block for Product and Portfolio Management is a common use case in the industry, with many are established players such as Jira, Clarity, Planview, VersionOne, AgileCraft, and ServiceNow offering similar functionality. Many of these tools were developed targeted at truly enterprise cases, allowing users to track large business initiatives across an organization. Customers using these tools typically have another set of tools for the product-development teams to turn these high-level business initiatives into scoped out detailed planned work and actual software deliverables. Therefore, our competitive advantage is having both (the high-level initiatives, and the product-development-level abstractions) in a single tool, that is fully integrated for a seamless experience. Our strategy is building toward those enterprise use cases, starting with the product-development baseline abstractions.
As the usage of Epics increase and more use cases and needs are being surfaced, we are tracking our most popular issues in the category. In particular, we are focusing on:
To support our Customer Success and Sales departments, we are validating and working towards critical items to enable them to serve additional prospects and customers:
Large enterprises are continually working on increasingly more complex and larger scope initiatives that cut across multiple teams and departments, often spanning months, quarters, and even years. GitLab's vision is to provide robust, multi-level roadmaps that enable businesses to track current effort in flight, and plan upcoming work to best utilize their resources and focus on the right priorities. GitLab provides timeline-based roadmap visualizations to enable users plan from shorter delivery increments (e.g. 2 week sprints for development teams) to larger time scales (e.g. quarterly or annual strategic initiatives for entire departments).
During FY22-Q2 and FY22-Q3, we will pause new feature work on roadmaps and focus on converting epics to issue types. This work will give us a solid foundation to build future roadmap capabilites.
Currently we are validating and tracking the following future big ticket items :
To move towards our long term vision of robust roadmapping and planning, we are focusing on providing a solid foundation of functionality that we can build on in the future. We are working to ensure that the roadmap view provides the information you need to understand current state of work, identify blockers or bottlenecks, and ensure upcoming work is prepared for.
To begin, we will be releasing multiple enhancements to the current Roadmap view:
This category is currently at the minimal level, and our next maturity target is viable by 2021-09-28 see MR. We are tracking progress against this target via this epic.
We are also tracking our progress toward complete via this epic.
The Roadmapping space is large and is made up of stand alone tools, and as additional functionality on top of software planning systems like AHA.io, Roadmunk, Productboard, Monday.com, Trello, and Productplan. Many of these were developed targeted at truly enterprise cases, allowing users to track large business initiatives across an organization. Customers using these tools often have another set of tools for the product-development teams to turn these high-level business initiatives into scoped out detailed planned work and actual software deliverables. Therefore, our competitive advantage is having both (the high-level initiatives, and the product-development-level abstractions) in a single tool, that is fully integrated for a seamless experience. In addition to the enterprise opportunity, we believe roadmapping can be also be beneficial to smaller organizations and individual teams to chart out the future and report on progress. Our strategy is building toward enterprise use cases starting with the product-development baseline abstractions.
As the usage of Roadmaps increase and more use cases and needs are being surfaced, we are tracking our most popular issues in the category. In particular, we are focusing on:
To support our Customer Success and Sales departments, we are validating and working towards critical items to enable them to serve additional prospects and customers:
