Question 1

What pitfalls might arise from a Product Backlog that's short on specifics?

Options :

A : It could lead to an unexpected surplus in the project budget.

B : Stakeholders might find the Product Backlog to be unclear.

C : It may cause the development team to ignore the Product Owner-s instructions.

D : It might result in the team having too little work to do during the Sprint

Answer: B

Question 2

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 3

Taylor, serving as the Scrum Master, is concerned about the recurring issues her Scrum Team encounters with understanding Product Backlog items and the subsequent scope debates that arise during Sprint Planning. What strategies could Taylor employ to improve the effectiveness of Sprint Planning for her team?

Options :

A : Avoid involving the Product Owner in Sprint Planning sessions to streamline the meetings, thinking their absence will reduce complexity.

B : Introduce a policy where the Scrum Master makes all final decisions on disputes and scope, undermining the team-s self-management and collaborative decision-making principles.

C : Allow team members to individually interpret Backlog items without group discussion, believing this will minimize arguments.

D : Prompt the team to allocate time for working closely with the Product Owner on refining both the Product Backlog and the individual PBIs within it.

Answer: D

Question 4

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 5

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