PSD Professional Scrum Developer 1 (PSD I) Questions and Answers

Work with the QA departments on the increment of the current sprint

Update the project plan with stakeholders

Refine the backlog

There are no such activities. The next sprint starts immediately after the current sprint

The scrum process

All of these

The increment

Coding and engineering practices

Meet with the team to see why it fails

Change the test in a way that is passes

Run it again to verify it fails.

Write the code to satisfy the test

The developers

Product owner

The company’s database specialist

Scrum master

Scrum is a framework for developing and sustaining complex products.

Each component of scrum serves a specific purpose and is essential to Scrum's success

Scrum is based on empirical process control

Scrum is like traditional project management, but then with project managers replaced by self-management.

Scrum is a methodology based on empirical process control.

Release documentation

Build automation

Security

Design pattern choices

Scalability

Finding bugs

Tracking quality metrics

All developers are responsible for quality

Verifying the work of the programmers

Scrum has no tester role

Scrum team

The product owner

Developers

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

True

False

True

False

The feature-branch is generally kept in a buildable state.

Know immediately how a change affected the product.

Reduce effort and risk when integrating changes.

Readability of code is improved.

Extracting methods

Reordering method parameters to improve readability

Changing external interfaces or APIs

Renaming things to be more logical

Extracting interfaces

An approach to make decisions easier to change in the future and find the best possible point in time to make decisions.

Starting development of a software product requires a clear understanding of the underlying software architecture, and Emergent Architecture describes the process of creating this final architecture.

In Scrum there is no Architect-Role; therefore, architecture emerges naturally.

Enterprise Architects must be involved to create the foundation of each software product.

The software architecture emerges solely from decisions the Developers make from a technical perspective.

The Developers may forecast less overall work in Sprint 8.

Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting.

There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint.

The Developers carry over incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work.

The Scrum Master adds additional Developers for Sprint 8.

The Developers put incomplete Product Backlog items back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8.

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

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.

Deductive

Hybrid

Empirical

Technical

Exploratory.

Functional.

Unit.

Integration.

Manual regression.

Performance.

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

The person who is responsible for configuration management within the team

The person who broke the build

The tester responsible for validating builds

The next person who needs the build to complete successfully

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.

A technical requirement that must be satisfied

A bug

Great development practices

Something that completes the test coverage of a system

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

Every team must make their own DoD, a meeting should be organised so that the differences are known.

It depends on the product owner

All development teams must have a DoD that makes their combined work releasable.

Every team uses its own. The differences are discussed in a hardening sprint.

An incremental and emergent approach to software design

A software development technique based on automated tests

A predictable way to develop working well-organized code

Creating a manual test script before writing code

Having testers involved in the development process

Release planning

Daily scrum

Sprint review

Sprint retrospective

Refinement meeting

A software development practice used by integration teams to create best practice branching and merging strategies

A software development practice that continuously integrates feedback from users in the software design

A software development practice where developers all work on the same computer to assure a common codebase

A software development practice where developers integrate and verify their work frequently, often multiple times a day, to detect integration errors as quickly as possible

Handle them during a risk mitigation phase before development

Scrum is for functional, frontend development only

Include them in the Product Backlog

Before the release, they should be tested and validated in a hardening sprint

Specific expectations can be used as acceptance criteria to specific product backlog items

Important, recurring non-functional requirements can be added to the definition of done

It is allowed to grow and change as more is learned about the product and its customers.

It provides just enough information to enable a Scrum Team to start the design phase of a product.

It is baselined to follow change management processes.

It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan.

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

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

Daily Scrum

Sprint

Sprint planning

All of these

Sprint review

Sprint retrospective

True

False

True

False

This way documentation is obligated and cannot be skipped

It creates a shared understanding of what done means

Management knows what the work of the developer needs to be checked for

It helps the developers know how much work to select during the sprint planning

Ready to be released to end users.

Whatever the Product Owner defines as quality.

No work is left to meet the Definition of Done.

Ready for integration.

All work the Developers are willing to do.

Unit tests per class

Cycle time per product backlog item

Number of check-ins per day

Depth of inheritance

Cyclomatic complexity

Class coupling

Release burn-up.

Burn-down chart.

Unit tests.

Critical path analysis.

Refactoring.

Build automation.

None of the above.

False

True

When the Product Owner says it is ready.

At the end of Sprint Planning.

When the Scrum Team agrees it is precise enough.

When the Product Backlog Refinement timebox expires.

It has always been documented in the past

The documentation is used to enhance and maintain the software

The scrum master demands it

The software tool being used requires it

It is required by the definition of done

The Scrum Team has all the skills to create an Increment by the end of every Sprint.

Every member of the Scrum Team is able to perform every task.

There are no conflicts within the Scrum Team.

A few of the Developers pair program and do Test-Driven Development.

The Architect chosen by the Scrum Team.

The software architect assigned to the Scrum Team.

The Developers with input from the Scrum Team and others.

The Chief Architect.

Scrum requires no documentation

Technical writers

Scrum master

Product owner

Developers

The behavior of a given object can be emulated to the system under test

They are machine-generated and eliminate the need to write code by hand

To increase tight coupling

TDD is impossible without them

Isolating a particular system component for controlled testing