Overview
OTDRP process is an extension to ARB process and technical leads working on design document make sure to compliance with solution guidelines provided by Architecture Review Board and same time follow ODP design principles at platform level
There will a technical design group at each platform level accountable to a create technical document wherever applicable.
The Responsibilities of Technical Design Members
Prior to PI Planning, Teams and ART will determine their capacity. First step is to estimate starting capacity, then allocate capacity to type of work. New Epics/Enablers and Tech Debt and Maintenance usually take the most of available capacity. Recommendation is to allocate 80% of available capacity to New Epics, 10%, to Tech Debt and 10% to Enablers, although this can vary by Teams/Squads and ARTs.
1. Identify feature or story require technical design document
2. Identify feature or story
3. Setup design review meeting at platform level
4. If needed, submit an ARB request
- Needed clarification on initial ARB solution note or Missing ARB notes
- There is any security, performance, network or infrastructure related concern with the implementation
- Data Mapping Issue
- Change in integration agreement
5. Responsible to complete design documentation on confluence
| AEM | FED | CDS | CCV2 | SFSc | Akamai | DAM/Tenovos |
|---|---|---|---|---|---|---|
| Torin Segstro, Gavik Wadhwa, Priya Sharma | Dan Webster | Praful Rajawat | Ravi Kumar | Pranav Pandit | Torin Segstro, Charlie Zhang | Torin Segstro, Lloyd Ramnauth |
