|Content Last Reviewed||
Welcome to the category strategy for Roadmaps, part of the Plan stage's Product Planning group. To provide feedback or ask questions, please reach out to the group's Product Manager, Mark Wood (E-mail).
We believe in a world where everyone can contribute. We value your contributions, so here are some ways to join in!
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).
To drive our vison for Roadmaps and how they supports our overall strategy for Portfolio Management 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 :
Prioritization of feature requests, enhancements, and bug fixes is described in the Prioritization section of the GitLab Handbook.
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-01-31.
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 oppritunity, we belive roadmapping can be also be beneficail to smaller organizations and individual teams to chart out the future and report on progress, so our strategy is building toward those 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: