Merge branch 'ogolowinski-master-patch-90076' into 'master'

Updates Workspace planning process

See merge request gitlab-com/www-gitlab-com!95606

development/dev/manage/_workspace_processes.erb

+Workspace works on components of the application that have a far-reaching impact and many groups will be involved in migratig features over, the following process is needed:
+
+* Inradev and performance issues must be triaged by the EM and PM to determine their pririty based on the impace of the number of users efffected and how severe the problem is.
+* Large scale projects (over 3 months of work) and mid-size projects (spanning over 1 milestone of planned work) will be organized in epics with clear iteration plans.
+* The epic must be broken down by the engineers to enable external contributors from other team to easily identify what needs to be picked up.
+* S1 & S2 security issues will be picked up in the closest milestone.   

development/dev/manage/index.html.md.erb

@@ -79,8 +79,6 @@ pages under the "Categories" header) is the single source of truth on where we'r
 * Direction pages should be reviewed regularly by Product. When updating these pages, please CC the relevant group to keep your teammates informed.
 * Product should make sure that their groups understand the direction and have an opportunity to contribute to it. Consider a monthly direction AMA for your group to field questions.
 
-
-
 #### Prioritization
 <!-- TODO: Would like to remove this and keep it on the group pages instead -->
 <%= partial("handbook/engineering/development/dev/manage/prioritization.erb") %>
@@ -127,9 +125,6 @@ It can be hard to understand how you're doing in your role, because feedback can
 | **(coaching)** | I'm trying to help you improve a behavior you are already exhibiting or change a behavior that you currently have | "The reports that you give me are very helpful, and in the future we can schedule them for the first of the month to be more consistent."
 | **(evaluation)** | Tells you where you stand according to existing standards or expectations | "My expectation was that our decision would be transparent. Since it was not, our team has forgotten the decision, so we must be sure and meet that expectation next time." |
 
-
-
-
 ### Group Access - additional considerations
 
 <!-- TODO: Would like to remove this and keep it on the group pages instead -->
@@ -154,7 +149,7 @@ It can be hard to understand how you're doing in your role, because feedback can
 
 ### Group Workspace - additional considerations
 
-TBD - areas in Workspace are far-reaching and should have their own process outlined or require rollout plans for certain areas
+<%= partial("handbook/engineering/development/dev/manage/workspace_processes.erb") %>
 
 ## Meetings