Professional Scrum Developer (PSD I) practice assessment

#1. What is a cross-functional team?

All team members can perform any task needed

The team has all skills needed to turn Product Backlog items into "Done" Increments

The team has at least one architect, developer, designer and tester assigned to the team

Each team member has a specialist skill, and a secondary skill in at least one other area

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. This does not mean that Scrum expects the team to be made up of cross-functional individuals.

#2. How is software architecture designed with Scrum?

Because of the complexity involved, software architecture must be thought about and designed up front in a “Sprint 0” before any functional code is written

Developers have no concern about designing software architecture, they just add whatever code is needed to implement the functionality that is needed for the next Product Backlog item they work on

Scrum Teams recognise that all architecture is there to serve a purpose, such as to achieve quality goals and to enable valuable functionality – it is driven by turning Product Backlog items into valuable usable Increments. Architectural decisions are made based on risk and effort to change later

The architecture needed for each Product Backlog item must be decided as part of Product Backlog refinement, with all items in the Product Backlog refined before the first Sprint so that architectural decisions can be made by the Developers having considered the whole product

#3. What is the "Single Responsibility Principle"?

A class has one single responsibility and therefore should only have one reason to change

Each Developer takes responsibility to ensure one of the Product Backlog items forecast for the Sprint is Done by the end of the Sprint

Each of the Scrum roles have their own clear accountabilities

Each Scrum Team works on only one product at a time

#4. Who monitors the progress of work during a Sprint?

The Scrum Master

The Product Owner

The Project Manager

The Lead Developer

None of the above

The Developers are accountable for managing, executing and monitoring the plan for the Sprint. This plan is made transparent in the Sprint Backlog.

#5. What is the minimum amount of code test coverage needed to ensure good quality?

75%

85%

90%

100%

None of the above

Code coverage is only an indicator, and should not be considered to be a good measure of code quality.

#6. What are some of the benefits of TDD?

Select all that apply:

It helps to enable a software design to emerge that provides the minimum necessary to implement a solution

It results in code with good test coverage, with tests of good quality

It results in cleaner and more maintainable code

It reduces the likelihood of bugs

#7. What is Test Driven Development?

A process by which testers get involved in writing the acceptance criteria for user stories, and these then form the basis for development

A software development process that consists of a repeating cycle; write a test, write just enough code to make the test pass, refactor the code

An approach where all of the tests are written, before code to make all of the tests pass is written

An approach that reduces and can even replace the need for manual testing

#8. When should the software architecture be decided?

The software architecture must be decided by the end of the first Sprint

The software architecture must be decided before the first Sprint starts

Software architecture decisions should be postponed to the last responsible moment, when the team has learned as much as possible and making no decision would be more harmful than making a wrong decision

The software architecture should be decided before the Product Backlog is estimated, so that the Developers understand the work involved in development

#9. Which of the following are good measures of code quality?

Select all that apply:

Number of successful builds

Test coverage

Cyclomatic complexity

Maintainability index

Depth of inheritance

Lines of code per class

#10. It is mandatory in Scrum to use technical practices such as Continuous Integration and automated testing.

True

False

Scrum is a lightweight framework, on top of which complimentary practices can be added. Technical practices are not mandatory, but they could be a great benefit.

#11. If a Developer comes across some poorly structured code, what should they do?

Select all that apply:

Only do the work required to implement whatever they are currently working on as the Developer should only spend time on work that contributes to the current Sprint Goal

If the work to refactor it is likely to be substantial and/or the risk of doing so is high, they should raise it with the rest of the Scrum Team for a collaborative discussion on what to do

Developers should strive to leave code cleaner than when they found it

Raise a task on the Product Backlog to clean it up later in a hardening Sprint

#12. Who must attend the Daily Scrum?

Developers

Developers and Scrum Master

Developers, Scrum Master and Product Owner

Developers, Scrum Master, Product Owner and stakeholders

The Daily Scrum is the Scrum event for the Developers to focus on progress towards the Sprint Goal and produce an actionable plan for the next day of work.

#13. Which of the following does Scrum prescribe as a way to measure the effectiveness of a particular Developer?

Select all that apply:

Lines of code written per day

Story points closed per Sprint

Defects fixed

Number of tasks completed

Scrum makes no such prescription

When using Scrum, the interest should be in the effectiveness and value delivered by the Scrum Team, not individual performance.

#14. While working on a Product Backlog item forecasted for the Sprint, a Developer finds a bug related to functionality that has been previously released. Which of the following is their best course of action?

Fix the bug, after all the Developers have an accountability to ensure quality

Bring the issue to the attention to the rest of the Scrum Team and have a discussion about what to do

Ignore it; the functionality was previously approved, so it is up to stakeholders or the Product Owner to raise it as an issue

If the Developer thinks they can fix it within 30 minutes they should, otherwise they should raise it on the Product Backlog as a new Product Backlog item

Bring the issue to the attention of the Scrum Team’s dedicated tester so that they can record the bug in their bug report

#15. Where does the Definition of Done come from?

It is created by the lead architect, since they have the most technical understanding

It is defined by the Product Owner, since they are the one with the product vision

It is the responsibility of the Scrum Master, since they are accountable for the effectiveness of Scrum

If there is already an organisational standard for the Definition of Done, the Scrum Team must follow it as a minimum, otherwise the Scrum Team must create one

#16. What is technical debt?

Defects in the product

Deferred work, often the result of decisions to trade quality for speed that can result in a brittle product

The gap between desired and actual velocity

Missing skills in the Scrum Team that are needed to produce “Done” Increments every Sprint

#17. What is meant by “Test First”?

Hire the testers first as they are the most important Scrum team members

Get sign-off from the tester on feasibility of features before asking programmers

Test feature ideas by asking users for their opinion before building them

Create tests before writing the code to make the tests pass

#18. During a Sprint, the Developers determine that they will not be able to complete all of the items forecasted. What should the Scrum Team do?

Renegotiate the scope, with a focus on how to still meet the Sprint Goal

The Developers should swarm on the items most likely to be finished so that there is something to show at the Sprint Review

Abandon the current Sprint and start a new one

Skip testing, and catch up with it in the next Sprint

Drop the Sprint Retrospective and Daily Scrum so that the Developers have more time to get the work done

During the Sprint, scope may be negotiated between the Developers and Product Owner as more is learned.

#19. Who can make changes to the Sprint Backlog?

Select all that apply:

The Developers

The Scrum Master

The Product Owner

Stakeholders

As described in the Scrum Guide, “The Sprint Backlog is a plan by and for the Developers.”

#20. "Self-management" means that Developers can work on whatever they want.

True

False

“Self-management” means that the the Scrum Team internally decides who does what, when, and how. This is within certain boundaries, for example, the rules of the Scrum framework and organisational standards. The Sprint is a container for the development work, and Developers should be focussed on achieving the Sprint Goal, every single Sprint.

#1. What is a cross-functional team?

#2. How is software architecture designed with Scrum?

#3. What is the "Single Responsibility Principle"?

#4. Who monitors the progress of work during a Sprint?

#5. What is the minimum amount of code test coverage needed to ensure good quality?

#6. What are some of the benefits of TDD?

#7. What is Test Driven Development?

#8. When should the software architecture be decided?

#9. Which of the following are good measures of code quality?

#10. It is mandatory in Scrum to use technical practices such as Continuous Integration and automated testing.

#11. If a Developer comes across some poorly structured code, what should they do?

#12. Who must attend the Daily Scrum?

#13. Which of the following does Scrum prescribe as a way to measure the effectiveness of a particular Developer?

#14. While working on a Product Backlog item forecasted for the Sprint, a Developer finds a bug related to functionality that has been previously released. Which of the following is their best course of action?

#15. Where does the Definition of Done come from?

#16. What is technical debt?

#17. What is meant by “Test First”?

#18. During a Sprint, the Developers determine that they will not be able to complete all of the items forecasted. What should the Scrum Team do?

#19. Who can make changes to the Sprint Backlog?

#20. "Self-management" means that Developers can work on whatever they want.

Results