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

#3. 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

#4. 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

#5. How should the Sprint Backlog be ordered?

Scrum does not prescribe ordering of the Sprint Backlog

The ordering of Product Backlog items on the Sprint Backlog should be the same as they were when they were on the Product Backlog

By whatever the Developers say

By whatever the Product Owner says

#6. What happens in-between Sprints?

The Scrum Team has some downtime to catch up on reading emails, and to carry out hardening tasks on the product such as refactoring and bug fixing

Nothing. As soon as one Sprint ends, the next Sprint starts

The Increment is released and the Scrum Team monitors its performance to validate that it delivered the expected value before starting the next Sprint

Enough time is spent refining the next set of Product Backlog items so that the next Sprint can begin

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

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

#9. 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.

#10. Which of the following describes the Definition of Done?

Select all that apply:

A formal description of the state of the Increment when it meets the quality measures required for the product

It creates transparency by providing a shared understanding of what it means for work to be completed

If the Definition of Done is part of the standards of the organisation, all Scrum Teams must follow it as a minimum

The Product Owner has the final say on whether the Definition of Done has been met and if an Increment can be released

#11. Which of the following activities should a newly formed Scrum team focus on? (pick the best 2 answers)

Select all that apply:

Have the Product Owner share and discuss the Product Goal

Create a Definition of Done and ensure that there is a shared understanding of it

Go out to lunch together so that the Scrum Team get to know one other

Decide what the team’s velocity will be

Configure the electronic project management system

#12. 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

#13. 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

#14. 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

#15. The last of the coding tasks has been completed for the Sprint and the Developers are discussing pulling an additional item from the Product Backlog into the Sprint. What should the Developers consider?

Select all that apply:

If pulling in the item would impact the Sprint Goal

If pulling in the item would put the Increment for the Sprint at risk

They should see how they could contribute to achieving the Sprint Goal and getting Product Backlog items forecasted for the Sprint "Done"

They could first see if any of their spare capacity could be used to pay off technical debt, perform some exploratory testing or be used for learning

They should first check that the item meets the Definition of Ready

The most important things to consider when discussing pulling in additional Product Backlog items into the Sprint is if doing so risks the Sprint Goal and the Increment. The Developers may also consider using the capacity in other useful ways, such as paying off some technical debt or using the time for self-learning, instead of always looking to pull the next item from the Product Backlog.

#16. 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

#17. How is Product Backlog refinement carried out?

The Product Owner, Scrum Master, architect and QA specialist collaboratively develop Product Backlog items, order them in the Product Backlog, and estimate how long each will take

Once per Sprint, the lead analyst presents user stories from the Product Backlog to the Developers, who use planning poker to estimate them in story points

Product Backlog refinement is carried out during the Sprint Planning event. Carrying out refinement in Sprint Planning and limiting Developers involvement until this point reduces waste as the Developers learn what needs to be done “just in time”

Product Backlog refinement is any collaborative, ongoing approach that the Scrum Team chooses to use to break down and further define Product Backlog items so that they are deemed ready for selection in a Sprint Planning event

#18. What is "Mobbing"?

When stakeholders form a group to overrule a decision made by the Product Owner

A form of Product Backlog refinement where all of the Developers come together to learn about and size Product Backlog items

A software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer

When more than two Developers work on the same Product Backlog item at the same time

#19. 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

#20. 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

#1. What is a cross-functional team?

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

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

#4. How is software architecture designed with Scrum?

#5. How should the Sprint Backlog be ordered?

#6. What happens in-between Sprints?

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

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

#9. Who must attend the Daily Scrum?

#10. Which of the following describes the Definition of Done?

#11. Which of the following activities should a newly formed Scrum team focus on? (pick the best 2 answers)

#12. What is technical debt?

#13. What is Test Driven Development?

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

#15. The last of the coding tasks has been completed for the Sprint and the Developers are discussing pulling an additional item from the Product Backlog into the Sprint. What should the Developers consider?

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

#17. How is Product Backlog refinement carried out?

#18. What is "Mobbing"?

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

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

Results