Free PSD Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

If you are not sure, review the daily scrum section in the scrum guide.

User Stories are not required in the Product Backlog as per the Scrum Guide. The Product Backlog is

a collection of all work to be done on the product, and it can include a variety of formats, such as

tasks, features, and technical requirements, not just user stories.

Product documentation can be part of a Done Increment if it adds value and meets the Definition of

Done. Scrum does not prescribe documentation but emphasizes delivering value to stakeholders.

It should be a working increment, but it's not mandatory to release it.

The sprint is the heartbeat of scrum, during the sprint the increment is created. The increment must

be usable and all the work that's part of the increment should adhere to the definition of done.

Best practices are based on past experiences and may not apply to complex, unpredictable

problems. Empirical approaches and experimentation are better suited to such challenges.

The scrum guide says: "The Scrum Team may also invite other people to attend Sprint Planning to

provide advice."

One product backlog per product

One product owner per product backlog, one product backlog per product

If you are not sure, please review the Scrum events section in the scrum guide

All the scrum events are timeboxed.

The DoD helps the developers know how much work needs to be done, and therefore they can

decide what should be part of the sprint. It also creates a shared understanding of what done means.

This is likely to include documentation, but that depends on the decisions of the organization and

team. Scrum does not dictate this.

Specific roles don't exist in scrum, developers are creating the value.

If you are not sure, please review the section scrum artifacts in the scrum guide.

Product owner is value optimizer. Of the product, which emerges by the work of the developers.

The working increment is the goal of the sprint and should be kept in mind. The self-managing aspect

of the teams is also crucial to take in mind. Stable velocity and optimally used developers are not the

scrum master's concern.

The first way of DevOps emphasizes optimizing the flow of work from development to operations to

deliver value to customers earlier and more frequently, reducing lead time.

These are all potentional topics for the sprint review. If you are not sure, please read the sprint review section in the scrum guide again.

The refinement is very important and can take quite some time for that reason, however, it should

not endanger the sprint goal.

Naming conventions help to make the code more readable and it can reduce naming clashes.