PSM-I Pre-Assessment Quiz

¡Supera tus tareas y exámenes ahora con Quizwiz!

Which statement best describes the Sprint Review?

It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next

Is it allowed to skip the Daily Scrum if there is nothing interesting to tell about?

NO. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt

When do Development Team members become the exclusive owner of a Sprint Backlog item?

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

Should larger projects have more than one Product Owner?

No, the Product Owner is only one person

Is it normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release?

No. Development Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only "Done" functionality that could be released immediately

An organization has decided to adopt Scrum. Should they tailor the Scrum terminology?

No. Scrum is a framework rather than a methodology. It's very lightweight and only contains the essential required aspects. Therefore, it shouldn't be tailored like methodologies

Who is allowed to change the Sprint Backlog during the Sprint?

Only the Development Team can change its Sprint Backlog during a Sprint.

What belongs solely to the Development Team?

Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team

Imagine you are a Scrum Master. There are 10 professionals (developers and QAs) and the Product Owner. How to distribute people between development teams? Choose all applicable variants

Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog

What is the Product Owner's responsibility?

Optimizing the value of the work the Dev Team does

What part of the capacity of the Development Team does Product Backlog refinement usually consume?

Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team

What are the 3 Scrum Artifacts?

Product Backlog, Sprint Backlog and Increment

What are the 4 inputs to the Sprint Planning

Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.

Which role can abnormally terminate a Sprint?

Product Owner

Who has the authority to cancel a Sprint?

Product Owner

Who is responsible for managing the Product Backlog?

Product Owner

What is the result of the Sprint Review?

Revised Product Backlog that defines the probable Product Backlog items for the next Sprint.

The customer doesn't spend enough time collaborating with the team and it's making problems for the project. Who's responsible for fixing this problem?

Scrum Master

What are the two essential features a Scrum Team should possess?

Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

What is Scrum?

Scrum is a framework within which people can address complex adaptive problems, while delivering valuable products

What is Scrum is founded on?

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

Scrum does not describe agile processes and techniques

Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.

What are the formal Scrum events for inspection and adaptation?

Scrum prescribes four formal events for inspection and adaptation: • Sprint Planning • Daily Scrum • Sprint Review • Sprint Retrospective

How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.

What is the order of Scrum events?

Sprint Planning - Daily Scrum - Sprint Review - Sprint Retrospective

How much time does the Sprint Planning take?

Sprint Planning is time-boxed to a maximum of eight (8) hours for a one-month Sprint.

When should we review the way we have worked during the Sprint and plan for improvements?

Sprint Retrospective meeting

T/FThe Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

TRUE. By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment

T/F: During each Sprint Retrospective the Scrum Team reviews the Definition of Done and changes it if necessary

TRUE. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.

T/F: All Development Teams working on the same Product should use the same Product Backlog

TRUE. Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.

T/F: Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.

TRUE. The Development Team may also invite other people to attend in order to provide technical or domain advice.

What does Cone of Uncertainty show?

The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project. (How much is known about the Product over time)

T/F: The Daily Scrum time-box depends on the size of the Development team

The Daily Scrum is a 15-minute time-boxed event for the Development Team of any size.

Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?

The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress.

Who is responsible for all estimates in the Product Backlog?

The Development team

What is the Increment?

The Increment is the sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints.

What could be a source of requirements for any changes to be made to the product?

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.

What is the order of items in the Product Backlog?

The Product Owner is responsible for placing the most valuable and clear items at the top of the Product Backlog.

ho is responsible for the Product Backlog?

The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

Who is responsible for the monitoring of the remaining work towards the Project Goal?

The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

Who is allowed to participate in the Daily Scrum?

The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. Other people could attend the meeting, but cannot participate

Who is responsible for coping with incomplete artifact transparency?

The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.

The Scrum Team consists of:

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

What is the Sprint Backlog?

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

What provides guidance to the Development Team on why it is building the Increment?

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment

What is the Sprint Retrospective?

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The purpose of the Sprint Retrospective is to (select three):

The purpose of the Sprint Retrospective is to: • Inspect how the last Sprint went with regards to people, relationships, process, and tools; • Identify and order the major items that went well and potential improvements; and, • Create a plan for implementing improvements to the way the Scrum Team does its work.

Choose three responsibilities of a self-organizing Development Team.

This is the responsibility of the Development Team to estimate, select, and develop the items, as well as tracking Sprint performance, and creating, assigning, and completing tasks. This is the responsibility of the Product owner to create and order the Product Backlog items, communicate with the customer, and make sure that everyone has the right understanding about the Product Backlog items

What are the three pillars that uphold Scrum?

Three pillars uphold every implementation of empirical process control: 1. transparency 2. inspection 3. adaptation

What happens when a Sprint is cancelled?

When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. If part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog

Could the Product Owner and the Scrum Master be a part of the Development Team?

YES. Scrum does not prohibit the Product Owner or the Scrum Master do development work. However, it is not the best practice because it could create a conflict of interest.

Can Developers remove items from the Sprint Backlog during the Sprint Planning meeting?

Yes, because the Sprint Backlog is not yet finalized until after the Sprint Planning meeting

Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less?

Yes, if the remaining work is also estimated, maybe in bigger units. The Scrum Guide requires only the work planned for the first days of the Sprint is decomposed by the end of the Sprint Planning, often to units of one day or less. However, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

List all opportunities to inspect and adapt.

(Retro, Daily Scrum, Review, Planning)

Which is NOT a Development Team responsibility?

1-Demonstrating the increment to the customer, 2-Monitoring the Sprint performance, & 3-Managing the Daily Scrums. 'Explaining the meaning of Sprint Backlog items to the customer' is the responsibility of the Product Owner to ensure every Product Backlog item (and Sprint Backlog item) is clearly understood by the team members and the customer.

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?

1. By facilitating Development Team decisions 2. By removing impediments that hinder the Development Team

How does the Scrum Master serve the Organization?

1. Leading and coaching the organization in its Scrum adoption 2. Planning Scrum implementations within the organization 3. Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

What are the two meetings in which people outside the Scrum Team are allowed to participate?

1. The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. 2. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting

What are the questions the Sprint Planning answers?

1. What can be delivered in the Increment resulting from the upcoming Sprint? 2. How will the work needed to deliver the Increment be achieved?

The timebox for a Sprint Review is...

2 hours for a two week Sprint (1 hour per week)

What are 3 Product Backlog features?

A Product Backlog is never complete. 1. The earliest development of it only lays out the initially known and best-understood requirements. 2. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. 3. As long as a product exists, its Product Backlog also exists

Who is responsible for crafting the Sprint Goal at the Sprint Planning?

After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.

If an inspector determines that one or more aspects of a process deviate outside acceptable limits when an adjustment must be made?

An adjustment must be made as soon as possible to minimize further deviation.

What does Burn-down Chart show?

Burn-down chart shows the evolution of remaining effort against time

If we're going to use burn-down charts for the Sprint performance, who should update it?

Development Team

Who creates the increment?

Development Team

Who is responsible for creation of the Definition of "Done"?

Development Team

Who participates in the Sprint Review?

During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint.

T/F: Scrum recommends using only those Scrum components and rules which suit most for a particular project

FALSE. Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.

T/F: Scrum does not allow additional meetings that are not defined in Scrum.

FALSE. Scrum allows additional meetings if they facilitate achieving the Sprint Goal.

T/F: All the Scrum Teams working on the same product should have the same Sprint length

FALSE. Scrum does not require having aligned Sprints for multiple teams.

T/F: The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team

FALSE. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, the Development Team adds it to the Sprint Backlog

T/F: The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team

FALSE. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team

T/F: If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled.

FALSE. The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and Development Team.

T/F: Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master

FALSE. The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

T/F: Each task in the Sprint Backlog should be owned by a Development Team member.

False

T/F: It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.

False, It is prohibited. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done."

T/F: Definition of "Done" is created during the first Sprint and remains unchanged until the Product release

False. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.

T/F: Cross-functional teams are optimized in a technical layer of a system.

False. The Development Team as a whole is cross-functional, which means the sum of all developers with their different expertise. It doesn't mean that we need to have cross-functional individuals. Each individual is experts in one or more technical layer or aspect of the project, and the team they create is cross-functional (have all the expertise required to get the job done, without any need for external resources).

T/F: The Scrum Master shouldn't allow the Development Team start developing without having the tasks identified and assigned

False. There are two problems in this statement: 1. The Scrum Master doesn't manage people and cannot forbid team members from doing something and cannot order them to do certain things. S/he should always "convince" them to do the right thing by training and coaching. 2. The Development Team identify the tasks and assign them gradually, throughout the Sprint. We don't do it upfront, in the beginning of the Sprint.

Which of the following is the best way the Scrum Master can help improve the communications between the Development Team and the Product Owner

Help them understand the importance of communications and the common tools and techniques

What should be taken into account for the Definition of "Done"?

If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."

What comprises Scrum

roles, artifacts, events & rules

The Scrum Master does the following regarding the Daily Scrum (select all applicable variants):

• Coaching the Development Team in self-organization and cross-functionality; • Helping the Development Team to create high-value products; • Removing impediments to the Development Team's progress;

How does Definition of "Done" help the Scrum Team?

• DoD is used to assess when work is complete on the product Increment • Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning • DoD ensures artifact transparency

How does the Scrum Master help the Product Owner?

• Finding techniques for effective Product Backlog management; • Understanding product planning in an empirical environment; • Facilitating Scrum events as requested or needed.

What happens during the Sprint?

• No changes are made that would endanger the Sprint Goal; • Quality goals do not decrease; and, • Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

What does Product Backlog management include?

• Ordering the items in the Product Backlog to best achieve goals and missions; • Optimizing the value of the work the Development Team performs; • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

What are the three most applicable characteristics of the Product Owner?

• Product Value Maximizer • Lead Facilitator of Key Stakeholder Involvement • Product Marketplace Expert

What are the 3 characteristics of a Development Team?

• Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule; • Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and, • Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole

What is the time-box for each Scrum event?

• Sprint Planning is time-boxed to a maximum of 8 hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. • The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. • Sprint Review is a 4 hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. • Sprint Retrospective is a 3 hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

What are the three main questions each member of the Development Team should answer at the Daily Scrum?

• What did I do yesterday that helped the Development Team meet the Sprint Goal? • What will I do today to help the Development Team meet the Sprint Goal? • Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?


Conjuntos de estudio relacionados

B1. CHN - Care of the Normal and At-Risk Families, Population Groups, and Communities (Pt 1)

View Set

Maryland state exam practice exam

View Set

Med Surg 1 Chapter 63 Care of Patients with Problems of the Thyroid and Parathyroid Glands

View Set

Chapter 12 - Managing Production

View Set