# data[].attributes.headline
Walkthrough of MOP activity in advance -Nadine

# data[].attributes.subject
Walkthrough of MOP activity in advance -Nadine

# data[].attributes.body
UAT should be involved right from the discussion phase so that all alignments and requirements are clear and they have done proper validations in LAB

# data[].attributes.body
Post launch if product is live and we are still getting issues then start logging tickets/incidents for each interactions along with reporting them over chat so that all such issues and their resolution can be tracked and discussed as lessons learned later. I find it difficult to navigate over all chats later after few days to count how many issues were reported and which team has provided resolution for same - Avinash

# data[].attributes.headline
Clearer call out of Customer or Channel experience Impacts

# data[].attributes.subject
Clearer call out of Customer or Channel experience Impacts

# data[].attributes.body
We need to make sure it is clearly understood by CE and Channel teams of potential impacts of release night, i.e. portal closing early on release night impacting BC channel. While this was announced several times in cross-functional meetings, maybe we need to get sign-off from impacted teams to ensure alignment. - Nadine

# data[].attributes.body
Having the deployment stakeholders connected on the same page during the production activity is important to keep track of deployment events, and timely updates.- Raghu

# data[].attributes.body
During a code releases, we should limit the config changes and try to bifurcate those across diff maintenance windows.

# data[].attributes.headline
Test all existing combinations of plans 

# data[].attributes.subject
Test all existing combinations of plans 

# data[].attributes.body
I suggest we test all existing combination of plans e.g. 30-day, 90-day etc.. to ensure that the frontend is properly displaying the information captured from the backend based on the plan criterias - Vince

# data[].attributes.body
Having all cross functional teams on one common platform is really great practice

# data[].attributes.body
We should not club such multiple releases, where we touch multiple platforms, as this will be hard to troubleshoot the root cause lies on which platform.

We should focus on planning such activities that comes as a package, e.g- Accenture and Digital planned release for KPre LTP has been planned for tomorrow, and avoid multiple platforms level release on a single day.- Raghu

# data[].attributes.body
Release planning meetings should include all stakeholders - there shouldn't be multiple meetings to keep reviewing the release strategy when not all participants are available.

# data[].attributes.body
Suggest we have a wider sharing of both test SIMs and Credit cards available, as we needed them due to the SALT issue for example. - Nadine

# data[].attributes.body
I suggest we run all Critical test cases that includes more than 1 function, and ensure we don't take for granted that since one of the two function works, that the other one will automatically work e.g. The 2FA password reset flow was tested with the Email function, and most likely missed with the SMS function since an issue was identified a couple days post launch - Vince

# data[].attributes.body
in general MVNE rate plan launch should include CE change lead or CE GTM (BAU). However, with big projects like Phoenix there is a CE GTM prime assigned and rate plans is critical to be shared from MKT to the prime before it's already posted on WSC. information must be worked on in Onesource at the same time its posted in WSC. Marc

# data[].attributes.headline
Continue to provide project updates via GChat or email. :)

# data[].attributes.subject
Continue to provide project updates via GChat or email. :)

# data[].attributes.body
Ensure that test stores are properly configured prior to the release & that test outlets are included in any automated CPMS configuration changes - with clearly defined expected behaviors after the change.

# data[].attributes.body
It was good to have a BETA environment to test ahead of time the changes within production.

# data[].attributes.body
Keep all verbiage related changes as a config change not a code level change so that it can be updated without any additional code level deployment if UAT identifies any issues with content over night.

# data[].attributes.body
We faced some technical challenges with the Kong POC during our MW, as he did not had the required platform knowledge.- Raghu

# data[].attributes.body
Having POC's from BT side will be much needed for this kind of Big release

# data[].attributes.body
Command centre hangouts chat was really helpful. It was a great way for issues to be flagged and resolved quickly. It also kept everyone in the loop with the progress of the resolutions

# data[].attributes.body
We should continue to maintain  Google Chat for Command Centre before during and after MOP - Nadine

# data[].attributes.body
Complete UAT in short period of time

Prioritizing exercises

2000+ test cases down to 1070 for WSC

Satisfied with test lead and testers

Marc

# data[].attributes.body
More hands on for CE with the regression

BAU engagement (project team to include CE)

Setting proper expectation on UAT turn around ahead of time with each PM workstream

# data[].attributes.body
With critical releases like this, we should continue interlocking MOP the same way we did for this release.

# data[].attributes.body
MOP Timelines Interlock should be part of every major release- Raghu

# data[].attributes.body
Need to include a SALT / payment processing prime either live or on standby during the MOP night - Nadine