Sprint review for Distributed Teams with Timezone Differences
I'm currently working with teams that are composed of people from different parts of the world (with different timezones). SM and devTeam are in a same time zone (Asia). PO and customer are in a different time zone (America). And since the english is not good in our local team and time zone problem, we use email communication during sprint and only wil have call meeting when we discussing requirements.
We don't have sprint review meeting now. At the end of sprint, we always release all completed functions to a similar production environment, and then PO will use it and give us feedback. PO also will show it to Stake Holders and synchronous feedback to us. Once PO accept the functions, we will release it to product environment.
Question: We don't have normal sprint review meeting in each sprint. Is this acceptable? Or does it not conform to agile thinking
I really would like to hear you suggestions. Many thanks in advance!
Once PO accept the functions, we will release it to product environment.
Why this delay? Doesn't the PO trust the Developers to build something immediately usable each Sprint?
We don't have normal sprint review meeting in each sprint. Is this acceptable?
The Scrum Guide makes it clear that the purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. If that doesn't happen, what are the consequences likely to be for product value?
Thanks for your comments Ian Mitchell.
Once PO accept the functions, we will release it to product environment.
Why this delay? Doesn't the PO trust the Developers to build something immediately usable each Sprint?
Since the real product environment is the environment in which the factory has been running all along. We deploy product usable each Sprint to a similar production environment. PO and customer need to Trial product and give feedback before release to real product environment, and also factory operators need time to notify relevant personnel in the factory and configure related databases as needed. So the real product release always a little delay.
We don't have normal sprint review meeting in each sprint. Is this acceptable?
The Scrum Guide makes it clear that the purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. If that doesn't happen, what are the consequences likely to be for product value?
We always get feedback from PO. Our meeting always is at our evening and the ealier morning of PO since the different time zone problem. We both attend meetings during non working hours. It's difficult for us to organize a meeting with everyone present. So PO always attend meeting with stakeholder/customer in a individual meeting and then synchronous feedback to us.