- This forum has 200 topics, and was last updated 1 year, 4 months ago by .
-
- Topic
- Voices
- Last Post
-
- 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?
- 0
- 1 year, 4 months ago
- During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?
- 0
- 1 year, 4 months ago
- Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)
- 0
- 1 year, 4 months ago
- In Scrum, who is responsible for making sure the Development Team has a clear and properly refined Product Backlog?
- 0
- 1 year, 4 months ago
- You must be logged in to create new topics.