@@ -445,7 +445,7 @@ Our belief is that we can guarantee a higher rate of success by incubating ideas
1. There is not enough code for multiple people to work on without running into merge conflicts.
1. Starting work earlier allows for more time for other people to contribute. We need to have a head start many years ahead of commercialization.
As a matter of process, we require that Single-engineer groups take part in our [Software Demo Process](/handbook/engineering/demos/#single-engineer-groups-demo) as a way to collaborate asynchronously with stakeholders, get iterative feedback, and maintain at least minimal alignment with the rest of GitLab while keeping their autonomy
As a matter of process, we require that Single-engineer groups take part in our [Software Demo Process](/handbook/engineering/workflow/demos/#single-engineer-groups-demo) as a way to collaborate asynchronously with stakeholders, get iterative feedback, and maintain at least minimal alignment with the rest of GitLab while keeping their autonomy
If the group finds great success, as measured by adoption, and needs to further evolve that area of the product, then the next step is to consider forming a multi-person group. Sometimes the category is complete and the group can successfully dissolve. There are other times when the category does not yield the adoption. We will gather the lessons learned and consider either dissolving the group or investing further based on the learnings.
@@ -7,7 +7,7 @@ At the conclusion of each project, we will conduct a root cause analysis using t
## Scheduling a Root Cause Analysis
1. Create an issue.
1. Use the [RCA](/handbook/engineering/root-cause-analysis/). Changes to that template can be added as an MR to the Professional Services project.
1. Use the [RCA](/handbook/engineering/workflow/root-cause-analysis/). Changes to that template can be added as an MR to the Professional Services project.
1. Ensure that the `Root Cause Analysis` label is applied to the issue.
1. Create a calendar event for the root cause analysis, including a link the issue and this page.
@@ -48,7 +48,7 @@ Work in the 40% time budget should be coordinated and prioritized by the Enginee
### Engineering Innovation
Engineering Innovation is a new process geared toward individual or small-team collaboration that encourages engineers to explore new ideas and Proof-of-Concepts. These projects are typically lean, time-boxed, iterative, and designed to validate whether an idea has the potential to evolve into a viable experimental feature or product. See the [Innovation at GitLab Guide](./engineering-innovation.md).
Engineering Innovation is a new process geared toward individual or small-team collaboration that encourages engineers to explore new ideas and Proof-of-Concepts. These projects are typically lean, time-boxed, iterative, and designed to validate whether an idea has the potential to evolve into a viable experimental feature or product. See the [Innovation at GitLab Guide](./workflow/engineering-innovation.md).
### Technical Roadmaps
@@ -204,32 +204,36 @@ There are five departments within the Engineering Division:
