Certified Scrum Master Flashcards

One time and at the end of the Sprint

The larger team size creates too much complexity and communication patterns for empiricism

<p>Encourage the team and organization to experiment with new ways of working</p> Signup and view all the answers

<p>Servant-leadership</p> Signup and view all the answers

<p>Estimate</p> Signup and view all the answers

<p>3-9</p> Signup and view all the answers

<p>Commitment</p> Signup and view all the answers

<p>One Sprint at a time; in Sprint Planning</p> Signup and view all the answers

<p>No more than 10% of our entire team capacity</p> Signup and view all the answers

<p>People and Processes</p> Signup and view all the answers

<p>After the Sprint Review and prior to the next Sprint Planning</p> Signup and view all the answers

<p>Courage</p> Signup and view all the answers

<p>Product Backlog</p> Signup and view all the answers

<p>Clearly expressing the Product Backlog</p> Signup and view all the answers

<p>Remove impediments for the team</p> Signup and view all the answers

<p>Creating the Sprint Backlog</p> Signup and view all the answers

<p>ScrumMaster</p> Signup and view all the answers

<p>Dev Team</p> Signup and view all the answers

<p>The item meets the Scrum Team's Definition of Done</p> Signup and view all the answers

<p>The Product Owner terminates the Sprint and the Dev Team re-plans</p> Signup and view all the answers

<p>Coach the team in self-organization and cross-functionality</p> Signup and view all the answers

<p>Product Owner</p> Signup and view all the answers

<p>An incremental process</p> Signup and view all the answers

<p>Focus</p> Signup and view all the answers

<p>Facilitating</p> Signup and view all the answers

<p>Working software over comprehensive documentation, Individuals and interactions over processes and tools, Customer collaboration over contract negotiation</p> Signup and view all the answers

<p>In the Product Backlog</p> Signup and view all the answers

<p>The team should agree on the length of the Sprint, taking the size and complexity of the project into consideration</p> Signup and view all the answers

<p>Supportive</p> Signup and view all the answers

<p>Weekly inspection</p> Signup and view all the answers

<p>Product Owner (A)</p> Signup and view all the answers

<p>Empower the team members, within appropriate limits</p> Signup and view all the answers

<p>Draw the problem to the attention of the ScrumMaster</p> Signup and view all the answers

<p>Assigning tasks to team members (D)</p> Signup and view all the answers

<p>A Sprint is a pre-specified amount of time in which the development team works at sustainable pace to complete a chosen set of work.</p> Signup and view all the answers

<p>The team</p> Signup and view all the answers

<p>A Sprint goal and a Sprint backlog (C)</p> Signup and view all the answers

<p>High trust teams do not have to be accountable to each other</p> Signup and view all the answers

<p>Agree the process and participants of the workshop with the workshop owner before the workshop</p> Signup and view all the answers

<p>The team should get acceptance of project deliverables from the appropriate stakeholders at least at the end of every Sprint</p> Signup and view all the answers

<p>User story cards containing only enough detail for planning and development, supplemented by face-to-face conversations</p> Signup and view all the answers

<p>Product Backlog</p> Signup and view all the answers

<p>A product of professional quality which fits the business need</p> Signup and view all the answers

<p>Scrum emphasizes taking a short step of development, inspecting both the resulting product and the efficacy of current practices, and then adapting the product goals and process practices</p> Signup and view all the answers

<p>The products will be of appropriate quality, as the guidance of the Product Owner is involved throughout the development process</p> Signup and view all the answers

<p>Do the necessary documentation to support the development and use of the product</p> Signup and view all the answers

<p>A visible chart of work to do, work in progress, and work done</p> Signup and view all the answers

<p>To be better able to respond to change</p> Signup and view all the answers

<p>Contact the Product Owner to clarify aspects of the work</p> Signup and view all the answers

<p>To share as a team what each member is working on and uncover obstacles standing in the way of completing the work</p> Signup and view all the answers

<p>Just enough design up front gives a good foundation to start from and helps to mitigate risk, without wasting unnecessary time</p> Signup and view all the answers

<p>It is best if the Scrum Master facilitates the project’s meetings (A)</p> Signup and view all the answers

<p>It meets the team's and Product Owner's negotiated definition of done</p> Signup and view all the answers

<p>To review the completed stories and look for opportunities to improve the product</p> Signup and view all the answers

<p>There is a predefined time limit for the event (A)</p> Signup and view all the answers

<p>Keeping metrics of earlier work load to help with future estimates required to get the whole project done</p> Signup and view all the answers

<p>Be fully involved in the estimating process</p> Signup and view all the answers

<p>Get something business-valuable delivered as quickly as possible, consistent with the right level of quality</p> Signup and view all the answers

<p>Usable</p> Signup and view all the answers

<p>Best architecture, requirements, and designs</p> Signup and view all the answers

<p>Meet and discuss outside of Daily Scrum</p> Signup and view all the answers

<p>Help to find effective Product Backlog management techniques</p> Signup and view all the answers

<p>Processes and tools</p> Signup and view all the answers

<p>One Sprint at a time in the Product Backlog Refinement meeting with participants of stakeholders</p> Signup and view all the answers

The usable product at the end of a Sprint that meets the Definition of Done.

A meeting held once at the end of each Sprint to assess the product increment.

Optimal number of team members ranges from 3 to 9 to maintain effective communication.

Role responsible for removing impediments and coaching the team.

A leadership style where the ScrumMaster prioritizes team needs.

A prioritized list of customer requirements for the team to work on.

Responsible for prioritizing and managing the Product Backlog.

Essential value for the team during a Sprint to ensure focus and responsibility.

Completing current tasks before starting new ones during a Sprint.

Admitting knowledge gaps as a sign of growth within the team.

A meeting where the team plans the upcoming Sprint and refines the Product Backlog.

Meeting held to inspect and adapt processes after the Sprint Review.

Items completed and accepted by stakeholders at the end of each Sprint to ensure quality.

A predefined limit on an event’s duration to promote efficiency.

Estimation of future workloads based on the team’s historical performance.

Philosophy of iterative improvement based on feedback after each Sprint.

Teams with trust that require less accountability, allowing autonomy.

Sets the values of prioritizing working software and individuals over tools.

A visual representation of work status including tasks in various stages.

Brief meetings focusing on progress and obstacles to promote problem-solving.

Criteria that a Product Backlog Item must meet to be considered complete.

The ongoing process of enhancing team practices based on experiences.

Visibility of all Scrum artifacts to stakeholders for accountability.

Encouraging team autonomy and decision-making.

Guiding and supporting the team in self-organization.

Time-boxed iterations where development occurs and product increments are delivered.

Continuous guidance from the Product Owner to maintain product standards.

Encouraging open dialogue among team members, especially about issues.

Essential for collaboration among team members and stakeholders.