Cross-functional teams are optimized to work on one technical layer of a system only

Answering: “True or False: Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).”

True or False: Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).
A. True
B. False

Answering: “True or False: Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).” Read More »

What are the advantages of keeping component teams while starting Scrum

Answering: “What are the advantages of keeping component teams while starting 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 know 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?
(choose the best answer)
A. Component teams have all the specialized skills needed to focus on their key competency.
B. Component teams generally have the skills needed to create a working Increment of software that provides business value.
C. Because they have worked together for some time, they are likely able to start producing shippable Increments faster than new feature teams would.
D. There’s less initial disruption than reorganizing into new teams. As they start, they will discover what works best, and how to potentially re-organize toward this.
E. There are fewer cross-team dependencies than working in feature teams.

Answering: “What are the advantages of keeping component teams while starting Scrum?” Read More »

How much time is required after a Sprint to prepare for the next Sprint

Answering: “How much time is required after a Sprint to prepare for the next Sprint?” (PSM I)

How much time is required after a Sprint to prepare for the next Sprint?
(choose the best answer)
A. The break between Sprints is time-boxed to one-week for a one-month Sprint, and usually less for shorter Sprints.
B. None. A new Sprint starts immediately following the end of the previous Sprint.
C. Enough time for the Developers to finish the testing from the last Sprint.
D. Enough time for the requirements for the next Sprint to be determined and documented.
E. All of the above are allowed depending on the situation.

Answering: “How much time is required after a Sprint to prepare for the next Sprint?” (PSM I) Read More »

Why do the Developers need a Sprint Goal

Answering: “Why do the Developers need a Sprint Goal?” (PSM I)

Why do the Developers need a Sprint Goal?
(choose the best answer)
A. Sprint Goals are not valuable. Everything is known from the Product Backlog.
B. The Developers are more focused with a common yet specific goal.
C. A Sprint Goal only gives purpose to Sprint 0.
D. A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.

Answering: “Why do the Developers need a Sprint Goal?” (PSM I) Read More »

You cannot copy content of this page