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

Can you explain the rationale of a Product Backlog?

Options :

A : To be the single source of work that will add value to the product.

B : To organize the company-s participation in trade shows and conferences.

C : To create a playlist for the office background music.

D : To tally the number of coffee cups used by the team each day

E : To outline the lunch menu for the team for the upcoming month.

Answer: B

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

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

As the new Product Owner facing a Product Backlog of 1000+ items, how do you work through this extensive backlog?

Options :

A : Delegate the entire Backlog to the development team for them to decide what to work on.

B : Maintain the Backlog-s size to demonstrate the product-s comprehensive potential to stakeholders.

C : Commit to implementing all 1000+ items, assuming that more features will always result in a better product.

D : Concentrate on delivering value by trimming down the Product Backlog, making it more navigable and transparent.

Answer: D