The GitLab DevOps lifecycle contains the Plan stage. The product vision of Plan is to enable all people in any size organization to:
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 allow organizing these initiatives into powerful multi-level work breakdown plans and 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 will leverage timeline-based roadmap visualizations to help enterprises plan from small time scales (e.g. 2 week sprints for development teams) to large time scales (e.g. annual strategic initiatives for entire departments). Enhanced issues and issue boards capabilities will allow more versatile and powerful backlog grooming and cross-sprint planning functionality.
GitLab will enable teams to track execution of these plans over time. In addition to roadmap views as well as existing time tracking and story point estimation features (called weights in GitLab), GitLab workflow management will also be improved with group-level customized workflows integrated into boards, as well as burndown and burnup charts also integrated into boards.
GitLab will help teams identify high ROI opportunities, by organizing and surfacing initiatives with relatively large benefits (as entered by team members) and relatively low costs (via rolled up effort estimates at the epic level).
GitLab supports enterprise Agile portfolio and project management frameworks, including Scaled Agile Framework (SAFe), Scrum, and Kanban.
See how GitLab team members themselves use GitLab Agile PPM to create GitLab, as of GitLab 11.4.
Large enterprises, especially those in highly-regulated industries such as finance and healthcare, rely on governance frameworks in their planning and execution, in order to mitigate a variety of business risks.
GitLab will be improved with customized workflows integrated into boards, supporting the specific governed workflow stages in a particular organization. Also, GitLab will have custom fields, enabling the level of oversight and standardization required in the given large company.
The enterprise software industry is quickly transitioning to an Agile DevOps delivery model, where the focus is no longer only on getting bits and bytes out the door, but instead on shipping iterative business value continuously to end users, with rapid customer feedback.
GitLab will be enhanced with value streams and analytics built natively into the application itself. Customized workflows will allow teams to define their own value streams, relevant to their own company, their own customers, and their own industry. GitLab will surface VSM (value stream management) style metrics, such as cycle time, lead time, and deployment frequency, aggregated and rolled up, per an individual team, across multiple teams within a department, or even across the entire organization. Since GitLab is the first single application for the entire DevOps lifecycle, these metrics will allow teams to quickly identify and pinpoint process gaps and areas needing urgent improvement.
Many organizations create applications with rigorous requirements that need to be accurately tracked, and accounted for before developing the software, during, and afterward. Larger requirements need to be further broken down into smaller ones, with the relationships closely documented. This also ensures effective change control. That is, if a requirement changes, the team should be able to see the downstream impact immediately. Requirements management in GitLab addresses these problems and use cases.
Many organizations manage quality through both manual and automated testing. These are supported by artifacts such as test plans, test cases, and test execution runs, and having them integrate back with documented issues and feature requirements, allowing for feature-test traceability and quantifying that coverage. Quality management in GitLab addresses these problems and use cases.
Teams leverage GitLab search to quickly search for relevant content, enabling stronger intra-team and cross-team collaboration through discovery of all GitLab data.
GitLab supports deep Jira integration, allowing teams to use Jira for issue mangement, but still leveraging the benefits of GitLab source control and other native GitLab features.
We follow the general prioritization process of the Product Team. In particular, we consider reach, impact, confidence, and effort to identify and plan changes in upcoming milestones (monthly iterations).
We love community code contributions to GitLab. Read this guide to get started.
Please also participate in our issue tracker. You can file bugs, propose new features, suggest design improvements, or continue a conversation on any one of these. Simply open a new issue or comment on an existing one.
You can also contact me (Victor) via the channels on my profile page.
There are a number of other issues that we've identified as being interesting that we are potentially thinking about, but do not currently have planned by setting a milestone for delivery. Some are good ideas we want to do, but don't yet know when; some we may never get around to, some may be replaced by another idea, and some are just waiting for that right spark of inspiration to turn them into something special.
Remember that at GitLab, everyone can contribute! This is one of our fundamental values and something we truly believe in, so if you have feedback on any of these items you're more than welcome to jump into the discussion. Our vision and product are truly something we build together!
notin issue/mr/epic list views and boards Starter