In financial services, data is essential for storing product information, capturing customer details, processing transactions and keeping records of accounts; the relationship between products and their underlying data has always been symbiotic. A significant amount of data infrastructure is static, fragmented across data silos or based on legacy platforms. This has created an impedance mismatch between products and the underlying data.

I’m sharing my experience as part of transitioning various programs and projects in adopting agile principles, which in part or in total made them successful. This blog series will give a guideline of steps for an organization to successfully start Agile Transformation from scratch, from having no understanding of agile to being a successful team in delivering the objectives of the project.

Introduction Once upon a time documentation was one of the most important aspects of Quality Assurance and this was not limited to the functional test efforts but the non-functional testing as well. We spent days, weeks, months even creating Performance Test Strategies, Approaches, Plans, Test Case, Completion Reports etc. Most of these documents were required before any automation could be written and before a sensible performance testing framework could be considered.