...
| Page Properties | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
3 weeks (Sample dates: Sep 2-20): Make configurations in all UC PSBs, P2P configuration instructions (UC only; note ‘rota automation recommendation’ above)
6 weeks (Sample dates: Sep 23-Nov 8): Testing in pairs, option to review/discuss testings in RS OST meetings - RS OST decided to extend this testing to Nov 27, 2024 (10/30/2024)
2 weeks (Sample Dates: Nov 11-Nov 22): Discuss and evaluate tests & seek feedback from stakeholders about moving forward in production - RS OST decided to change this date to Dec 2 - 13, 2024 (10/30/2024)
1 day (RS OST meeting, Sample date: Dec 4): yes/no move forward with P2P in production - RS OST decided to change this date to Dec 18, 2024 (10/30/2024)
If yes, implement in production:
1-2 days, coordinated (Sample date: late Jan 2025 or early Feb 2025): Make configurations in all UC production Almas
2-6 months (Sample date: Feb 2025 - July 1 2025 - note: might be concurrent with other large project): go wild
After 1 month (sample date: August April 2025): check analytic reports for these requests
After 6 months (Sample date: Dec August 2025): check in, continue? Undo? expand?
...
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
RS OST |
| RS OST decided to table project at testing phase until after Tipasa implementation, expected to pick up Sept 2025 | |