My team and I are working with iterations of two weeks (trying to use our own version of Scrum) and we try to deliver a new version after every iteration.
After an iteration we let the stakeholders test our new version on a staging environment and they send us feedback. This feedback will be processed and the smoothed version will be deployed to production after we get an OK from all stakeholders.
This way of working is working fine sometimes, but in some iterations we are experiencing problems plannings wise. At the start of our next iteration, it is still unclear how many feedback we will get on our deliverable, so we can't really estimate the time needed to process the feedback in our iteration.
Can someone give us some tips about how to incorporate a correct feedback loop inside or workflow? Maybe we can deliver the deliverable two days before the end of our sprint, so we know how many feedback we have on the moment we start our sprint? I also thought about a workflow in which we let the stakeholders test the features during the sprint, so we can process the feedback in the same iteration we developed the feature.