# data[].attributes.headline
Shoutout to our Engineering and Product teams for supporting us putting out the Transflo fires. Even though this felt like, "well what's going to fail next?" both Product and Engineering were ON TOP of their game for quick resolutions. Incredible work by Fifth Wheel and Spice Route. 

# data[].attributes.subject
Shoutout to our Engineering and Product teams for supporting us putting out the Transflo fires. Even though this felt like, "well what's going to fail next?" both Product and Engineering were ON TOP of their game for quick resolutions. Incredible work by Fifth Wheel and Spice Route. 

# data[].attributes.headline
Late deploy of tickets that blocked full E2E testing. Each time there was a new test case, a new issue would arise that the team didn't know existed prior to the previous fix. 

# data[].attributes.subject
Late deploy of tickets that blocked full E2E testing. Each time there was a new test case, a new issue would arise that the team didn't know existed prior to the previous fix. 

# data[].attributes.headline
 This felt like a hot potato on who was responsible for a fix (Mastery vs Transflo). The back and forth caused Ruan to lose confidence in the functionality of the integration. 

# data[].attributes.subject
 This felt like a hot potato on who was responsible for a fix (Mastery vs Transflo). The back and forth caused Ruan to lose confidence in the functionality of the integration. 

# data[].attributes.headline
Communicate requirements with Product and Engineering to make sure there is a clear understanding of the integration needs, including dates for go-live. Create a checklist and ensure everything is completed. 

# data[].attributes.subject
Communicate requirements with Product and Engineering to make sure there is a clear understanding of the integration needs, including dates for go-live. Create a checklist and ensure everything is completed. 

# data[].attributes.headline
TEST EARLY!!!! IMPL/CE needs to test with the client a lot earlier in the project and catch any outstanding issues so they can be prioritized and fixed within our normal release cycle. Our burning fires were last minute issues we didn't know about due to inability to complete testing E2E. 

# data[].attributes.subject
TEST EARLY!!!! IMPL/CE needs to test with the client a lot earlier in the project and catch any outstanding issues so they can be prioritized and fixed within our normal release cycle. Our burning fires were last minute issues we didn't know about due to inability to complete testing E2E. 

# data[].attributes.headline
Engineering and Product rallied around to help resolve issues as they were coming in. Very fast turnaround time. 

# data[].attributes.subject
Engineering and Product rallied around to help resolve issues as they were coming in. Very fast turnaround time. 

# data[].attributes.headline
No ownership of tracking Story issue types at Mastery

# data[].attributes.subject
No ownership of tracking Story issue types at Mastery

# data[].attributes.body
This TransFLo integration was one of the first (if not 1st) with a clients on-prem system and not a cloud agnostic api. In the future before any agreement with a client on a potential integration to an on-prem offering a thorough deep dive needs to occur collaboratively with Product AND Engineering. As each installation of a 3rd party application to an on-premise client could be unique. on top of that,  fire-wall configurations, network complexities and security requirements around the connection will be unique to each future client.

In MANY of these cases our clients will look to Mastery to drive the connection even though they are contracted with the 3rd party vendor (in this case TransFlo) who when they let Ruan down was still perceived as a Mastery issue.

# data[].attributes.body
Clear and open communication between Ruan and Mastery teams. Quick turnaround to run through working sessions.

# data[].attributes.body
Lack of environment build configuration tracking.

# data[].attributes.body
Environment configuration / Feature Flag activation tracking was not present in JIRA for the Production environment. Changes were made in the UAT environment without consideration for how they would be updated in production. Single issues showing as "Released to Prod" when the change was only reflected in the UAT environment.

# data[].attributes.body
Feature flag configuration out of sync between environments. In order to test the configuration, the FF settings should be an exact copy between environments.

# data[].attributes.body
Lack of replicated environment to run true ETE & UAT tests (outside of Production)

# data[].attributes.body
JIRA management:
* How much of the integration is captured within each story / epic / initiative?
* Should comments on individual changes be included in the story that addresses the individual feature or at the initiative level?
* Environment configuration should have a respective UAT & Production story to track completion of the effort within each environment. The integration consisted of multiple custom configurations that required tracking that existed on the backend.

# data[].attributes.body
Ensure UAT environment configuration is an exact replica of Production when performing ETE & UAT testing.

# data[].attributes.body
Maintain SME throughout the project. Many handoffs of this integration from Discovery to Implementation without a full understanding of development completed.

# data[].attributes.body
Unit test endpoints to ensure credentials are valid and working as expected.