This document discusses applying agile principles and methods to business process management (BPM) projects. It outlines both the traditional waterfall and agile approaches to software development. While BPM projects often follow a waterfall approach, the document argues they could benefit from agile principles like short iterations, frequent releases, user stories, and a backlog prioritization process. It provides examples of how agile practices could be adapted to a BPM project, including using user stories, iterations and releases to develop process functionality incrementally.

1. Agile BPM – Impossible?

2. Robert Gimbel
• Agile since 2006
• BPM since 2008
• Agile BPM since 2010

3. Waterfall Approach to Software Development
Specification
Coding
Test
Rollout

4. Agile Approach to Software Development
Feature 1
Feature 2
Feature 3
Feature 4

5. It‘s all about value
Agile Value
Value
Waterfall Value
Team Cost
Time

6. Who is agile?

7. BPM – Agile or Waterfall?
Value
ROI
agile BPM-
Project
waterfall
ROI
BPM-
Project
ROI
ROI
BPM-
Project
ROI
BPM-
Project BPM-Project
Time

8. What‘s your BPM Project like?
• Degree of change?
• Level of automation?

9. Agile Methods in BPM Projects?
Business IT
Interations
(Timeboxing,
Review)
Product Backlog, Estimation,
Prioritization Commitment
Agile Selforganizing
Agile BPM
Requirements Team
User-/Customer-
Agile Testing
feedback
Burndown
Charts

10. Quick Releases Release 1
Task 2.1
Task 1 Task 3
Task 2.2
Task 2.1
Task 1 Task 3
Task 2.2
Release 2

11. Process and Agile Requirements
create new
article
article administration
open article delete
administra- article
tion
modify
article
User Story 1 User Story 3 User Story 6 User Story 9
User Story 2 User Story 4 User Story 7
User Story 5 User Story 8

12. Short Iterations and Quick Releases
Release 1.1 Release 1.2 Release 1.3
open article
Artikel-
administra-
verwaltung User Story 2 User Story 1
tion
öffnen
create new
article User Story 3 User Story 4 User Story 5
delete
article
User Story 9
modify User Story 7
article User Story 6
User Story 8

13. Product Backlog
Feature 3
Sprint 1 Burndown
Feature 23
Feature 1
Feature 7
Sprint 2 Feature 11
Feature 16
Feature 17
Sprint 3 Feature 22
Feature 13
Review 1 Review 2 Release Time

14. Release planning
I1 (100%) I2 (75%) I3 (50%) I4 (40%) I5 (30%) I6 (30%) I7 (20%)
Today Release 1 Release 2
Level of detail, probability of realization

15. Practical Example: Process View
User Story Link

16. Practical Example: User Story View
User Story
GUI
Priority
Aceptance criteria

17. Practical Example: Product Backlog
Priority
Iterations

18. It‘s Tough and it‘s Fun!
Comments?

19. camunda services GmbH
Thank You! Zossener Str. 55-58
1096 Berlin
1
Telefon: +49 30 664 0409-00
Telefax: +49 30 664 0409-29
Email: info@camunda.com
Robert Gimbel
consultant
robert.gimbel@camunda.com
SOA Symposium
5th October 2010, Berlin
Der Praxis-Blog zu BPM:
www.bpm-guide.de