Sec. SSCS [Co-Create Initiatives]

Please follow instructions here (&2554). If needed, please assign team PMs to assist in further defining co-create initiatives for your stage.

Please evaluate with your applicable engineering manage based on the following criteria:

Scope and complexity of the initiative

• Technical requirements and complexity
• Anticipated lead time to engage and capacity plan

Label as:

• Small (2-4 weeks)
• Medium (1-2 months)
• Large (quarter or more)

Resource requirements

• Engineer level needed for specific effort (i.e. Junior, Staff, etc.)
• Design and UX resources
• Testing and quality assurance needs
• Documentation requirements

Label as:

• General (Junior, Intermediate, etc.)
• Specialized (Specific skill set needed for developer)
• Expert (Principal / Staff engineer needed)

Lead time

• Expectations on the amount of lead time our internal teams would need to make this initiative successful

Label as:

• Weeks
• Month
• Quarter
• Multi-Quarter

Product Area	Scope and Complexity	Resource Requirements	Lead Time	Issue
grouppipeline security	Large (in-progress)	Sent Developer on site already	N/A	Support AWS secrets manager as alternative to V... (gitlab-org/gitlab#29047 - closed)
groupauthentication	Very Small (Not started)	General (Intermediate engineer)	< 1 week	Add Configuration Option for Mandatory public e... (gitlab-org/gitlab#9828)
grouppipeline security				Job artifacts should be encryptable (gitlab-org/gitlab#363548)
groupauthentication	Not ready for Co-create			https://gitlab.com/gitlab-org/gitlab/-/issues/353065+