PSD Questions and Answers

The continuous restructuring of software to retain flexibility

Having the tester in the development team write the test plans before coding

Creating tests before satisfying them

Testing existing code before adding more code to it

Meet with the business analyst to ensure that the test is correct.

Write the minimum amount of product code to satisfy the test.

Run it again to make sure it really fails.

Implement the required functionality.

Refactor the test so the code passes.

They may update estimates for Product Backlog items.

They do not. The Scrum Master and the Product Owner are responsible for Product Backlog refinement.

They give input on technical dependencies.

They do not. The Developers are only responsible for prioritizing technical work.

They ask QUESTION NO:s to clarify the intent of Product Backlog items.

Managers assign individuals to teams

Get all the people together and let them self-manage into new teams

Scrum master chooses a few team leads that get to pick their team

The chief product owner divides the group in teams to make sure the teams will be cross-functional

Existing teams propose how they would like to go about organizing into new teams

Fix the bug

Revise the tests to hide the bug from the tests reports

Talk to the product owner

Stub out the code that causes the bug

Increase quality

Complain only in this session to avoid complaining in the rest of the sprint

Have more fun during the sprint

Increase effectiveness

Why is this sprint valuable?

When is this sprint going to be done?

How to improve the scrum process in this sprint?

How will the selected work get done?

What can be done in this sprint?

Who is going to do what?

It defines a state when the entire Increment is releasable.

It might be a subject of discussion during the Sprint Retrospective.

It is synonymous with acceptance criteria.

It is the sole responsibility of the Developers to define it.

It can only be extended; nothing can be removed.

Work together and self manage to create value

Design the full architecture before starting

Creating a plan for the entire project

Create a potentially shippable functionality in the sprint

Product goal

Sprint goal

Sprint planning outcome

Definition of done

Sprint Retrospective

Developers must stand up at the Daily Scrum.

Sprint Burndown Chart.

Release Planning.

All of the above.

False

True

False

True

True

False

Vague statements or untested assumptions

Assigning blame

Generic titles

Simple and repeatable reproduction steps

One bug per report

Every member can do every task

They work with TDD

They never argue

They do pair programming

Developers have the combined skills to create a usable increment

Never, it is the sole responsibility of the Product owner to refine the backlog

Only during the sprint planning

Anytime during the sprint

Only during the refinement meetings planned by the PO

Scrum team

The product owner

Developers

The scrum master lets them know whether they need to be preset

When all the tasks are completed by the Developers.

When the Sprint Retrospective is complete.

When all Product Backlog items meet their Definition of Done.

When the Product Owner decides enough has been delivered to meet the Sprint Goal.

Just before the first check-in

Just before the product is released

When the product owner asks for a build

Just before the end of the sprint

As soon as there is code in the version control system

Models are not used by agile teams

Models are maintained along with the software as it emerges

Models are assembly instructions for the developers

Modeling may be useful to increase shared understanding

Improving code quality

All of these

It is a nice way to work

Information sharing and learning

Efficiency

Build.

Security.

Design pattern selection.

Scalability.

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

Discover decisions to be made as soon as possible but postpone making those decisions until the latest reasonable moment.

Making decisions as soon as possible to close feedback loops as soon as possible.

The last moment in a Sprint when code changes are allowed; after this, only stabilization work should be conducted.

The last moment a Developer is responsible for quality; after this, the Tester is responsible.

Until everyone is done.

Max two hours for a one month sprint

Max two hours

Max four hours

Max four hours for a one-month sprint

As needed, taking into account a short term reduction in productivity

Every sprint to remain agile

Never, it will reduce the velocity

As needed, but it should not affect the productivity

True

False

Improves quality in the requirement itself.

Promotes the use of the DRY principle.

Tracking of completeness.

Using a code generation tool, the solution can be generated from the requirements model.

Clear acceptance criteria for each feature.

False, the scrum master does that

True

True, in line with what was promised to the stakeholders

True, if the developers have enough capacity

False, the project manager does that

False

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

Do all the work except for deployment

Complete the work in the within the foreseen time and costs

Create a potentially releasable increment from the product backlog items

Managers doing performance reviews by comparing one programmer’s code to another’s

Two developers writing code together, providing constant peer review

Two programmers writing code separately, but always review each other’s pull requests

Developer and tester work together to write and test code

Immediately.

Don't fix it immediately, but change the test to not show it as a temporary fix.

Don't fix it, but stub out the code that causes it.

Depends on what the product owner wants.

However much time the developers ask the PO to be present

40%, or more depending on stakeholders

100%

Enough to be aware of the increment’s value at the sprint review

After the tests passes

When preparing legacy code for unit tests

When I can see the debt building in the code

After the tests fails

Execution is fast

Independent of others

Includes exercising the persistence layer

Makes assertions about only one logical concept

Identifying a particular codebase as ready for distribution

Combining two or more versions of code into a single codebase

Copying a portion of a codebase to isolate it from the original codebase

Two or more developers working together to ensure proper coding and configuration management

Doing all work needed to meet the Definition of Done.

Updating Sprint tasks properly in the electronic tracking tool.

Keeping track of and estimating all undone work to be completed in a “hardening" Sprint.

Reporting Sprint progress to the stakeholders daily.

Screenshots or pictures of the bug in action, if possible

Explains some new system functionality desired

Includes build or version number where bug was found

Expected results and observed results

Provides simple and repeatable reproduction steps

Includes code for a proposed fix

Code review is done

Acceptance tests pass

Regression tests pass

The product is released at the end of every sprint

Code coverage 90%

It is a great way for Testers to contribute early in the Sprint as they can start creating all the tests from the beginning.

It increases collaboration between Developers as it requires Pair Programming.

It helps to identify gaps in understanding the desired behavior.

It might lead to better code as refactoring is part of the Test-Driven Development cycle.

It helps break down complex problems into smaller ones that are much easier to be tackled.

It makes Integration Tests obsolete and by doing so saves a lot of time.

A culture of continuous experimentation and learning.

To deliver value earlier and more frequently.

A tool-focused way of introducing DevOps, compared to a mindset way (second way) and organizational structure (third way).

Using automated build and release pipelines.

The first set of practices a team should apply before moving to the second way.