The Agile School

I have a simple guideline for this Leave it to the teams - unsynchronized sprints Simple products with single teams working on it If you have a different independent products which rarely or doesn’t communicate with each other. Team will be more creative and it gives more flexibility. Because of all these unsynchronized releases there will be lot of churn so the management & PMO should use a lot of common sense in dealing with such cycles. Use synchronized sprints If you have a big product, with multiple teams working on it  If you a product portfolio of products/applications which communicates with each other  If you want to synchronize the release because of billing, reporting or any other similar reasons    Synchronization helps in large organization where we have to worry about lot of complexities. They will have a common reporting tool which can provide the correct view across all the teams. This helps in billing and other administrativ...