Scrum PSD - Professional Scrum Developer 1 (PSD I)

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

Detailed Explanation: According to the Scrum Guide, Developers are responsible for all activities required to produce a Done Increment, including testing. While other roles may contribute insights, the team ensures quality through their combined skills.

Detailed Explanation: Continuous Integration fosters transparency by identifying integration issues early and providing rapid feedback. It also enhances collaboration by encouraging frequent communication and integration.

Detailed Explanation: The Product Backlog is a dynamic artifact that evolves as the Scrum Team learns more about customer needs and product requirements. It reflects Scrum's empirical nature.

An architecture spike is a small development activity to learn about technical elements of a proposed solution.

The scrum guide says: "The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint."

Refinement meeting and release planing are no scrum events. The others are, and they are all about feedback: inspection and adaptation. (And in order for the inspection to have a good outcome, the artifacts need to be transparent)

This should not be too much in a healthy situation, and this also doesn't imply that the developers can control the PO. But when the developers need the product owner to clarify or renegotiate the work to be done, it will be an impediment if the PO is not available.

Branching means that you create a new version from the code that exists indepently from the original code. It is not isolated forever, it can be merged back later.

Releasing the product at the end of the sprint doesn't relate to one item and when it's done. Code coverage does, but it's the worst criteria in this list, because it's a stimulus to write tests that cover a lot of lines rather than cover the functionality.