Scrum Exam Prep: Content Review (Sprint 2) von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider

video locked

Über den Vortrag

Der Vortrag „Scrum Exam Prep: Content Review (Sprint 2)“ von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider ist Bestandteil des Kurses „Scrum: Exam Preparation“.


Quiz zum Vortrag

  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. Incorrect
  2. Correct
  1. ...decides on the use of technologies used in the development process.
  2. ...is accountable for sorting the backlog items.
  3. ...is responsible for removing obstacles that hinder the work of the development team.
  4. ...takes care of involving the right stakeholders.
  5. ...actively manages the day-to-day tasks of the development team.
  1. ...to describe the goal of the sprint.
  2. ...to help the development team decide how many items they can select for the sprint.
  3. ...to define the acceptance criteria more precisely.
  4. ...to increase transparency.
  5. ...to generate a common understanding of what needs to be done for each Product Backlog Item.
  1. When all tasks for the item are completed.
  2. When everything listed in the Definition of Done has been done.
  3. When the Sprint Review is finished.
  4. When the sprint is over.
  1. not at all
  2. When the Sprint Goal becomes obsolete
  3. When the sprint no longer makes sense
  4. If there is a technical dependency that has not been resolved
  5. If there are not enough tasks available for the sprint
  1. It does not need to be created
  2. During Sprint Planning
  3. During the sprint
  4. At the beginning of the project
  5. At the beginning of Sprint Planning
  1. When the development team realizes that too much technical debt has been built up.
  2. When the Product Owner realizes that it no longer makes sense because the Sprint Goal is no longer achievable.
  3. When the Scrum Master decides that it no longer makes sense to achieve the Sprint Goal.
  4. If the licenses for the software are not fully available.
  1. At the end of each sprint
  2. Whenever it is needed
  3. If the Product Owner requests it
  4. If the Scrum Master has found situations that need improvement
  5. Between two sprints
  1. Requirements for the next sprint
  2. A finished product increment
  3. An interface layout
  4. An architectural description
  1. The sprint is aborted.
  2. The sprint is being expanded.
  3. The product backlog items will be processed in the next sprint.
  4. The product backlog items of the sprint are added back to the product backlog.
  1. The definition of done remains constant throughout the project.
  2. The definition of done is becoming a concrete product feature.
  3. The Definition of Done assigns responsibility to individual team members.
  4. The definition of done is expanded to include acceptance criteria.
  5. The definition of done is improved and made more specific.
  1. Ask the development team to periodize the product backlog items.
  2. Help the Product Owner sort the entries (coaching & management of the Scrum process)
  3. Ask the customer if he can help
  4. Extend the length of the sprint to free up more time for the product owner
  1. The infrastructure is provided.
  2. Preparing for the product backlog.
  3. Preparing for Sprint Planning.
  4. There is no Sprint 0.
  1. A demonstration of the product increment
  2. Communication of project progress
  3. Reflection on successes during the sprint
  4. Reflection on failures during the sprint
  5. Considerations for improving the following sprint
  1. The product increment is created.
  2. Nothing, because there is no time between the retrospective and the planning.
  3. Refactoring if necessary.
  4. Preparations for Sprint Planning are made.
  1. The product backlog is sorted according to the customer s wishes.
  2. The product backlog is sorted by priority.
  3. The Product Owner selects the entries that he believes provide the most value to the customer.
  4. According to the WSJF.
  1. It changes over time as more is learned about the project.
  2. It includes all necessary work for the product.
  3. It is a baseline for the requirements in the project.
  4. It represents a detailed project plan that remains unchanged throughout the project.
  5. It is created and maintained by the customer or client.
  1. It is the development team's plan for the sprint.
  2. It is loaded with entries from the Product Backlog by the Product Owner.
  3. It is compiled by the Product Owner.
  4. Each of these entries is valued in story points.
  5. Each of these entries is estimated in hours.
  1. Backlog Refinement
  2. Daily Scrum
  3. Sprint Planning
  4. Sprint Retrospective
  5. Sprint Review
  1. The entries that have the greatest development scope
  2. The entries that have the highest business value
  3. The entries that have the highest value
  4. The entries that the Product Owner provides for this
  5. The entries that have the highest urgency
  1. He answers questions from the development team about the product backlog items.
  2. He conducts the Daily Scrums.
  3. He communicates and works with stakeholders.
  4. He prioritizes the development team s tasks.
  1. They do not exist as a role in the Scrum framework.
  2. You review code as part of the development team.
  3. You are responsible for the final quality assurance.
  4. They test hypotheses about the progress of the project.
  5. They verify the results produced by the development team.
  1. There can be multiple DoDs as long as they ultimately result in a potentially deliverable product increment.
  2. There can be multiple DoDs if these are agreed upon with the customer.
  3. There should be a common DoD for all teams so that a potentially deliverable product increment is created at the end.
  4. Each team determines its DoD independently of all others.
  1. The development team
  2. The management
  3. The CEO
  4. Der Product Owner
  5. The Scrum Master
  1. The development team
  2. The Integrator
  3. Der Product Owner
  4. The Scrum Master
  5. The testing department
  1. The development team
  2. The Scrum Team
  3. The product owner and the development team.
  4. The Scrum Master
  5. Nobody
  1. The development team
  2. The management
  3. Der Product Owner
  4. The Product Owner and the Development Team
  5. The Scrum Master
  1. Avoid changes to the sprint backlog
  2. Assign tasks to developers
  3. Prioritize the Product Backlog items
  4. Measuring team members' performance
  5. Moderate meetings and eliminate impediments
  1. The Product Owner determines who can best work together in a team from a product perspective.
  2. The disciplinary superiors decide who goes into which team.
  3. The developers themselves organize themselves into appropriate teams.
  4. The product owners determine who can best work together in a team from a product perspective.

Dozent des Vortrages Scrum Exam Prep: Content Review (Sprint 2)

Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider

Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider

Sebastian Schneider arbeitet seit 2005 mit dem agilen Projektmanagement Framework Scrum, hat eine Vielzahl von Projekten selbst als Product Owner, Scrum Master, Agile Coach und Certified Team Coach (Scrum Alliance) begleitet und berät seit 2011 Kunden in unterschiedlichen Branchen mit Schwerpunkt Automotive. Mit dem ScrumKurs24.de stellt er eine Wissensbasis rund um Scrum zur Verfügung und hat es sich zur Aufgabe gemacht, Kunden zu befähigen Produkte zu entwickeln, die deren Kunden lieben!

Kundenrezensionen

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