Understanding the importance of the functionality to achieve the business goals of the clients
initially, some of these scenarios were considered as non-priority
understanding of real user business scenarios
feedback from customers: how to improve our product
The first client bugs
unique user platforms and configurations
initial orientation to a specific client group and a platform related to business promises
Check UX Hypothesis
UX gaps and omiisions
corrected / improved a number of scenarios / functions
creating a new customer experience
change generally accepted
Built a process of interaction with the Help Desk service
Employees training
Solving the real users problems
Team became ready for release
It is IMPORTANT when Teams of professionals work on the project, united by a common goal and understanding of the product
product development team
project managers
team of promoters
support team
Understanding what customers want now from CBT
fully working product with a part of unimplemented functionality that does not affect on the main business scenarios
disagreement with the work of the functions / partial non-implementation is resulted in negative feedback, up to the decision of refusal of the product
We are ready for release!
How we could improve testing
Adaptation and improvement of regression testing scenarios
Expanded the test data
accounts
according to updated user groups
platforms
new data types
Update cards for HD
The main problems we faced
The unwillingness of the Team to simultaneously develop new functionality and lead customer support
creation of regulations
Unexpected using of the system
new scenarios
Difficult localization of client bugs related to local cryptographic problems
Legacy client platforms
small screens, outdated OS, crypto-providers
Inconsistency of received business requirements and reality
the expected types of clients / client environments and reality
Interaction with product managers and promoters
Not all clients participating in the PTA were loyal
How CBT affected on new iterations
T2M increased
It was necessary to perform work both on product support, problem solving of real customers, and to continue work on creating new product functionality.
The scope of iterations on the development of new functionality has not been truly reduced.
High loaded prerelease / release days
Regression systems + work on client bugs, some of which required hot-fixes
Team loss of focus
Team defocused
If CBT would start now, then
follow the recipe for beta testing: https://www.xmind.net/m/JvrB/