Agile Practices: User Story and INVEST
Über den Vortrag
Der Vortrag „Agile Practices: User Story and INVEST“ von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider ist Bestandteil des Kurses „Sprint 3“.
Quiz zum Vortrag
What should be avoided when splitting up a user story that is too large?
- Separation by user interfaces
- Separation by user paths
- Separation by data types
- Separation according to rules
- Separation according to technical components
What is the recommended approach if a user story is too big for a sprint?
- Mark the story as Epic and leave it unchanged
- Divide the story into frontend and backend tasks
- Divide the story into technical components
- Divide the story into smaller stories using the SPIDER technique
- Distribute the story sequentially across multiple sprints
What is the main purpose of a user story?
- Describe the "what" from the user's perspective
- Defining the "how" of implementation
- Plan development times precisely
- Define technical specifications
- Document test cases
What is the difference between acceptance criteria and the definition of done?
- Acceptance criteria apply only to a specific story, Definition of Done for all
- Acceptance criteria are optional, Definition of Done is mandatory
- Acceptance criteria are technical in nature, Definition of Done describes business objectives
- Acceptance criteria are created after the sprint, Definition of Done before
- Acceptance criteria are defined by the team, definition of done by the product owner
Which component of a user story enables verification of completion?
- Card
- Collaboration
- Communication
- Conception
- Confirmation
Which components belong to the "three Cs" of a user story? (Choose three answers.)
- Card (Carte)
- Collaboration
- Communication
- Conception
- Confirmation
Which component of the SPIDER approach is only recommended in exceptional cases?
- Data
- Interfaces
- Paths
- Rules
- Spike
How should acceptance criteria ideally be formulated?
- With detailed implementation steps
- With a focus on observable behavior
- With precise design specifications
- With internal system requirements
- With concrete technical solution specifications
What does the letter "I" in the INVEST criterion stand for?
- Implementable (Implementierbar)
- Important
- Independent
- Innovative (Innovativ)
- Instructive
Dozent des Vortrages Agile Practices: User Story and INVEST
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
5,0 von 5 Sternen
| 5 Sterne |
|
5 |
| 4 Sterne |
|
0 |
| 3 Sterne |
|
0 |
| 2 Sterne |
|
0 |
| 1 Stern |
|
0 |
