1. Scrum Master I: Information Radiator, Rules, and Scaling (EN)

Scrum Master I: Sample Exam von Dion Training

video locked

Über den Vortrag

Der Vortrag „Scrum Master I: Sample Exam“ von Dion Training ist Bestandteil des Kurses „Scrum Master I: Information Radiator, Rules, and Scaling (EN)“.

Quiz zum Vortrag

  1. Sprint review
  2. Release planning
  3. Backlog refinement
  4. Sprint execution
  1. The Developers identify two well-known stories against which other stories can be compared.
  2. The Scrum Master assigns a set of known stories for the Developers to compare against.
  3. The Product Owner identifies similar stories from a previous sprint to be used as baselines.
  4. The most experienced Scrum Developer will select certain previous stories as baselines.
  1. Product Owner
  2. Product manager
  3. The Developers
  4. Scrum Master
  1. 1,3
  2. 2,4
  3. 1,2
  4. 3,4
  1. Product backlog items completed in a sprint and accepted by customers
  2. Items that are identified as most important to customer satisfaction
  3. Sprint backlog items that are proven to fully meet the definition of done
  4. Items that meet all quality criteria and have successfully passed testing
  1. 1,4
  2. 1,2
  3. 2,3
  4. 3,4
  1. Problems encountered during the sprint execution
  2. Customer dissatisfaction with the increment
  3. Velocity deviations over the last four sprints
  4. Adaptations requested by customers in the sprint review
  1. An actionable plan
  2. An amended goal
  3. A task list
  4. A burn-down chart
  1. Burn-down and burn-up charts
  2. A sprint goal as a commitment
  3. Selected product backlog items
  4. Actionable plan for the increment
  1. Scrum theory
  2. Scrum artifacts
  3. Scrum knowledge
  4. Scrum events
  1. By facilitating stakeholder collaboration as needed
  2. By helping the employees understand and enact Scrum
  3. By ensuring all Scrum events take place and are productive
  4. By maintaining a focus on creating high-value increments
  1. Represents the commitment for all increments resulting from sprints
  2. Ensures all the user stories can be completed correctly during a sprint
  3. Identifies the criteria for a user story to be chosen in sprint planning
  4. Describes the efforts required to complete a user story during the sprint
  1. All increments created during a sprint must work together for the sum of all of them to be presented during a sprint review.
  2. Each increment produced during a sprint must meet the team's definition of done and be independently verified to work.
  3. All work carried out by the Developers during the sprint will be included in the increment presented to customers.
  4. Every increment created by the Scrum team during the sprint execution is deemed usable and ready for release.
  1. It is a plan for the Developers that is updated throughout the sprint.
  2. It represents the Product Owner's desires for what needs to be done.
  3. It is modified throughout the sprint and contains epics and features.
  4. It is used during the sprint to visually represent the completed work.
  1. Holding each other accountable as professionals
  2. Clearly documenting product backlog epics and stories
  3. Ensuring the highest levels of effectiveness and quality
  4. Maximizing the product value for the customers
  1. A visual representation of task planning and flow management
  2. A visual means of controlling the number of product backlog items selected
  3. A visual way to display the time allocation for each sprint backlog item
  4. A visual display for the Product Owner to assign sprint tasks and user stories
  1. Individuals who are not trusted by others
  2. Individuals who are respected by peers
  3. Individuals who exhibit good teamwork
  4. Individuals who are proven leaders
  1. A framework for generating value through adaptive solutions to complex problems
  2. The adaptive process used to manage all the complex products and solutions
  3. A predictive technique used to manage complex products and solutions
  4. The definitive method used to predictively manage complex products
  1. 1,4
  2. 2,3
  3. 1,3
  4. 2,4
  1. Describes a future state and serves as a target against which a Scrum team can plan
  2. Defines a vision for the Developers in terms of finding adaptive solutions
  3. Serves to drive all stakeholders toward making effective decisions during a sprint review
  4. Identifies the correct epics and features to be added to the backlog by the Product Owner
  1. Planning for the upcoming sprint
  2. Executing the daily work
  3. Prioritizing the product backlog
  4. Forecasting the completion date
  1. The refined product backlog
  2. The sprint goal
  3. The definition of done
  4. The sprint backlog
  1. A group of related user stories used for complex products
  2. A refined and ready-for-development requirement
  3. An entire workflow that is large and broadly defined
  4. A discrete part of the overall product’s functionality
  1. One or more increments
  2. New product backlog items
  3. Resolutions to problems
  4. Refined product backlog
  1. An ongoing process of adding sizes, more detail, and an order to backlog items
  2. A time-boxed event during which sizes are added to backlog items chosen for the sprint
  3. An iterative adjustment of the product backlog by the Product Owner and customers
  4. A repetitive activity during which customers add more detail to the epics and user stories
  1. Sprint review
  2. Sprint retrospective
  3. Sprint execution
  4. Sprint planning
  1. Non-functional, functional, and performance
  2. Effectiveness, quality, and performance
  3. Functional, non-functional, and quality
  4. Performance, functional, and quality
  1. The refined product backlog
  2. The updated sprint backlog
  3. The new sprint goal
  4. The new product goal
  1. Story point sizing
  2. Ideal time sizing
  3. Absolute sizing
  4. Fibonacci sizing
  1. Embracing the Scrum values
  2. Making artifacts transparent
  3. Inspection of the artifacts
  4. Adaptation as required
  1. The Product Owner agrees to the changes since it is clear they will not alter the sprint goal.
  2. The Product Owner denies the changes since the Developers have already begun working.
  3. The Product Owner allows the changes even though some do not align with the sprint goal.
  4. The Product Owner rejects all changes because of time constraints in the sprint duration.
  1. 1,4
  2. 1,2
  3. 2,3
  4. 3,4
  1. Customer collaboration over contract negotiation
  2. Team members' collaboration over timelines
  3. Transparency and inspection over documentation
  4. Working software over inspection and adaptation
  1. Scrum team
  2. The Developers
  3. Scrum Master
  4. Product Owner
  1. 1,2
  2. 1,3
  3. 3,4
  4. 2,4
  1. Used to compare one Scrum team to another
  2. Total story points completed per sprint
  3. Not a goal, but is used for forecasting
  4. Should be steady or increasing over time
  1. 2,4
  2. 1,2
  3. 2,3
  4. 1,3
  1. Start with epics and refine until ready for selection.
  2. Write the most complex stories first, then prioritize.
  3. Start with the smallest stories first, then group into features.
  4. Create independently and then sort them to compare.
  1. Openness
  2. Focus
  3. Transparency
  4. Commitment
  1. Product backlog
  2. Epic backlog
  3. Sprint backlog
  4. Story backlog

Diese Kurse könnten Sie interessieren

PeopleCert Scrum Master I (EN)
PeopleCert Scrum Master I (EN)
Dion Training
(1)
54,45 € mtl. 39,99 € mtl.
Sie sparen 27 %
Scrum Master I: Information Radiator, Rules, and Scaling (EN)
Scrum Master I: Information Radiator, Rules, and Scaling (EN)
Dion Training
(1)
9,90 € mtl. 8,99 € mtl.
Sie sparen 9 %

Dozent des Vortrages Scrum Master I: Sample Exam

Dion Training

Dion Training

Jason Dion (DionTraining.com) is a professor and instructor with multiple information technology professional certifications, including Certified Information Systems Security Professional (CISSP), Certified Ethical Hacker (CEH), Certified Network Defense Architect (CNDA), Digital Forensic Examiner (DFE), Digital Media Collector (DMC), CySA+, Security+, Network+, A+, PRINCE2 Practitioner, and ITIL. With decades of project management and networking experience, Jason Dion has been a network engineer, Deputy Director of a Network Operations Center, and an Information Systems Officer for large organizations around the globe.

Kundenrezensionen

(1)
5,0 von 5 Sternen
5 Sterne
5
4 Sterne
0
3 Sterne
0
2 Sterne
0
1  Stern
0

© 2024 Lecturio GmbH. Alle Rechte vorbehalten.

Betreuung durch Dozenten
Auch unterwegs auf Tablet und Smartphone lernen
100% Geld-zurück-Garantie