What is the main reason for the Scrum Master to be at the Daily Scrum?
You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it's a good idea to have teams organized by feature.What are the advantages of keeping component teams while starting Scrum?
How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?
How often should Scrum Team membership change?
Who should make sure everyone on the Scrum Team does his or her tasks for the Sprint?
When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
