Scope Blended: 3 days (Digital Module + 2 Workshop days) After our training in Requirements Management you will... - Understand what it means to work Agile with requirements management - Master writing requirements as user stories - Be able to structure, prioritise and plan user stories Training content Introduction to requirements management The requirements specification trap and quality in information systems Sources of requirements: process model, goal model, concept model, stakeholder model, existing systems, GUI Agile methods and Scrum Key concepts: the Agile Manifesto, User Story, Backlog, Task, Sprint The agile team: Product Owner, Scrum master / Agile master, Developers and testers Pitfalls of agile development User roles and User Stories Identifying and describing user roles Personas Purposes of a User Story What makes a good User Story, INVEST Epics Story Mapping Background and purpose Ordering User Stories over time using activities Describing dependencies between User Stories Prioritising User Stories Allocating User Stories to releases More about User Stories Functional requirements and quality requirements (non-functional requirements) Principles for splitting a User Story into several The sprint backlog The agile testing matrix Acceptance criteria What a User Story is and is not Different types of requirements Describing quality attributes with User Stories User Stories that affect the architecture Qualities/non-functional requirements and the backlog
When you complete the course, Astrakan issues your certificate. Your name, the course content and the issue date are encrypted and secured on blockchain, so it cannot be changed, and anyone can check that it is genuine.
Sample Credential with placeholder data. Each credential is issued with the recipient’s details and is verifiable with the provider.
