Phased Vs Big-Bang approach of Deployment for Core-HR Redwood ?
Summary:
Hi Team,
Can someone pls help with recommending which approach of deployment should be followed for rolling out Redwood Core HR for a client with extremely high number of personalization, phased approach wherein some specific workflows shall be identified and deployed in different phases or Big-Bang approach where we go-live for compete Core HR module in one go? We have identified 32 workflows/pages for which personalization exists via TDS, Page composer and auto complete rules.
Content (please ensure you mask any confidential information):
Just to add, the volume of personalization is very high on almost each workflow like Hire an EE, Add a Pending Worker, convert Pending worker etc, The deployment involves business rules for approx. 40 countries, and we have 14 languages in place already in responsive, we are seeking help in identifying approach which shall be best for us to follow to move to redwood for CoreHR.