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.
This direction page was last reviewed on:
2024-02-07
| Stage | Plan |
| Group | Project Management |
| Maturity | Viable |
👋 This is the category direction for Team Planning in GitLab, which is part of the Project Management group with the Plan stage. Please reach out to the group's Product Manager, Gabe Weaver (E-mail), if you'd like to provide feedback or ask any questions related to this product category.
This direction is a work in progress and everyone can contribute:
Team Planning's goal is to provide collaboration and planning capabilities to empower small, autonomous teams to continuously deliver customer and business value with the shortest possible cycle times. Features owned by the Team Planning category include work items (issues), tasks, milestones, iterations, boards, discussions, labels, todos, quick actions, markdown, and notifications.
Team Planning's strategy is aligned to Plan's 3 year stage themes.
Our group level issue board provides detailed insight into everything currently in flight.
/iteration quick action now accepts a cadence reference with --current or --next arguments.While we believe the following items are critically important to the long-term use cases we want to support within Plan, we currently are not focusing on solving them:
BIC (Best In Class) is an indicator of forecated near-term market performance based on a combination of factors, including analyst views, market news, and feedback from the sales and product teams. It is critical that we understand where GitLab appears in the BIC landscape.
This information is maintained on this internal handbook page
This information is maintained on this internal handbook page
This information is maintained on this internal handbook page
This category is currently at the Viable maturity level, and our next maturity target is Complete on 2024-06-22.
We are tracking our progress against this target via this epic.
GitLab identifies who our DevSecOps application is built for utilizing the following categorization. We list our view of who we will support when in priority order.
We are currently focused on providing best-in-class solutions for the following Jobs To Be Done (JTBD):
| Job statements | Maturity | Confidence | Source |
|---|---|---|---|
| When splitting prioritized initiatives or features into requirements, I want to group related slices of value and surface dependencies, so I can maximize alignment on the scope of a business goal and efficiently plan its incremental delivery. |
|
Researched | Issue |
| When estimating work during refinement, I want to validate that requirements are valuable and discrete, so I can increase the amount of value delivered with the least effort. |
|
Researched | Issue |
| When planning a release, I want to prioritize and sequence estimated work based on feasibly, capacity, and ROI, so I can incrementally deliver toward business objectives. |
|
Researched | Issue |
| When organizing priority work, I want to visualize our intended workflow, so I can increase team efficiency, collaboration, and predictability. |
|
Researched | Issue |
| When collaborating with a team or stakeholders, I want to radiate the current status of work continuously, so I can increase alignment on progress and any impediments that need to be addressed. |
|
Researched | Issue |
| Job statements | Maturity | Confidence | Source |
|---|---|---|---|
| When reviewing my product strategy with leadership, I want to demonstrate how my plans will drive overall vision and objectives toward reality, so I can increase buy-in, trust, and allocation of resources toward my efforts. |
|
Researched | Issue |
| When synthesizing inputs, I want to categorize opportunities based on how efficiently they drive the success of business objectives, so I can increase confidence in items I have prioritized, and feel empowered to say no to less impactful ideas. |
|
Researched | Issue |
| When visualizing the plan of how my strategy will be implemented, I want to display how prioritized items cascade up toward larger vision and business objectives, so I can increase alignment on the overall impact and importance of even the most granular items within my plan. |
|
Researched | Issue |
| When soliciting feedback and collaboration on the implementation of my strategy, I want to craft a view of my plan with the intended audience in mind, so I can increase team and stakeholder alignment through effective storytelling at the correct level of abstraction. |
|
Researched | Issue |