Scrum PSD Professional Scrum Developer (PSD) Exam Practice Test

Automated builds are making builds of the code after every change to the codebase. As soon as something breaks, the developers get informed. In order to automate it, the build process needs to be cleary defined. They're a corner stone for CI.

All the scrum events are timeboxed.

They are concerned with everything that needs to happen to create a working increment. And they are self-managing, so resolving conflicts is something they should arrange as well.

Automated builds should be changed everytime the codebase gets changed. This happens the first time when the first bit of code gets added to the version control system.

Cyclomatic complexity is a number expressing the number of different paths that can be taken throughout the code. Higher means complex code.

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

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

An increment is the usable value added in the last sprint plus the usable work of all previous sprints.

You can't really say anything because you don't know what the unit tests are testing and whether they are correctly representing whether the application is working correctly. However, if all the tests passes you didn't break any already existing tests. Also, if none tests existed yet, you did not break them.

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.

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

The scrum master doesn't need to be present during the daily scrum. Neither does the daily scrum need to consist of three questions, which is a commonly chosen format though.

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)

There is no hardening sprint, there are only regular sprints. If it's an ever recurring non-functional requirement, it can be added to the definition of done. If it's not it can be added (as a criteria) in the product backlog (item).

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.

Pair programming means that two developers are coding together and performing live peer review. This will enhance the effectivity as it leads to increased code quality. Regardless of your opinion, when answering QUESTION NO:s about pair programming, know that it's considered a really good practice for PSD. And in case you are wondering, the instructor of the course is also a big fan.

Tests are part of the development, and the development is done by the developers. There are no specific roles in scrum, even though members of the scrum team can have their own expertise.