I understand that the Pega Modernization Toolkit can help identify the number of UI rules (like sections, harnesses, custom controls, etc.) that need to be modernized for a move to Constellation.
However, is there any tool or sizing framework that goes a step further and provides effort estimation—something like a sizing wizard that could help quantify development and testing effort based on rule types, complexity, or guardrail warnings?
Looking for inputs from others who may have used internal tools, estimation templates, or best practices for planning Constellation migration initiatives.
Thanks!
@Pavan Kumar Koduri timely ask. This Expert Circle had 2 webinars this week on the Modernization Assistant. If you missed out, the reply will be up on Pega Community shortly, in the last 15 minutes we talk rough guidance for effort.
I suggest watching the reply, but high level this is subjective, based on the experience of the person, the complexity involved. Our discussion suggest this would be a good starting point, but you should evolve as you learn from practice.
Constellation Adoption Strategies
I should also stress, you do not have to migrate to Constellation, careful consideration should be made if you need to migrate existing builds.
There are things like blended UI and coexistence that can mean you can run both infrastructures at the same time, meaning new things can be Constellation and you can still run your existing items in Traditional UI
@MarcCheong Hey Marc, Could you please share the title of the videos?
Kind Regards,
Subhajit
