PSD Professional Scrum Developer (PSD) Questions and Answers

The design grows as more is learnt.

Architecture emerges in scrum during the adding of functionality. The plan for the rest of the project cannot be made by the developers, they should just focus on their sprint.

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.

Test first development is a different way of saying TDD.

if the documentation is adding to the quality and maintenance of the software this is definitely a good argument for documenting every sprint. Just because that's the way it's done and we don't want change is not a good reason. Tooling that requires is also isn't. And the scrum master cannot demand this kind of things. If the company's definition of done says so, you must :)

A ready product item needs to be able to be done in a sprint (scrum guide). In order for it to be ready, the product owner and the developers need to understand it well. Tracking tools and requirements analysis and how user stories should be made isn't part of scrum or the best practices for development.

These are the three topics mentioned in the scrum guide. Who is going to do what is not determined upfront, when the sprint will end is fixed and doesn't need to be discussed, what can be done to improve the process is for the sprint retrospective meeting.

In the scrum guide it says: "The Scrum Team may refine these items during this process, which increases understanding and confidence."

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

Scrum requires no development practices, but good development practices do help and make scrum more successful.

you don't want to blame anyone, have vague titles of make vague statements. It needs to be clear and constructive, and focussed on one specific problem. It should als not contain feature requests.

It is not fixed, it is a live artifact that will grow and change as more is learnt. The product owner orders it by value.

The product owner can cancel the sprint if the sprint goal becomes obsolete. This is a very rare event. It can happen when a company losing a client or the client decides to take a completely different turn.

One product backlog per product

Review the scrum guide section sprint planning if this is still an uncertainty for you.