Agile SAP: Mission Impossible?<br />Twan van den Broek<br />SAP SDN VirtualCommunityDay<br />24 September 2009<br />
Intro<br />Twan van den BroekPrincipal Consultant CIBER NLScrum master@tbroek“Agile can not work within the SAP world”<br ...
Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />4<br ...
GammamijnNS / Refund<br />NS.nl<br />RTS<br />Balie<br />Balie<br />Automaat<br />ccInternet<br />ccOVCP<br />SAP<br /> CR...
Solution Architecture in 5 layers<br />6<br />Agile SAP: Mission Impossible<br />
Plotting SAP solutions in Solution Architecture<br />ccBPM<br />XI<br />CRM<br />R/3<br />7<br />Agile SAP: Mission Imposs...
Agenda<br />Agile SAP: Mission Impossible<br />8<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />...
Project phases<br />Phase n<br />Extend functionality/ travel products<br />oct09-dec10<br />Oct 09<br />Phase 2<br />Prep...
Project waterfalls<br />Waterfall issues:<br /><ul><li>Lots of discussions during business design</li></ul>- Delivery fina...
 Working on ‘illegal’ versions of design
No efficient preparation of testing activities
Very difficult to keep focus within the team</li></ul>10<br />Agile SAP: Mission Impossible<br />
Waterfall according to Dr. Winston W. Royce (1970)<br />11<br />Agile SAP: Mission Impossible<br />
But we seem to forget the way back<br />12<br />Agile SAP: Mission Impossible<br />
ASAP Project approach<br />13<br />Agile SAP: Mission Impossible<br />
Agenda<br />Agile SAP: Mission Impossible<br />14<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br /...
Project approach<br />Goals different approach<br />- Team focus on solution<br />- Deal with changing insights and priori...
What is Scrum?<br />16<br />Agile SAP: Mission Impossible<br />
Scrum process<br />Final delivery<br />Delivery<br />Sprint/Iteration 2<br />Delivery<br />Sprint/Iteration 1<br />Analyze...
Smart software life cycle<br />18<br />Agile SAP: Mission Impossible<br />
Smart<br />Smart Use Cases<br />YAGNI, Agile requirements<br />Identifying smart use cases<br />Modeling smart use cases<b...
Teaming the project<br />Product owner<br />Responsible for gathering all business requirements <br />Difficulty: No ‘real...
Designing together with business<br />
Modeling smart use cases<br />
Estimating smart use cases<br />
Product Backlog<br />Agile SAP: Mission Impossible<br />25<br />
Project wall with dashboard<br />26<br />Agile SAP: Mission Impossible<br />
Daily scrum meeting<br />
Agile SAP: Mission Impossible<br />28<br />Demo and review to conclude every sprint<br />
Acceptance test<br />
Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
Project Burn down chart<br />31<br />Agile SAP: Mission Impossible<br />
Project statistics<br />Agile SAP: Mission Impossible<br />32<br />
Project statistics /2<br />Agile SAP: Mission Impossible<br />33<br />
Experiences<br />High speed project<br />Day to day focus on scope <br />Connecting roles and teams<br />Change management...
Enthusiastic on project and approach<br />
Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
Lessons learned<br />Realistic scope for sprint backlog	Too much will discourage team<br />Focus team on delivery 	Prevent...
Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
Upcoming SlideShare
Loading in …5
×

20090924 Agile Sap Sdn Vcd09 V1.0

1,657 views

Published on

Approach and experiences of the first Agile SAP project in the Netherlands where SAP, Scrum and Smart go hand in hand together.

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,657
On SlideShare
0
From Embeds
0
Number of Embeds
245
Actions
Shares
0
Downloads
6
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

20090924 Agile Sap Sdn Vcd09 V1.0

  1. 1. Agile SAP: Mission Impossible?<br />Twan van den Broek<br />SAP SDN VirtualCommunityDay<br />24 September 2009<br />
  2. 2.
  3. 3. Intro<br />Twan van den BroekPrincipal Consultant CIBER NLScrum master@tbroek“Agile can not work within the SAP world”<br />(Sander Hoogendoorn)Principal Technology Officer Capgemini and Agile evangelistAgile Coach@aahoogendoornAuthor<br />A.C.W. van den Broek<br />3<br />Agile SAP: Mission Impossible<br />
  4. 4. Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />4<br />Agile SAP: Mission Impossible<br />
  5. 5. GammamijnNS / Refund<br />NS.nl<br />RTS<br />Balie<br />Balie<br />Automaat<br />ccInternet<br />ccOVCP<br />SAP<br /> CRM<br />VCM<br />CECURE<br />R/3<br />Finance Center<br />ccKlantsystemen<br />TLS<br />ccTicketing<br />SAP XI<br />LocAL<br /> BOM<br /> LDM<br />Automaat<br />NS<br />L2EPS<br />L3CPS<br />ETDS<br />Amersfoort<br />CardInformationService<br />Engraved IDChip IDConversie<br />L4CCHS<br />TLS<br />System landscape<br />5<br />Agile SAP: Mission Impossible<br />
  6. 6. Solution Architecture in 5 layers<br />6<br />Agile SAP: Mission Impossible<br />
  7. 7. Plotting SAP solutions in Solution Architecture<br />ccBPM<br />XI<br />CRM<br />R/3<br />7<br />Agile SAP: Mission Impossible<br />
  8. 8. Agenda<br />Agile SAP: Mission Impossible<br />8<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />Goal<br />Phases<br />Architecture<br />
  9. 9. Project phases<br />Phase n<br />Extend functionality/ travel products<br />oct09-dec10<br />Oct 09<br />Phase 2<br />Prepare country wide roll out<br />feb09-sept09<br />Feb 09<br />Sept 08<br />Phase 1<br />Settle basis<br />sept08-feb09<br />9<br />Agile SAP: Mission Impossible<br />
  10. 10. Project waterfalls<br />Waterfall issues:<br /><ul><li>Lots of discussions during business design</li></ul>- Delivery final versions of designs took long due to reviews<br /><ul><li> Time pressure ‘given’ to realization team
  11. 11. Working on ‘illegal’ versions of design
  12. 12. No efficient preparation of testing activities
  13. 13. Very difficult to keep focus within the team</li></ul>10<br />Agile SAP: Mission Impossible<br />
  14. 14. Waterfall according to Dr. Winston W. Royce (1970)<br />11<br />Agile SAP: Mission Impossible<br />
  15. 15. But we seem to forget the way back<br />12<br />Agile SAP: Mission Impossible<br />
  16. 16. ASAP Project approach<br />13<br />Agile SAP: Mission Impossible<br />
  17. 17. Agenda<br />Agile SAP: Mission Impossible<br />14<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />Why differently<br />Planning<br />Smart / Scrum<br />Project team<br />
  18. 18. Project approach<br />Goals different approach<br />- Team focus on solution<br />- Deal with changing insights and priorities<br />- Delivery in iterations<br />- Involve environment (Business, BA&A) in design and demo’s<br />15<br />Agile SAP: Mission Impossible<br />
  19. 19. What is Scrum?<br />16<br />Agile SAP: Mission Impossible<br />
  20. 20. Scrum process<br />Final delivery<br />Delivery<br />Sprint/Iteration 2<br />Delivery<br />Sprint/Iteration 1<br />Analyze<br />Analyze<br />Analyze<br />Realize<br />Specify<br />Realize<br />Realize<br />Specify<br />Specify<br />Accept<br />Accept<br />Accept<br />Test<br />Test<br />Test<br />Sprint 1<br />Sprint 2<br />Sprint 3<br />Product BacklogList with highlevel<br />requirements<br />Expected product<br />17<br />Agile SAP: Mission Impossible<br />
  21. 21. Smart software life cycle<br />18<br />Agile SAP: Mission Impossible<br />
  22. 22. Smart<br />Smart Use Cases<br />YAGNI, Agile requirements<br />Identifying smart use cases<br />Modeling smart use cases<br />Modeling services to smart use cases<br />Smart estimation<br />Smart use case stereotypes<br />Smart estimation poker<br />19<br />Agile SAP: Mission Impossible<br />
  23. 23. Teaming the project<br />Product owner<br />Responsible for gathering all business requirements <br />Difficulty: No ‘real’ business owner<br />Scrum team<br />Business analyst /2<br />Information analyst /1,5<br />SAP CRM /1<br />SAP XI/ BPM /2<br />SAP ABAP /1<br />.NET developer /1<br />Test /2<br />20<br />Agile SAP: Mission Impossible<br />
  24. 24. Designing together with business<br />
  25. 25. Modeling smart use cases<br />
  26. 26. Estimating smart use cases<br />
  27. 27.
  28. 28. Product Backlog<br />Agile SAP: Mission Impossible<br />25<br />
  29. 29. Project wall with dashboard<br />26<br />Agile SAP: Mission Impossible<br />
  30. 30. Daily scrum meeting<br />
  31. 31. Agile SAP: Mission Impossible<br />28<br />Demo and review to conclude every sprint<br />
  32. 32. Acceptance test<br />
  33. 33. Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
  34. 34. Project Burn down chart<br />31<br />Agile SAP: Mission Impossible<br />
  35. 35. Project statistics<br />Agile SAP: Mission Impossible<br />32<br />
  36. 36. Project statistics /2<br />Agile SAP: Mission Impossible<br />33<br />
  37. 37. Experiences<br />High speed project<br />Day to day focus on scope <br />Connecting roles and teams<br />Change management in and outside, “Agile will not work in the SAP world”<br />Skeptical attitude turned into faith towards end<br />“Just do it” approach<br />Documentation is up to date<br />Very agile to changing requirements<br />Planning insight<br />Discussions on priorities in stead of deadlines<br />34<br />Agile SAP: Mission Impossible<br />
  38. 38. Enthusiastic on project and approach<br />
  39. 39. Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
  40. 40. Lessons learned<br />Realistic scope for sprint backlog Too much will discourage team<br />Focus team on delivery Prevent busy with everything<br />Involve project environment Prevent reviews afterwards<br />Be firm in following approach Prevent to catch up old habits<br />Transition to maintenance Involve during iterations<br />Project team on onelocation Prevent communication gaps<br />Use project wall/ dashboard Facilitates discussions<br />37<br />Agile SAP: Mission Impossible<br />
  41. 41. Agenda<br />Lessons Learned<br />Experiences<br />Background<br />Approach<br />Project<br />Closure<br />Intro<br />
  42. 42. Key take a ways<br />Scrum is a process, Smart is complementary and offers techniques in addition<br />A good, flexible architecture is precondition for a high speed start<br />The product owner is key role to success<br />Manage fear for changes, both within team as within environment<br />Facilitate the team to collaborate<br />Agile / SOA / SAP project: Think in services, focus on processes, deliver in iterations<br />39<br />Agile SAP: Mission Impossible<br />
  43. 43. Contact<br />Agile SAP: Mission Impossible<br />Twan van den Broek<br />CIBER Nederland BV<br />Meerkolklaan 15<br />Postbus 843<br />5600 AV Eindhoven<br />M : +31 (0)6 29 735 952<br />T : +31 (0)40 232 90 90<br />F : +31 (0)40 232 90 91<br />E : twan.van.den.broek@ciber.nl<br />I : www.ciber.nl<br />twanvdbroek.blogspot.com<br />So, Agile is not only working within the SAP world …<br />It will change doing SAP projects <br />40<br />
  44. 44. More …<br />ESME: anatomy of a community based project https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/10758Dennis Howlett<br />What is Scrum?http://www.scrumalliance.org/learn_about_scrumScrum alliance<br />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<br />Agile SAP: Mission Impossible?https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14973Twan van den Broek<br />Is ASAP the best we can do now?https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13745Vijay Vijayasankar<br />Iterations in Smarthttp://www.smartusecase.com/SmartLifecycle.ashxSander Hoogendoorn<br />41<br />Agile SAP: Mission Impossible<br />

×