Cartes mémoires PSPO I (Seite 5 von 7)

Cartes-fiches	265
Utilisateurs	74
Langue	English
Catégorie	Informatique
Niveau	Autres
Crée / Actualisé	28.12.2020 / 12.03.2025
Lien de web	https://card2brain.ch/box/20201228_pspo_i
Intégrer	<iframe src="https://card2brain.ch/box/20201228_pspo_i/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

What is the time-box for the Sprint Review?

4 hours and longer as needed

1 day

4 hours for a monthly Sprint

As long as needed

What is typical work for a Product Owner in a Sprint?

Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items

Update the work plan for the Development Team on a daily basis

Work with the Development Team on Product Backlog refinement

Create financial reporting upon the spent hours reported by the Development Team

Collaborate with stakeholders, user communities and product managers

What might indicate to a Product Owner that she needs to work more with the Scrum Team?

She isn't working full time with the Scrum Team

The increment presented at the Sprint Review does not reflect what she thought she had asked for

Developers leave the Team

The acceptance tests do not appear to be complete

What things might a Scrum Product Owner focus on to ensure his product delivers value?

How readily his products can be absorbed and used by his customers

The size of his product in "lines of code"

How much of the functionality of the product is being utilized

Direct customer feedback

Minimizing changes to project scope

What three factors are best considered when establishing the Sprint length?

The ability to go to market with a product release.

Sprints must have the same length throughout an organization.

The frequency at which team formation can be changed.

The level of uncertainty over the technology to be used.

The risk of being disconnected from the stakeholders.

What two phrases best describe the relationship of the Product Owner and the Development Team?

They should work apart as much as possible in order to keep the concerns of business and technology separated.

They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items.

The Product Owner should be with the Development Team full-time to grow a deep understanding of the technology being used.

They collaborate often so the Development Team builds Increments keeping end-user and stakeholder concerns in mind.

They should share no more than the Sprint Planning and the Sprint Review meeting.

What two things best help the Product Owner manage the value of a product?

Setting value on individual Product Backlog items using Value Poker.

Devising a formula for a neutral calculation of value.

The order of the Product Backlog.

Validating assumptions of value through frequent releases.

What two things should be done if the Product Owner is unavailable?

Within the Sprint, the Development Team makes the best decisions possible to assure progress toward the Sprint Goal, re-aligning with the Product Owner once he/she is available again.

There should be a Product Owner team to allow a different person from that team to instantly take over the role of Product Owner.

In a permanent state of unavailability, a new Product Owner needs to be appointed. Development efforts without a Product Owner are not employing Scrum.

Development of functional requirements stops until the Product Owner is available again.

What typically happens if Product Backlog is not sufficiently clear at Sprint Planning?

The Development Team has difficulties creating a forecast of work for the Sprint.

Nothing in particular.

It is compensated if the Product Owner gives the team a clear Sprint Goal instead.

The meeting is cancelled so refinement can be done first.

The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.

What variables should a Product Owner consider when ordering the Product Backlog?

Effort first, then value.

Development cohesion as indicated by the Development Team.

Lowest development cost in order to maximize ROI.

The availability of resources and skills for implementation.

Whatever is most appropriate for the Product Owner to achieve the product's goals and to optimize the value received.

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

The Product Owner and the Development Team

The Scrum Master, project manager and Development Team

The Development Team

The Product Owner and all stakeholders

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

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

Defer the work to a more appropriate Sprint.

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

Add a specialist to the Development Team.

When can a Development Team cancel a Sprint?

It can't. Only Product Owners can cancel Sprints.

When functional expectations are not well understood.

When the Product Owner is absent too often.

When the selected Product Backlog items for the Sprint become unachievable.

When a technical dependency cannot be resolved.

When can the Product Backlog be updated?

Only after a Sprint Review if agreed to by the stakeholders.

Only during Product Backlog refinement sessions if the Product Owner is present.

Never, unless agreed to by the change request.

At any time when done by the Product Owner or at the Product Owner's discretion.

When does a Development Team make adjustments to its engineering practices?

After they have been discussed and agreed to at the Sprint Retrospective.

During Sprint Planning.

Prior to start a new project.

Before a Sprint begins.

Whenever needed.

When does a Development Team member become the sole owner of a Sprint Backlog item?

During the Daily Scrum.

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be implemented by an individual development team member..

Whenever a team member can accommodate more work.

At the Sprint planning meeting.

When does the next Sprint begin?

Next Monday.

Immediately following the next Sprint Planning.

When the Product Owner is ready.

Immediately after the conclusion of the previous Sprint.

When does the second Sprint start?

After the customer completes acceptance testing of the first Sprint

Immediately after the first Sprint

After the Product Backlog for the second Sprint has been selected

Once the architectural changes for the second Sprint have been approved by the senior architect

When is a Sprint over?

When the Product Owner says it is done.

When the time-box expires.

When all the tasks are completed.

When all Product Backlog items meet their definition of done.

When is implementation of a Product Backlog item considered complete?

At the end of the Sprint

When all work in the Sprint Backlog related to the item is finished

When the item has no work remaining in order to be released

When QA reports that the item passes all acceptance criteria

When is it most appropriate for a Development Team to change the definition of "Done"?

During the Sprint Retrospective

Prior to starting a new project

Prior to starting a new Sprint

During Sprint Planning

When is the Sprint Backlog created?

During the Sprint

At the beginning of the project

Prior to the Sprint Planning meeting

During the Sprint Planning meeting

When many Development Teams are working on a single product, what best describes the definition of "Done"?

Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

It depends.

Each Development Team uses its own but must make their definition clear to all other teams so the differences are known.

All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

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

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.

No, each Scrum Team stands alone.

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

When might a Sprint be abnormally cancelled?

When it becomes clear that not everything will be finished by the end of the Sprint.

When the Sprint Goal becomes obsolete.

When the Development Team feels that the work is too hard.

When the sales department has an important new opportunity.

When multiple Scrum Teams are working on the same project, they should make sure that each team has different Sprint start dates.

True

False

When multiple teams work together on the same product, each team should maintain a separate Product Backlog.

True

False

When should a Sprint Goal be created?

At any time during the Sprint.

It must be established before Sprint Planning in order to begin planning.

It should have been created in the previous Sprint during Product Backlog refinement.

During Sprint Planning.

A Sprint Goal is not mandatory in Scrum.

When should the Product Backlog be refined?

The Product Owner and the Development Team do it in the 1-2 preceding Sprints.

The Product Owner takes the time between the Sprints to do it.

The Product Owner must do this as essential work in Sprint 0.

The Product Owner and the Development Team do it in the actual Sprint if they haven't been able to do it in preceding Sprints.

Business analysts in the organization should do this work for the Scrum Team 1-2 Sprints ahead of the Development Sprints.

When should the Product Owner update the project plan?

The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.

Before the Sprint Planning to know how much work will have to be done in the Sprint.

After the Daily Scrum to ensure an accurate daily overview of the project progress.

Scrum forbids having a project plan.

The Product Owner shouldn't be occupied by that. It is work for the Project Manager.

Which answer best describes the topics covered in Sprint Planning?

Who is on the team and what team member roles will be.

What went wrong in the last Sprint and what to do differently this Sprint.

What can be done and how to do it.

How conditions have changed and how the Product Backlog should evolve.

What to do and who will do it.

Which are functions of a self-organizing Development Team in Scrum?

Pull work from the Product Backlog into the Sprint.

Track their velocity in an ALM tool.

Undertake the work in the Sprint Backlog.

Report on daily Sprint progress to the stakeholders.

Set the best time for the Daily Scrum.

Which are properties of the Daily Scrum?

It is free form and designed to promote conversation.

It is held first thing in the morning.

It is fifteen minutes or less in duration.

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

Its location and time should remain constant.

Which description best fits the role of the Product Owner?

Project Manager 2.0.

Value Maximizer.

Requirements Collector.

Scope Protector.

Chief Analyst.

Which does a self-organizing Development Team choose?

When to release, based on its progress.

Product Backlog ordering.

Sprint length.

Stakeholders for the Sprint Review.

How to best accomplish its work.

Which is NOT a valid consideration when ordering a product backlog?

Development team tools and techniques

Dependencies on other product backlog items

Risks

Importance to customers

Alignment with strategy and goals

Which is the most important stakeholder Product Owners must satisfy?

The company owners and the shareholders.

Executive staff.

The chief Product Owner.

The Product Users.

Which metrics will help a product owner establish that value is being delivered?

Time to market

Productivity

Customer satisfaction

Scope implemented

Velocity

Which of the below are roles on a Scrum Team?

Customers

Development Team

Users

Scrum Master

Product Owner

Which of the following are feedback loops in Scrum?

Daily Scrum.

Sprint Review.

Release Planning.

Sprint Retrospective.

Refinement Meeting.

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