Hi

I suggest to use the concept of branching . You can create a branch for every cycle and then merge it with the main ruleset when the cycle ends. Refer this for details  

Hi,

I donot think we can do anything much on this, as if we have to do a deployment to higher env, we need a ruleset to move to make life easy. And usually even though we do  short sprints, unless we are moving the code to a higher env, we may not need a new Ruleset, and can continue to use the same ruleset across sprints. And we can roll on the Rulesets only when the code is moving to higher env.