This epic drives Phase 2, Limited Adoption, of the feature readiness rollout. For more details about rollout strategy and the domains refer to https://gitlab.com/gitlab-org/architecture/readiness/-/issues/67+. ## Objectives Transform feature readiness from a validated concept into a proven practice that demonstrably improves deployment success and builds organizational trust this process delivers genuine value. ### Contribution - **Expand domain coverage**: Add content from 3-5 additional Infrastructure teams beyond Delivery - **Refine through usage**: Update templates based on actual review patterns and feedback ### Consumption - **Prove production value**: Successfully assess and deploy 3-5 production features using feature readiness - **Measure impact**: Quantify cycle time reduction and risks/gaps identfied - **Create success stories**: Document compelling cases that resonate with feature teams ### Automation In close collaboration with ~"group::feature readiness": - **Define tool requirements**: Specify automation needs based on Phase 1 learnings, with focus on AI-assisted workflows - Collaborate on tool specifications and validate implementations - **Enable scale**: Ensure tools create foundation for Phase 3 self-service model ## Directly Responsible Individuals (DRI) - @pursultani ## Participants - @niskhakova ## Exit Criteria - [x] 3-5 additional infrastructure teams contributed their content - [x] 3-5 production features engaged with the process - [x] 40% reduction in manual work through automation - [x] At least one published success story with quantified impact - [x] Support creation of enablement content - [x] Impact of limited rollout is measured --- <!-- STATUS NOTE START --> ## Status 2026-01-06 **Limited Adoption phase completed with measurable impact achieved.** :clock1: **total hours spent this week by all contributors**: 1 :tada: **achievements**: This work is completed because it has achieved measurable impact: - 3+ infrastructure teams engaged beyond initial ~"section::gitlab delivery" scope, establishing PREP as cross-functional infrastructure practice - 3 production features assessments are underway or completed, identifying critical infrastructure gaps before production - PREP Assistant automation reduced assessment time by 60-70%, exceeding our expectations (40% manual work reduction target) - LevelUp course, comprehensive documentation, and quick-start guides enable self-service adoption - Repeatable process established that shifts infrastructure validation left in development cycle, reducing post-release firefighting :arrow_forward: **next**: We can now conclude this epic and continue our work: - A new team is formed to continue PREP support and evolution. We will focus on direction and success metrics of the new team - Plan the next phase for self-service scaling based on Limited Adoption outcomes and learnings :notebook: **notes:** - We will report the related work to ongoing feature PREPs in ~"group::operate" BAU. - Thes [LevelUp course issue](https://gitlab.com/gitlab-org/architecture/readiness/-/work_items/81) is reopened for solution validation only. This is not a blocker for concluding Limited Adoption. - We will monitor DevEx feedback from https://gitlab.com/gitlab-org/architecture/readiness/-/work_items/84 for process improvements when it becomes available. _Copied from https://gitlab.com/groups/gitlab-org/distribution/-/epics/127#note_2985072796_ <!-- STATUS NOTE END -->