Question 1

What are the possible consequences of a Product Backlog that's too vague?

Options :

A : The team could become too reliant on external consultants for decision-making.

B : The clarity and transparency of the Product Backlog could be significantly clouded.

C : The development team might complete tasks ahead of schedule too frequently.

D : The clarity of the Product Backlog might intimidate new team members.

Answer: B

Question 2

Why is the Product Backlog considered ordered but no prioritized?

Options :

A : Many items can have the same level of priority but there is only one order

B : The Product backlog is neither ordered or prioritized

C : Because prioritizations harm agility

D : Using a Monte Carlo analysis leads to orederng instead of prioritisation

Answer: A

Question 3

True or False: User stories are the only acceptable format for Product Backlog items in Scrum.

Options :

A : FALSE

B : TRUE

Answer: A

Question 4

Stepping into the shoes of an outgoing Product Owner, you're greeted by a Product Backlog brimming with over 1000 items. How do you begin to tackle this colossal list?

Options :

A : Add more items to the Product Backlog to ensure no potential feature is overlooked.

B : Prioritize for value and streamline the Product Backlog to enhance its clarity and manageability.

C : Divide the Backlog into smaller sections without assessing the value, aiming for quantity management over strategic clarity.

D : Postpone dealing with the Backlog-s size and focus on other priorities, assuming it will self-regulate over time

Answer: B

Question 5

Which of the following are the correct components of the INVEST acronym?

Options :

A : Independent

B : None of these

C : Testable

D : Negotiable

E : Estimable

F : Small

G : Valuable

Answer: A,C,D,E,F,G