Cartes mémoires PSPO I (Seite 6 von 9)

Cartes-fiches	325
Utilisateurs	11
Langue	Deutsch
Catégorie	Technique
Niveau	Autres
Crée / Actualisé	12.04.2022 / 25.12.2024
Lien de web	https://card2brain.ch/box/20220412_pspo_i
Intégrer	<iframe src="https://card2brain.ch/box/20220412_pspo_i/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

What is the primary role of management in Scrum?

To continually monitor staffing levels of the Developers during the Sprint

To identify and remove people that aren't working hard enough

To support the Scrum Teams with insights and resources that help them improve

To monitor the Developers’ productivity

Sprint burndown charts are an efficient tracking tool because they show:

How much effort has gone into a Sprint

How many Product Backlog Items remain

An estimate of the total work remaining for the Sprint

How many hours have been worked by each Developer

Self-managing Developers choose:

The Product Backlog ordering

How to best accomplish their work

When to release

Attendees for the Sprint Review

Which one of the following is NOT a responsibility of a self-managing Developers?

Doing the work planned in accordance with the Definition of Done

Pulling Product Backlog items for the Sprint

Ordering the Product Backlog.

Determining the time for the Daily Scrum.

Why do Developers need a Sprint Goal?

A Sprint Goal only gives purpose to Sprint 0.

A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.

The Developers are more focused with a specific goal.

Sprint Goals are optional. Everything is known from the Product Backlog.

When a Developer is having trouble delivering a working Increment because they don't understand a functional requirement, what should they do?

Defer the work to a more appropriate Sprint.

Add a specialist to the Developers.

Partially complete the functionality and discuss the remaining work at the Sprint Review.

Collaborate with the Product Owner to determine what is possible and acceptable.

Which Scrum Values are exhibited by not building Product Backlog items that have low business value? Choose 3

Respect

Courage

Focus

Earned Value

Persistence

Who determines how work is performed during the Sprint?

Development managers

Subject matter experts

The Scrum Master

The Developers

Architects

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

No, that is far too hard and must be done in a hardening Sprint.

No, each Scrum Team stands alone.

Yes, but only for Scrum Teams whose work has dependencies.

Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.

Multiple Scrum Teams working on the same project must have the same Sprint start date:

True

False

You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of five new Scrum Teams.

There should be five Product Owners, reporting to a chief Product Owner.

Each Scrum Team should have a separate Product Backlog.

There should be five Product Owners, one for each Scrum Team.

The product has one Product Backlog

There should be only one Product Owner.

Which of the following are true about the length of the Sprint? Choose 2

It is best to have Sprints of consistent length throughout a development effort.

The length of the Sprint should be proportional to the work that is done in between Sprints.

All Sprints must be 1 month or less.

Sprint length is determined during Sprint Planning and should be long enough to make sure the Developers can deliver what is to be accomplished in the upcoming Sprint.

Every Scrum Team must have a Product Owner and Scrum Master.

False. A Scrum Master is only required when asked for by the Developers.

True. Each must be 100% dedicated to the Scrum Team.

True. Outcomes are affected by their participation and availability.

False A Product Owner can be replaced by a business analyst in the Developers..

Which two things are appropriate for a Scrum Master to do if the Developers don’t have the engineering tools and infrastructure to completely finish each selected Product Backlog item?

Have the Developers establish a Definition of Done that is actually possible to achieve given current circumstances.

Declare the Developers not ready for Scrum.

Encourage the Product Owner to accept partially done Increments until the situation improves.

Coach the Developers to improve its skills, tools and infrastructure over time and adjust the Definition of Done accordingly.

Refocus the current Sprint on establishing the Developers’ infrastructure instead of delivering an Increment.

The purpose of a Sprint is to produce a done Increment of product:

True

False

How much time is required after a Sprint to prepare for the next Sprint?

Enough time for the requirements for the next Sprint to be determined and documented.

Enough time for the Developers to finish the testing from the last Sprint.

None. A new Sprint starts immediately following the end of the previous Sprint.

What are three benefits of self-organization?

Increased rule compliance

Increased accuracy of estimates

Increased self-accountability

Increased commitment

Increased creativity

For which is the Scrum Master responsible?

The Scrum process being adopted and used properly.

Keeping track of resource allocation.

The meetings and the objectives that a Scrum Team sets for itself.

Managing the effectiveness of the Scrum Team.

Which Scrum Value is affected by a lack of trust in the Scrum Team?

Commitment

Openness

Respect

Courage

Focus

The Developers should have all the skills needed to:

Do all of the development work, except for specialized testing that requires additional tools and environments.

Complete the project within the date and cost as calculated by the Product Owner.

Turn Product Backlog items into an Increment of potentially releasable product functionality.

Which are properties of the Daily Scrum? CHOOSE 2

It is facilitated by the team lead.

It is fifteen minutes or less in duration.

It consists of the Scrum Master asking the Team members the three questions.

It is free form and designed to promote conversation.

Its location and time should remain constant.

When a Developer is having trouble delivering a working Increment because they don't understand a functional requirement, what should they do?

Defer the work to a more appropriate Sprint.

Collaborate with the Product Owner to determine what is possible and acceptable.

Partially complete the functionality and discuss the remaining work at the Sprint Review.

Add a specialist to the Developers.

If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?

When the work remaining will likely be completed if nothing changes on the Product Backlog or the Developers.

When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.

When it is anticipated that all work will be completed, and the team can be released.

The evolution of the cost spent on the project.

Which outcome is expected as Scrum Teams mature?

A Scrum Master is no longer needed since they are a mature team now.

They will improve their Definition of Done to include more stringent criteria.

There is no need for a timeboxed Sprint, since timeboxes are only for new Scrum Teams.

Sprint Reviews will no longer be needed.

How much of the Sprint Backlog must be defined during the Sprint Planning meeting?

The entire Sprint Backlog.

Enough for the Team to forecast and start working for the first few days of the Sprint.

Enough to give confidence to the Scrum Master that they have a good plan.

Enough to understand the design impact to the overall architecture

Who must attend the Daily Scrum?

The Scrum Team

The Developers

The Developers and Scrum Master

The Scrum Master and Product Owner

Who can abnormally terminate a Sprint?

The Scrum Master

The Product Owner

Any Executive

The Project Sponsor

What factor is NOT a consideration when establishing the Sprint length?

The stability of the Team members

The level of uncertainty with new technology

All Sprints in organization should have the same duration

The length of planned releases

Which does self-managing Developers choose?

Sprint length.

When to release.

How to accomplish their work.

Product Backlog prioritization.

What are two good ways for the Developers to make non-functional requirements visible?

Add them to the definition Done.

Add to the Product Backlog.

Keep them on a separate Non-functional list of requirements.

Add them as part of a hardening Sprint.

What is the accountability of the Product Owner during Sprint 0?

There is no Sprint 0.

Creating the Agile Charter.

Approving the scope, schedule and cost of the project.

Creating that initial Product Backlog.

During a Sprint Retrospective, for what is the Product Owner responsible?

The Product Owner takes part as a team member as he or she is part of the Scrum Team.

The Product Owner does not attend.

Take notes on ideas for new Product Backlog items.

Facilitate the retrospective since they are neutral to any Team issues.

Which two topics are NOT appropriate or discussion in a Sprint Retrospective?

The completeness of the Definition of Done.

Team interactions.

The next Sprint Goal.

The use of burndown charts and other Scrum artifacts.

The ordering of the items on the Product Backlog.

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

The Product Owner decides.

The Developers pull in work in agreement with the Product Owner.

The Scrum Team with the highest velocity pulls Product Backlog items first.

Each Scrum Team takes an equal number of items.

The Product Owner should provide each team with its own Product Backlog.

Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces):

True

False

What happens if the Developers cannot complete its work by the end of the Sprint?

The end date of the Sprint is extended.

The Sprint ends on time and the team learns what is possible to accomplish in that Sprint Length.

The Sprint ends on time and all the work is moved into the next Sprint.

Four new Scrum Teams have been created to build one product. How should the teams coordinate their work?

Leave it up to the Scrum Master to come up with a solution.

The Scrum Master should attend all 4 Daily Scrums to coordinate the work.

The Product Owner should work with a lead developer to assign work to each team.

The Developers need to work together to come up with an approach to create an integrated Increment.

A Scrum Master is working with Developers that are in different physical locations. The Developers meet in a variety of meeting rooms and the Scrum Master has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take?

Take over setting up the conference calls.

Allow the Team to self-manage to manage the issue.

Ask management to assign someone to handle it.

Ask different team members to take turns on how to do it.

Which two activities will a Product Owner engage in during a Sprint?

Engage Stakeholders.

Answer questions about the existing Sprint.

Update the Sprint Backlog daily.

Update the Sprint Burndown Chart.

When the Developers determines that it has over-committed itself for a Sprint, who has to be present when reviewing and adjusting the Sprint work selected?

The Scrum Master

The Scrum Team

The Product Owner and stakeholders

Only the Developers

PSPO I

Créer ou copier des fichiers d'apprentissage

Créer ou copier des fichiers d'apprentissage

Connecte-toi pour voir toutes les cartes.

SWITCHaai

Office 365

Edulog

Apple ID

Google