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

video locked

Über den Vortrag

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


Quiz zum Vortrag

  1. The vertical axis shows project progress, the horizontal axis shows team capacity.
  2. The vertical axis shows the number of tasks, the horizontal axis shows the team's velocity.
  3. The vertical axis shows the story points, the horizontal axis shows the work efficiency.
  4. The vertical axis shows team utilization, the horizontal axis shows sprint iterations.
  5. The vertical axis shows the remaining work, the horizontal axis shows the time course of the sprint.
  1. The Sprint Backlog remains dynamic throughout the Sprint as the team can add or remove new work.
  2. The sprint backlog must be completely filled at the beginning of the sprint and may not be changed.
  3. The Sprint Backlog is only adjusted by the Product Owner during the Sprint.
  4. The Sprint Backlog is automatically controlled and updated by the Burn Down Chart.
  5. The Sprint Backlog is only updated and adjusted in the Sprint Retrospective.
  1. The developers decide independently on the concrete implementation of their tasks, while the product owner is responsible for the "what".
  2. The developers follow a predefined technical framework specified by the stakeholders.
  3. Developers must have their implementation decisions approved by the Product Owner.
  4. The developers follow the technical specifications of the project management.
  5. The developers coordinate their approach with the Scrum Master and follow his technical specifications.
  1. Stakeholders can communicate feature requests to the product owner and development team in parallel.
  2. Stakeholders can discuss their requests directly with developers and then inform the product owner.
  3. Stakeholders must first submit their requests to the Scrum Master, who then forwards them to the team.
  4. Stakeholders coordinate their requests with management, who then bring them to the team.
  5. Stakeholders and customers must submit feature requests through the product owner and may not approach the developers directly.
  1. The team composition can be flexibly adjusted at any time to optimize productivity.
  2. The team composition should not be changed during an ongoing sprint; changes are only possible between sprints.
  3. The team composition is determined by the stakeholders according to the project priorities.
  4. The team composition is determined by the Product Owner based on the Sprint requirements.
  5. The team composition is re-evaluated weekly by the Scrum Master and adjusted if necessary.

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

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