Download - 20090924 Agile Sap Sdn Vcd09 V1.0
Agile SAP: Mission Impossible?Twan van den BroekSAP SDN Virtual Community Day24 September 2009
Intro
• Twan van den BroekPrincipal Consultant CIBER NLScrum master@tbroek“Agile can not work within the SAP world”
• (Sander Hoogendoorn)Principal Technology Officer Capgemini and Agile evangelistAgile Coach@aahoogendoornAuthor
A.C.W. van den
Broek
3Agile SAP: Mission Impossible
Agenda
4Agile SAP: Mission Impossible
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
LocAL
SAP XI
NS
Amersfoort
TLS
GammamijnNS / Refund
Balie
Automaat
CardInformation
Service
Engraved IDChip ID
Conversie
Balie
Automaat
L2EPS
L3CPS ETDS
L4CCHS
NS.nlccInternet
ccKlantsystemen
ccTicketing
ccOVCP
Finance Center
TLS
SAP CRMVCM CECURE
RTS
BOM LDM
R/3
System landscape
5Agile SAP: Mission Impossible
Solution Architecture in 5 layers
User data
Gamma
Klantgegevens
Cecure
Identificeren Specificeren Valideren
mijnNS.nl
Verwerken Leveren
user
ProductenProduct-catalogus
SAP R/3
TLSiBase
CardMaster
ContracteniBase
SAP CRM CPM
klant
productenProductcombinaties/E-ticket vertaling
contractgeg
kaartgegkaartgeg
kaartgeg
Automaat
Aanvraag ROS, bestaande klant, bestaande kaart
Presentatie
Proces
Integratie
Applicatie
Database
kaartstatus
Contracten
SAP CRM
contract
uitvalcontractgeg
kaartgeg
NAL
leveracties
levertrx
kaartgeg
6Agile SAP: Mission Impossible
Plotting SAP solutions in Solution Architecture
User data
Gamma
Klantgegevens
Cecure
Identificeren Specificeren Valideren
mijnNS.nl
Verwerken Leveren
user
ProductenProduct-catalogus
SAP R/3
TLSiBase
CardMaster
ContracteniBase
SAP CRM CPM
klant
productenProductcombinaties/E-ticket vertaling
contractgeg
kaartgegkaartgeg
kaartgeg
Automaat
Aanvraag ROS, bestaande klant, bestaande kaart
Presentatie
Proces
Integratie
Applicatie
Database
kaartstatus
Contracten
SAP CRM
contract
uitvalcontractgeg
kaartgeg
NAL
leveracties
levertrx
kaartgeg
ccBPM
XI
CRMR/3
7Agile SAP: Mission Impossible
Agenda
Agile SAP: Mission Impossible 8
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
GoalPhasesArchitecture
Project phases
Sept 08
Feb 09
Oct 09
Phase 1Settle basissept08-feb09
Phase 2Prepare country wide roll outfeb09-sept09
Phase nExtend functionality/ travel productsoct09-dec10
9Agile SAP: Mission Impossible
Project waterfalls
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
10Agile SAP: Mission Impossible
Waterfall according to Dr. Winston W. Royce (1970)
11Agile SAP: Mission Impossible
But we seem to forget the way back
12Agile SAP: Mission Impossible
13
ASAP Project approach
Agile SAP: Mission Impossible
Agenda
Agile SAP: Mission Impossible 14
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
Why differentlyPlanningSmart / ScrumProject team
Project approach
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40Sprint
FunctionaliteitModelleren smart use casesActiverenVerlengenDeactiverenmijnns.nlBeheer
Opleveren AcceptatieQA refreshOplevering Local QA 1-julQA inrichten voor PRoSMigratie I baseKS KI T
Transitie naar beheerDemo workshopsAanpassen proceduresBeheer acceptatietestenGebruikers acceptatietesten
Go Live voorbereidingRCC KI TPRD inrichten voor PRoSMigratie I base
MeiAprMrt J ul Aug SeptJ un
980 1 2 3 4 5 6 7KS Release 2009.3
7-7 Deactiveren9-7 mijnns.nl
30-6 Activeren2-7 VerlengenGoals different approach
- Team focus on solution
- Deal with changing insights and priorities
- Delivery in iterations
- Involve environment (Business, BA&A) in design and
demo’s
15Agile SAP: Mission Impossible
What is Scrum?
16Agile SAP: Mission Impossible
Scrum process
Sprint 1An
alyze
Speci
fy
Realiz
e
TestAc
cept
Expected product DeliverySprint/Iteration 1
DeliverySprint/Iteration 2
Final delivery
Sprint 2 Sprint 3Product BacklogList with highlevelrequirements
17Agile SAP: Mission Impossible
Analy
ze
Speci
fy
Realiz
e
TestAc
cept
Analy
ze
Speci
fy
Realiz
e
TestAc
cept
Smart software life cycle
18Agile SAP: Mission Impossible
Smart
• Smart Use Cases– YAGNI, Agile requirements– Identifying smart use cases– Modeling smart use cases– Modeling services to smart use cases
• Smart estimation– Smart use case stereotypes– Smart estimation poker
19Agile SAP: Mission Impossible
Teaming the project
• Product owner– Responsible for gathering all business requirements – Difficulty: No ‘real’ business owner
• Scrum team– Business analyst /2– Information analyst /1,5– SAP CRM /1– SAP XI/ BPM /2– SAP ABAP /1– .NET developer /1– Test /2
20Agile SAP: Mission Impossible
Designing together with business
Modeling smart use cases
Estimating smart use cases
Product Backlog
Agile SAP: Mission Impossible 25
26Agile SAP: Mission Impossible
Project wall with dashboard
Daily scrum meeting
Agile SAP: Mission Impossible 28
Demo and review to conclude every sprint
Acceptance test
Agenda
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
Project Burn down chart
31Agile SAP: Mission Impossible
Project statistics
Agile SAP: Mission Impossible 32
Project statistics /2
Agile SAP: Mission Impossible 33
Experiences
• High speed project• Day to day focus on scope • Connecting roles and teams• Change management in and outside, “Agile will not work in
the SAP world”• Skeptical attitude turned into faith towards end• “Just do it” approach• Documentation is up to date• Very agile to changing requirements• Planning insight• Discussions on priorities in stead of deadlines
34Agile SAP: Mission Impossible
Enthusiastic on project and approach
Agenda
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
Lessons learned
37Agile SAP: Mission Impossible
Realistic scope for sprint backlog Too much will discourage team
Focus team on delivery Prevent busy with everythingInvolve project environment Prevent reviews afterwardsBe firm in following approach Prevent to catch up old
habitsTransition to maintenance Involve during iterationsProject team on one location Prevent communication
gapsUse project wall / dashboard Facilitates discussions
Agenda
Intro
Backgro
und
Projec
t
Approa
c
h Expe
rience
s
Lesson
s Lea
rned
Closure
Key take a ways
• Scrum is a process, Smart is complementary and offers techniques in addition
• A good, flexible architecture is precondition for a high speed start
• The product owner is key role to success• Manage fear for changes, both within team as within
environment• Facilitate the team to collaborate • Agile / SOA / SAP project: Think in services, focus on
processes, deliver in iterations
39Agile SAP: Mission Impossible
Contact
40Agile SAP: Mission Impossible
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
I : www.ciber.nl
twanvdbroek.blogspot.com
So, Agile is not only working within the SAP world
…
It will change doing SAP
projects
More …
• ESME: anatomy of a community based project https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/10758Dennis Howlett
• What is Scrum?http://www.scrumalliance.org/learn_about_scrum Scrum alliance
• SAP Scrum: An agile approach to deliver what is really requiredhttps://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13378Twan van den Broek
• Agile SAP: Mission Impossible?https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14973Twan van den Broek
• Is ASAP the best we can do now?https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13745Vijay Vijayasankar
• Iterations in Smarthttp://www.smartusecase.com/SmartLifecycle.ashx Sander Hoogendoorn
41Agile SAP: Mission Impossible