The document discusses agile requirements management in Scrum, highlighting the importance of user stories and acceptance criteria for effective project execution. It provides examples of user stories, such as a skilift operator tracking ticket sales, alongside specific requirements for system performance and user interface design. The conclusion invites questions and refers to additional resources on agile requirements engineering.

1. Think different! Agiles Anforderungsmanagement
auf den Punkt gebracht.
Raphael Auf der Maur
Senior Business Analyst & Project Leader
Dipl. Inf. Ing. ETH, CSP, Certified Professional RE
www.bbv.ch
www.bbv.ch

2. Motivation
Der wesentliche Unterschied
Requirements Management in Scrum
Q&A
www.bbv.ch
www.bbv.ch

3. Motivation
www.bbv.ch

4. Motivation
www.bbv.ch

5. www.bbv.ch

6. Motivation
Der wesentliche Unterschied
Requirements Management in Scrum
Q&A
www.bbv.ch
www.bbv.ch

7. www.bbv.ch

8. www.bbv.ch

9. www.bbv.ch

10. www.bbv.ch

11. www.bbv.ch

12. www.bbv.ch

13. www.bbv.ch

14. Oft praktiziert
www.bbv.ch

15. Anti-Pattern
www.bbv.ch

16. Scrum
www.bbv.ch

17. Motivation
Der wesentliche Unterschied
Requirements Management in Scrum
Q&A
www.bbv.ch
www.bbv.ch

18. User Story
As a <type of user>, I want <some goal> so that <some reason>.
Story Description Priority
As a skilift operator, I want to be able to count all lift rides grouped by ticket
type, so that I am able to account the tickets with other skilift companies in the
ressort at the end of the month. 633
Acceptance Criteria Story Points
- show screen where all ticket types are shown with ticket name, total lift ride count per season per line.
- Screen must be pixel and color accurate with User Interface Design, Page 13
- ticket names which are too long for one row shall be shortened with Elipsis.
- report selection criteria must include from and to date as a date selector control. Dates must be
13
changeable manually (format DD.MM.YYYY) and are validated on input time (from date must be after to
date and in correct format). Validation error highlights box according UID.
- Default selection times are 1st of november of current season (from) and 31st of april of current season
(e.g. 01.11.2010 – 31.04.2011)
- systems response time must be below 1 second in 90% of the cases and below 3 seconds in 100% of the
cases.
Comments
Export to Excel, PDF, CSV will be part of another story. Story ID: 53.6
www.bbv.ch

19. vertikale Requirements
Beispiel:
„The system shall be able to store a price in EUR, CHF and USD for a ticket.“ vs.
„As an operator, I want to be able to define ticket prices for the tickets defined in
the system in the administration screen.“
www.bbv.ch

20. Inkrementell erweiterte Stories
1 2 3
www.bbv.ch

21. Motivation
Der wesentliche Unterschied
Requirements Management in Scrum
Q&A
www.bbv.ch
www.bbv.ch

22. Fazit
www.bbv.ch

23. Any questions?
Booklet & Poster zum Thema Agiles Requirements Engeneering am bbv Stand
oder unter www.bbv.ch
Blog: www.agilerequirementsengineering.com
www.bbv.ch