A core tenet of Agile Product Development is the ability to deploy an A/B testing strategy. Does anyone have a proposal on how to deploy A/B testing for high volume process flows where state and flow specifics are contained within longer lived work objects? For example, if I would like to A/B test a new process for instances of Work Class Foo, business traffic creates 100 instances of the new Foo, and I don't like what I see. Now I need to revert the B instances of Foo to their corresponding business state of where they should have been in the original process, e.g., back into A instances of Foo. It seems that could certainly be done writing an activity but that level of additional overhead required to deploy an A/B test reduces the "Agility" available in the Agile model. Any simpler way to do this within the guard rails?
Share this page
Moderation Team has archived post,
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 5 Sep 2017 8:35 EDT
Brian Albere (ALBEB)
Pega Technology Scrum Master
Before we even discuss Activity vs. non-Activity options, I'd like to hear more about how specifically you plan to approach this. When using casetypes & stages, it may make sense to have two classes, FooA and FooB, that inherit the same data model but have different stages & processes. To convert a case from FooA to FooB, you would have an activity that does a page-change-class from one to the other followed by a pxChangeStage to the corresponding stage, however that would be "behind the scenes". The user would most likely perform bulk processing on the cases in FooA and choose a Convert flow action which you've supplied that calls this activity.