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 »

Which output from Sprint Planning provides the Scrum Team with a target and overarching direction for the Sprint

Answering: “Which output from Sprint Planning provides the Scrum Team with a target and overarching direction for the Sprint?”

Which output from Sprint Planning provides the Scrum Team with a target and overarching direction for the Sprint?
(choose the best answer)
A. Sprint Review minutes.
B. The Sprint Goal.
C. The release plan.
D. The Sprint Backlog.

Answering: “Which output from Sprint Planning provides the Scrum Team with a target and overarching direction for the Sprint?” 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 »

You cannot copy content of this page

$35 Exam Preps

Sale Ending Soon

Day
Hour
Min
Sec
Offer Expired
Add Your Heading Text Here