Agile Requirements Engineering RE_… · Design Thinking@Insiders Bring different expertise together ... • Gojko Adzic: Specification by Example: How Successful Teams Deliver the

Michael Ehresmann, Michael Rölle, Christian Sporer

Agile Requirements Engineering

Insiders Technologies

Leading vendor

„intelligent document processing and business process optimization“

| 05.02.2015 |

© Insiders Technologies Page 2

Insiders Technologies Founded 1998 German Research Center for Artificial Intelligence (DFKI) 120 Employees

| 05.02.2015 |


More than 800

| 05.02.2015 |

© Insiders Technologies Seite 4


Industries: Insurance & financial services

Seite 5 | 05.02.2015 | © Insiders Technologies


Industries: Manufacturing, Retail


Insiders world-wide


Multichannel Management


Multichannel-Management


Archiv

ERP

CRM

Konfiguration Administration

Extraktion Klassifikation

Verifikation

Reporting

Intelligente Kopplung an Geschäftsprozesse

4 Nach-

bearbeitung

3

Automatische Analyse

2 Anbindung aller Eingangskanäle

1

Analysedienst


A B D C

KLASSIFIKATION UND EXTRAKTION DER RELEVANTEN DATEN

1 NACHBEARBEITUNG DER AUSGELESENEN DATEN

2

INTELLIGENTE KOPPLUNG AN GESCHÄFTSPROZESSE

3

ARCHIV PDF/A

CRM/ERP

Working Fields


Image Processing Self-Learning Autoadaption Domain Specific Language Search Technologies Content Classification

Technologies


Web Verifier


Insiders App


INTELLIGENT E-MAIL


smart E-MAIL PILOT



Insiders-technologies.de

| 05.02.2015 |


Research & Development


Joint R&D Lab

Insiders Technologies is a


Development@Insiders


Design Thinking Scrum & eXtreme Programming

Design Thinking@Insiders

Bring different expertise together

Put the customer into the center – empathy phase

Set up a space for creativity

Let the team produce prototypes

Fail early and often - Test prototypes and learn

Find best ideas and solutions


SCRUM@Insiders


The Product Backlog


Requirements Document

Ordered Featurelist

Product Backlog Item

The Product Backlog


PRIORITY - ORDER HIGH

LOW


The Product Backlog


Prouct Backlog Itemem

User Stories Examples Use Cases

A promise for a conversation – User Story


What is a good User Story?

Independent

Negotiable

Valuable

Estimable

Small

Testable


Build right or Right product?


Right product

Build right

Specification by example Com

mun

ity fo

cus

in la

st 1

0 ye

ars

Maintenance nightmare

Useless crap

Success Business failure

The process


business goals deriving scope from

goals

specification with

examples

specifying collaboratively illustrating

using examples

scope (user stories, …)

refining the specification

key examples

Deriving scope from goals



As a jet pilot, I want the F16 to fly Mach 2.5, so that I can espace any fight.




specification with

examples

The process



goals


using examples



key examples

Specify collaboratively


Developer Tester Business Analyst

Illustrating using examples

Best Practices Realistic examples No abstract equivalence classes (e.g. smaller than 10) No combinatorial task to find examples only key examples No clean copy use pen & paper Lo-Fi prototypes for the GUI Play with the data to find new examples


specification with

examples

The process



goals


using examples


key examples


Refining the specification


Rules • Free delivery is offered to VIP customers once they purchase a certain

number of books. • The minimum number of books to get free delivery is five • Free delivery is not offered to regular customers • Free delivery is not offered to VIP customers buying anything other than

books Examples

Customer type Cart contents Delivery Customer type Cart contents Delivery VIP 5 books Free

Customer type Cart contents Delivery VIP 5 books Free VIP 4 books Standard


Regular 10 books Standard


Regular 10 books Standard VIP 5 washing machines Standard


Regular 10 books Standard VIP 5 washing machines Standard VIP 5 books, 1 washing machine Standard

An Example

Use Context

As a customer I want to see the availability of a computer configuration so that I can change my configuration based on what is available.


possible stock states for parts: • Available

• Ordered

• Out of stock

CPU

RAM

HDD

Main-board

An Example

Use Context

As a customer I want to see the availability of a computer configuration so that I can change my configuration based on what is available.


possible stock states for parts: • Available

• Ordered

• Out of stock

CPU

RAM

HDD

Main-board

Let‘s specify collaboratively!

The Solution

Rules

If all parts are available the computer is available

If at least one part is out of stock, then the computer is out of stock

If no part is out of stock and at least one part is ordered, then the computer is ordered

(An empty or incomplete configuration is not orderable)


Agile Planning

Backlog Managment


Rank Order



essential

dispensable

Level of Detail



fine-grained i.e., small user stories

coarse-grained i.e., epics

20 %

80 %

size


Product Backlog Item Product Backlog Item

Backlog Grooming

Backlog Grooming


rearrange split

1

How to estimate ?


1

Choose a reference


1

Estimate the size


possible values: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,

1

Estimate the size


possible values: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,

1

Estimate the size


possible values: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,

Relative Estimation


Magic Estimation Game!

Magic Estimation Game

Seite 54 | 2/5/2015 | © Insiders Technologies

1 2 3 5 8 13 …

Magic Estimation Game


Draw different columns on a board.

Label each column with one number representing the size of the items.

The Product Owner presents each item to the team.

The Product Owner distributes the items randomly and evenly among the team.

Each team member chooses the right column (i.e. size) for his items.

Once all items are on the board, the team members can change other estimations.

Items that often change columns are removed from the board and discussed

afterwards.

Using the Magic Estimation Game, you can estimate a complete backlog within one

or two hours!

Release Planning



Iteration 1

Iteration 2

Iteration 3

Iteration 4

Release 1

Estimates are measured in story points. I know my team can implement 20 story points in one iteration. If the product backlog contains 80 points of items, we will need 4 iterations.

Story Map – 2 dimensional backlog


Epics

Stories

Story Map – 2 dimensional backlog


Find the epics – the big stories - for your product Bring the epics into the right order. The most important epic is on the top left. After that, assign each backlog item to the corresponding epic. Order the Items for instance with lines as priority. In the scope of an epic, it should be very easy to order the items.

The first line in the Story Map is your smallest possible product.

Conclusion

Agile specification is teamwork.

The customer is part of the team.

Backlog grooming is a steady process.

For each requirement, choose the right technique.

Do not rely on a single specification technique.

Prioritize the requirements on the basis of their business value.


The books

• Gojko Adzic: Specification by Example: How Successful Teams Deliver the Right Software, 978-1617290084

• Kent Beck: Extreme Programming Explained: Embrace Change. Addison-Wesley, 0201616416

• Mike Cohn: User Stories Applied. For Agile Software Development. Addison-Wesley, 978-0-321-20568-1

• Mike Cohn: Agile Product Management with Scrum: Creating Products That Customers Love. Addison-Wesley, 9780321605788

• Robert C. Martin: Agile Estimating and Planning. Prentice Hall, 0131479415

• Ken Schwaber: Agile Software Development with Scrum. PEARSON STUDIUM, 978-0132074896


http://www.amazon.de/Agile-Software-Development-Scrum-Schwaber/dp/0132074893/ref=sr_1_4?ie=UTF8&qid=1421918918&sr=8-4&keywords=Ken+Schwaber

Exercise

Specification by Example Friday, Febrary 13th 8:00 – 9:30 am


Documents

Agile Requirements Engineering RE_… · Design Thinking@Insiders Bring different expertise together ... • Gojko Adzic: Specification by Example: How Successful Teams Deliver the