[UX] Concept - Project Orchestration Feature
❓
Problem GitLab has historically targeted individual contributors such as:
- Software Developers (Source Code Management)
- Security Analyst (SAST)
- Dev-Ops Engineer (CI/CD)
There is currently no clear and concise way for a team lead to configure how their team will use GitLab to develop software. All these settings are very much spread out throughout the product, throughout the different stages, which makes them harder to find and organize. Each stage is typically configured by an expert in the area, and for a team lead it takes a herculean effort to bring it all together, with all of the correct settings to define how a team will work.
This is an opportunity area that would be good to explore more.
✏ ️
Job To Be Done When I'm starting a new project or service, I want a clear and concise way to access and configure all the settings my team will need develop software on GitLab, So that I can immediately maximize my teams productivity and minimize any potential issues in the development process.
Personas to focus on:
📋
Expected Takeaways At the completion of the research around this concept, we expect to have a solid understanding on if this a feature we should pursue further for actual implementation with the quantitative and qualitative data to back that up. Additionally, we will have some initial UX concepts to work off of, when we do go into releasing the first MVC.