PSD Sample Questions Answers

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.

There is no sprint 0, architecture won't take care of itself and there is no architect role. The architecture is an ongoing discussion and growing construct. There are guidelines and principles in place.

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

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."

The scrum guide says: "The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. "

There is no time in between sprints, so there cannot be activities.

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.

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.

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

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)

Scrum doesn't know any other role than developer. The developers are cross-functional and have all the skills needed to create a usable increment. They are doing the work and responsible for the architecture.

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.

The product must be releasable and done must mean the same for all additions to the product. So they must have a DoD that can combined. There is no hardening sprint.

Unit tests are testing the smallest units of code possible and integration tests are testing the components of the system together. Unit tests aims at isolated pieces of behavior and integration tests could be composed of unit tests to test components.

All of these would good moments to update the PO with the work done.

Cross-functional is on team level and not on individual level.

This way there are no surprises near the end of the sprint or during delivery and the increment will be most stable as possible.

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.

Technical debt is the result of incomplete work going into the increment and poor design and architectural choices.

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

This is pretty much the definition of ATDD.

You should refactor as soon as possible, but before the tests passes it cannot be refactored, because then it is not esatablished just yet. So it would still be part of the first version if changes would be made then.

The design grows as more is learnt.

It is part of the increment, so it is part of the work of the developers.

Never should they reduce the DoD. They should be able to do the work their selves and therefore work with the product owner to reduce the scope. Since the product owner is responsible for maximizing value and making priorities, he is the go to person for matteres like this.

Refactoring is only about the own code, so not about changing an external interface or api.

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

In ATDD you start with writing tests to represent the requirement. Since you start with this, there is no production code to satisfy the test which is why the tests will fail.

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

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

The scrum guide says: "A new Sprint starts immediately after the conclusion of the previous Sprint."

Static analys is performed on code (and not a running program or build).

In TDD you start with writing the test before the code. This test cannot pass. If it does, the test is wrong. When the tests are written, the production code to satisfy the test will be written. Once all the tests succeeds, the product code is done.