Hi @RajeshPrabhu below are my comments. >> We are essentially holding ongoing sprint development until prod issue hot fix patch is released. Will it not impact sprint timeline given we never know how long it would take for a hot fix change to close. Is it advisable ? Yes, with this approach the current sprint build activity will be hold. If assumed that hot fix is going to take more time then better take the hot fix for next release if possible. Else after each sprint you need to take DEV copy and use it for hot fix so that current sprint build will not be impacted. But with this approach you need to create a new PROD of each sprint as you will not be able to sync the existing PROD model with new sprint changes. >>If there is an ongoing spring UAT then we have to hold that as well. Follow the same process as development. Is that a right understanding? You need to maintain different UAT models for each sprint. Keep it in archived state and unarchive it when required, so that you can save space when the older UAT models are not in use. Else take a copy of PROD and perform UAT for hot fix. >> Would it not override hot fix changes when we put back ongoing sprint build ? Yes, it will. You need redo the hot fix changes after roll back in current sprint so that when current sprint went live there will be any issues.
... View more