How to deal with requirements in an Agile context? RE@Agile primer How to deal with requirements in an Agile context?

Pleased to meet you: Hans van Loenhoud hans.vanloenhoud@ireb.org www.ireb.org International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. Route Requirements in Agile? The RE@Agile Primer Requirements in Agile! International Requirements Engineering Board e.V. 20-11-2018

Requirements? Just ask the Product Owner! International Requirements Engineering Board e.V. 20-11-2018

Common misunderstandings about requirements in Agile User stories are enough Upfront is evil Only working software counts documen- tation = waste! International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. #1: Upfront is evil No! Too much detail upfront is waste Upfront, you do need a vision to set the direction The highest level of requirements, Specifying the overall demands the solution should satisfy to fulfill its purpose Set a framework for all development without constraining creativity A vision always needs further refinement International Requirements Engineering Board e.V. 20-11-2018

#2: User stories are enough User stories are great to capture functional requirements To get the complete picture, you also need non-functionals (quality requirements, constraints) Describing a User Story is quite simple Overseeing a complete product backlog of all related User Stories and keeping it consistent is quite tough International Requirements Engineering Board e.V. 20-11-2018

#3: Documentation is waste No! Except for tiny projects with small teams that deliver a product without direct users that needs no future maintenance Documentation is … a means to bridge time and space a thinking tool to sharpen and order one’s thoughts often a deliberate part of the product sometimes a legal obligation sometimes a marketing instrument International Requirements Engineering Board e.V. 20-11-2018

#4: Only working software counts No! Working software is worthless if no one knows … how it works how to work with it A project is not about output, but about outcome In fact, the most valuable product is knowledge The focus should be on learning instead of building International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. RE@Agile Primer 16-5-2019 Poor Product Owner Comes from the business Has a management role there Is full-time assigned to the project Represents the business Not just his own department, but the whole business Knows all ins and outs of all stakeholders involved Is an expert in his profession and knows everything about IT and about the Agile way of working … so also an expert on requirements and therefore made responsible for the product backlog International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

International Requirements Engineering Board e.V. A helping hand RE@Agile International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. Route Requirements in Agile? The RE@Agile Primer Requirements in Agile! International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. A requirement is ‘a condition or capability needed by a user to solve a problem or achieve an objective’ (IEEE Std 610.12 - 1990) International Requirements Engineering Board e.V. 20-11-2018

We all have requirements International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. From the waterfall … Needs Use Deploy Analyze Build Design Test International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. … to Agile Iterative Needs Use Analyze Incremental Design Test Deploy Build International Requirements Engineering Board e.V. 20-11-2018

Continuous Requirements Engineering Not a single initial phase but a continuous attention point International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. Points of engagement Feedback ………… Product increment Backlog … Backlog item Team Stakeholders input for develops give reviewed by 1. Initial definition 2. Selection 4. Update 3. Validation 5. Timing International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. Route Requirements in Agile? The RE@Agile Primer Requirements in Agile! International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. RE@Agile Primer Requirements Engineering in Agile context Developed by IREB working group “RE@Agile“ Published in Baumann, L. et al. (2017): IREB CPRE – RE@Agile Primer – Syllabus and Study Guide (Version 1.0.1), IREB, Karlsruhe. One day introduction A bird’s eye overview of the topic Level in Bloom’s taxonomy: K1 ‘remember’ Ends with a certification exam 22 MC questions, 40 minutes (+25%), pass mark 70% International Requirements Engineering Board e.V. 20-11-2018

RE@Agile Primer set-up 16-5-2019 RE@Agile Primer set-up Introduction to the topic Relevant theory Discussion & exercises Online practice exam Feedback ………… Product increment Backlog … Backlog item Team Stakeholders input for develops give reviewed by 1. Initial definition 2. Selection 4. Update 3. Validation 5. Timing International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

RE@Agile Primer contents 16-5-2019 RE@Agile Primer contents Motivation Fundamentals Artifacts and techniques Organizational aspects Feedback ………… Product increment Backlog … Backlog item Team Stakeholders input for develops give reviewed by 1. Initial definition 2. Selection 4. Update 3. Validation 5. Timing International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

RE@Agile Primer topics 16-5-2019 RE@Agile Primer topics Motivation Fundamentals Artifacts and techniques Organizational aspects Core values Why Agile? Why RE? RE + Agile = RE@Agile Related approaches Design Thinking Design Sprint Lean Startup International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

RE@Agile Primer topics 16-5-2019 RE@Agile Primer topics Motivation Fundamentals Artifacts and techniques Organizational aspects Agile methods Scrum Product Owners Continuous process Value driven Simplicity Improvement International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

RE@Agile Primer topics 16-5-2019 RE@Agile Primer topics Motivation Fundamentals Artifacts and techniques Organizational aspects Artifacts Vision  Context  etc. Techniques for Elicitation Documentation Validation Management International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

RE@Agile Primer topics 16-5-2019 RE@Agile Primer topics Motivation Fundamentals Artifacts and techniques Organizational aspects Maturity organization Context: customer centered Scalability Upfront vs. continuous International Requirements Engineering Board e.V. 20-11-2018 © Taraxacum, 2017

International Requirements Engineering Board e.V. For whom? Product owners who want to learn more about requirements Agile team members who feel uncomfortable about the present state of requirements Analysts who feel unsure about their role in an Agile team Feedback ………… Product increment Backlog … Backlog item Team Stakeholders input for develops give reviewed by RE@Agile International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. And next? CPRE Expert Level Prerequisite: 3 Advanced Levels; 2 Advanced Levels may be substituted CPRE Advanced Levels Elicitation Modeling Management RE@Agile The modules Most important education in RE worldwide – besides the university education Prerequisite: CPRE Foundation Level CPRE Foundation Level RE@Agile Primer Prerequisite: None International Requirements Engineering Board e.V. 20-11-2018

International Requirements Engineering Board e.V. The End Requirements in Agile? The RE@Agile Primer Requirements in Agile! International Requirements Engineering Board e.V. 20-11-2018

Requirements: too important to leave them to the PO International Requirements Engineering Board e.V. 20-11-2018