Agile Requirements Management with SCRUM

Course overview

What is Requirements Engineering (RE)? Distinction between agile RE and classical RE: What are the differences? The Scrum Flow as a process model of Scrum, the Product Owner as product manager, requirements manager, and requirements engineer. The product vision: Vision Board, changes in the product vision. Product Backlog: The 3 tasks of the Product Backlog, the central instrument of project planning, requirements documentation, and requirements management, granularities in the Product Backlog, DEEP, Backlog Refinement, status of Product Backlog entries, combining Product Backlog and Kanban, ARE and Change Management, granularities of requirements: Epics, Features, User Stories. User Stories: tasks, CCC, characteristics, INVEST, benefits/justification of a User Story, variants for User Stories, what User Stories are not, best practices for User Stories, User Stories for back-end systems, User Stories and User Interface. Breaking down User Stories: simple techniques, Lawrence Pattern, SOUND Pattern, anti-patterns for cutting User Stories, what happens with the cut User Stories. Evaluating and prioritizing requirements: MVP right and wrong, evaluation criteria, prioritization methods: two-criteria classification, prioritization based on urgency and value, Buy-a-feature, Weighted Scoring System, Weighted Shortest Job First. Acceptance criteria: advantages, uses of acceptance criteria (AKs), tasks of acceptance criteria, unstructured AKs, structured AKs with initial situation-event-expected outcome, scenario-based acceptance criteria, acceptance criteria templates, Specification By Example (SBE), rule-based acceptance criteria. Constraints, Epics, Topics, Glossary: overview of non-functional requirements (constraints), constraints and functional requirements, relationships between constraints and User Stories, acceptance criteria for constraints, breaking down constraints, Epics, Product Backlog with Epics, proposal for Epic template, topics, forming subsets with topics, glossary: what is included and what to consider. Working with stakeholders: what are stakeholders, stakeholder involvement, stakeholder documentation, rough classification into stakeholder classes, stakeholder knowledge matrix, the Kano model for user-oriented categorization of requirements. Techniques for eliciting requirements overview, personas, User Stories expanded with persona, attributes for personas, wireframes, scenarios, flowcharts (Wire Flow), storyboards, User Story Map, Event Storming, User Stories and models, task analysis and User Stories, analyzing requirements. Quality in agile Requirements Engineering: INVEST, DEEP, quality improvements for User Stories, Definition-of-Ready, Definition-of-Done. Structuring large amounts of requirements: Product Backlog Board, Story Maps, models, Story Maps with hierarchical levels. Agile Requirements Engineering in large projects: Product Owner with multiple teams, Chief Product Owner, master and area backlog, backlog with views, t…

Upcoming dates

• 2026-11-10T23:00:00.000Z · 2026-11-12T23:00:00.000Z · Köln · Seminar
• 2027-01-10T23:00:00.000Z · 2027-01-14T23:00:00.000Z · Online-Seminar
• 2027-01-31T23:00:00.000Z · 2027-02-02T23:00:00.000Z · Köln · Seminar
• 2027-01-31T23:00:00.000Z · 2027-02-02T23:00:00.000Z · Online-Seminar

More courses in this field

• Qualification as a City Logistician

  SVG Nord Service und Vertrieb GmbH

• Project Management in the Context of AI, EU AI Act, and Agile Management

  A-Leecon GmbH

• AI in Cloud Computing with Salesforce AI Developer

  New Horizons Nord

• Nurse - Initial Training

  gfg Gesellschaft für Gesundheitsfachberufe gGmbH gfg Bildungszentrum Pflege (Aus- und Weiterbildungszentrum)