Expert Answer
Anonymous
I have handled multiple feature and integration program end-to-end. I will share an example with respect to the delivery of a partner integration program.
1. Align the scope with partner: We did a product walkthrough of the existing app with the partner to align them with the product user journey
2. API Documents from partner: Post the journey walkthrough, we request for the partner API for the loan onboarding journey
3. API Analysis and Documentation: Once we received the APIs, we do an exhaustive API testing and also map them with our existing application. During this phase, we evaluate if all the fields present in the partner APIs are relevant to the existing applications, feasibility check on the mandatory fields and parameters. Also evaluate workarounds in case of missing fields. This is then documented for the Engineering teams to consume for the tech solution and execution phases.
4. PRD Creation: Created a detailed documentation with relevant details like scope of the program, consents and tncs, API details, partner information, API workflow, user journey workflow stages, etc.
5. Product walkthrough and grooming: Align the engineering team with the scope of the program journey
6. Tech Solution: Finalize the implementation approach and alignment with all the relevant engineering teams required for the development. Finalize the internal contracts between engineering teams.
7. Roadmap and timeline plan: Create the execution plan, post discussions with all teams and align the same with the partner as well. Request the partner execution plan too for streamlining both team's timelines.
8. Development and Integration testing: During this phase, the engineering team completes the development and also conducts integration tests to confirm the changes are working end to end. the QA team, writes the manual and automation test cases for the E2E testing. Environment mappings are finalized for end to end testing
9. E2E Testing: The QA engineers execute all the test cases covering happy, negative and edge case scenarios. Bug reports are published, which the development team triages and fixes on priority for closure of this phase.
10. Product and Partner UAT: A workshop is conducted where the Product managers and Partner is given a demo for the entire journey to validate if they are aligned with the developed journey. Once teams have validated, a sign off is shared by internal and partner teams.
11. Production movement: A production production discussion is conducted to align on the backward compatibility of the changes, rollback plan and order of deployment before the production deployment date
12. CUG: A closed user group testing is conducted with selected real time customer, to check if the application is performing as expected on the live application
13. Agreement sign off: Confirm on all legal agreement closures before opening the feature to 100% live traffic
14. Customer Go-live: Whitelist users to be able to access the application.
