Fundamentals of Requirement Engineering

▪ Requirements Engineering as Continuous Process
▪ Value-driven development
▪ Simplicity as Essential Concept
▪ Inspect and Adapt 

▪ Bridging Requirements Engineering and Agile Principles
▪ Benefits, Misconceptions and Pitfalls for the Use of Requirements Engineering
▪ Agile development in a non-Agile environment
▪ Interaction with stakeholders outside the IT organization
▪ Product vs. project organization
▪ Handling of complex problems by scaling
▪ Initial Requirements Definition

▪ Difference between traditional specification documents and backlogs
▪ Different levels of granularity in requirements
▪ Different specification formats for the different artifact types in Agile processes (i.e. textual vs. template-based vs. diagrammatic)
▪ Definition of Ready and Definition of Done in Agile Requirements Engineering processes
▪ Difference between Prototype and Increment
▪ Context Model, Epic, User Story, Backlog, Roadmap, Requirement, Definition of Done,

▪ How to elicit requirements in Agile Requirements Engineering
▪ Right level of detail for backlog items
▪ Right update cycles for the product backlog
▪ Requirements Documentation
▪ Requirements Validation and Negotiation
▪ Requirements Management