Scrum Example: Creating Requirements von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider

video locked

Über den Vortrag

Der Vortrag „Scrum Example: Creating Requirements“ von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider ist Bestandteil des Kurses „Sprint 3“.


Quiz zum Vortrag

  1. The Product Owner is solely responsible for prioritizing the backlog items.
  2. The Product Owner can delegate both accountability and responsibility for the Product Backlog.
  3. The Product Owner must personally write and document all Product Backlog items.
  4. The Product Owner has accountability but can delegate responsibility for certain tasks.
  5. The Product Owner transfers responsibility for the Product Backlog to the Development Team.
  1. ...offer more flexibility in technical implementation, while user stories prescribe precise solution paths.
  2. ...are suitable for complex and extensive projects, while user stories are more suitable for small projects with few requirements.
  3. ...are unsuitable for software projects, while user stories can only be used for software development projects.
  4. ...are short and precise, while user stories contain comprehensive descriptions of user benefits.
  5. ...are solution-oriented and specified in detail, while user stories focus on user benefits and the flexibility of the implementation.
  1. For projects in complex environments where predictable requirements and stable framework conditions can be found
  2. For projects in complex environments where incremental development and adaptability are required
  3. For projects in moderately complex environments, with predominantly technical challenges and without customer interaction
  4. For projects in simple environments that work exclusively with detailed and pre-specified requirements
  5. For projects in simple environments where regular sprint reviews are required
  1. Essential component: Reason (Why)
  2. Essential component: Role (Who)
  3. Essential component: Desire (What)
  4. Optional component: Reason (Why)
  5. Optional component: Wish (What)
  1. Maximizing value
  2. Writing the backlog items (backlog item writing)
  3. Daily updates
  4. Full cost calculation
  5. Accessibility of the backlog (transparency)

Dozent des Vortrages Scrum Example: Creating Requirements

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