20100220 sit bonn v1 0

Agile SAP: Mission Impossible?

SAP Inside Track Bonn

Twan van den BroekFebruary 20, 2010

SIT Bonn / Agile SAP: Mission Impossible?

Introduction

• CIBER NL– Principal Consultant – SAP NetWeaver Solution Architect

• Other– SAP project experience since 1995– Speaker at international conferences– Author of articles

• Web– Blog: twanvdbroek.blogspot.com– Twitter: @tbroek– LinkedIn: tbroek

2


Why are we here?

3

Intro

Agile?

How to start?

A day at the office

Arrival

Experiences

Why are we here?

4

ASAP project approach


Waterfalls didn’t help

Waterfall issues:

- Lots of discussions during business design

- Delivery final versions of designs took long due to reviews

- Time pressure ‘given’ to realization team

- Working on ‘illegal’ versions of design

- No efficient preparation of testing activities

- Very difficult to keep focus within the team

5


Agile?

6

Intro

Agile?

How to start?

A day at the office

Arrival

Experiences

Why are we here?


What does being agile mean?

• Collaborate– Different roles, same time and location

• Iterate– Plan - Deliver - Evaluate– Two to four weeks

• Deliver– Deliver early and frequent– Small units of work / smart use cases

• Plan– Daily– Measure continuously– Test early and often

• Simplify communicaton– Simple dashboards, burn down charts, pair programming

8


What is Scrum?

9

© SAP AG 2009. All rights reserved. / Page 4

'()*+,-#(&./)$&0+122/3/#$34+.)+567/$#77+!"/0/.4+Deliver Competitive Advantage with a Business Process Platform

Business Agility

Business Process Reengineering

Enterprise Resource Planning

Operational Efficiency

Business Network Transformation

Business Process Platform

1990s 2000s 2010s

8


What does being agile with SAP mean?

• Involve– Product owner, business users– Enterprise architect, business analysts

• Standardize– All roles work on same product– Simplify product life cycle– Model front end and services in smart use cases– Test and deliver individual services– Integrate front end and services each iterations

• Expect issues– “Agile is for small projects”– “We need to design the whole system upfront” – “Sorry, connectivity to our system is available in 4 months”– “We need to review every use case before you can implement it”

11


www.smartusecase.com

12

Smart use cases?

http://www.smartusecase.com

http://www.smartusecase.com


What is smart?

13

Propose Scope Realize Realize Realize Realize Finalize Manage

Createproject proposal

Writeproject plan

Deliverworkingsoftware

Round upsoftware

Maintainsoftware

Smart: Sander Hoogendoorn, Principal Technology Officer, Capgemini


Smart iterations

14

Propose Scope Realize Realize Realize Realize Finalize Manage

Build

Evaluate

Plan

What product(s) do we want to deliver?

Define done

Deliver product(s) using product cycle

Visualise progress

Are we up to speed?

Is our process optimal?

Are the product(s) done?


How to start?

15

Intro

Agile?

How to start?

A day at the office

Arrival

Experiences

Why are we here?


Build your team

• Product owner– Responsible for gathering all business requirements (scope)– Prioritize requirements

• Scrum team– Business analyst /2– Information analyst /1,5– SAP CRM /1– SAP XI/ BPM /2– SAP ABAP /1– .NET developer /1– Test /2– Scrum master /1– Agile coach /1

16

Design together with business

Modeling smart use cases

Estimating smart use cases


Product Backlog

21

Determine velocity


A day at the office

23

Intro

Agile?

How to start?

A day at the office

Arrival

Experiences

Why are we here?

Daily scrum meeting

25

Project wall with dashboard

How far are we?Done / Total

How many points realized on daily basis

Burn down chart

How many points realized per iteration

Project pie chart

Dashboard to track single smart use cases

Pair programming/ customizing


Project Burn down chart

27


Project statistics /2

28

Pair testing

Demo end of each iteration

Evaluate


Experiences

32

Intro

Agile?

How to start?

A day at the office

Arrival

Experiences

Why are we here?


Key take aways

Lessons learned

• Agile is no silver bullit• Realistic scope for sprint backlog

– Parkinson’s law, Student syndrome, Overflow

• Focus team on team delivery– Prevent everyone is busy with everything

• Involve project environment– Avoid long lasting review cycles– Participate with application management

• Be firm in following approach– Heartbeat in iterations– Prevent to catch up on old habits

• Co-located project team– Prevent communication gaps

33


Key take aways

Experiences agile SAP

34

• Focus– Connect teams and roles– High speed project– Day to day focus on scope– Great planning insights– Discussion on priorities instead of deadlines– Documentation is up to date– Very agile to changing requirements– Connects business and IT to deliver business needs with a short

time to market

• Change management– “Agile will not work in the SAP world”– Skeptical attitude turned into faith towards end– “Just do it”, think big, start small


Key take aways

Tips to apply agile SAP within your project

• Use project wall / dashboard– Facilitate collaboration, communication and insight

• Scrum is a process, smart is complementary and offers techniques in addition– Single modeling technique with smart use cases for whole project– Good unit of work, small enough to oversee and fit within iteration– Easy project estimation

• Product owner is key role to success• Agile / SOA / SAP project: Think in services, focus on

processes and deliver in iterations

35

Enthusiastic on project and approach


Questions?

37

Twan van den Broek

CIBER Nederland BV

Meerkolklaan 15

Postbus 843

5600 AV Eindhoven

M : +31 (0)6 29 735 952

T : +31 (0)40 232 90 90

F : +31 (0)40 232 90 91

E : [email protected]

I : www.ciber.nl

twanvdbroek.blogspot.com

Twitter: @

tbroek