Your SlideShare is downloading. ×
20100220 Sit Bonn V1 0
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

20100220 Sit Bonn V1 0

1,142

Published on

Agile SAP: Mission Impossible? Real life story on first agile SAP project in Netherlands.

Agile SAP: Mission Impossible? Real life story on first agile SAP project in Netherlands.

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,142
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
69
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile SAP: Mission Impossible? SAP Inside Track Bonn Twan van den Broek February 20, 2010
  • 2. 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 SIT Bonn / Agile SAP: Mission Impossible? 2
  • 3. Why are we here? Intro Why are we here? Agile? How to start? A day at the office Experiences Arrival SIT Bonn / Agile SAP: Mission Impossible? 3
  • 4. ASAP project approach 4
  • 5. Waterfalls didn’t help s design review s ues: bu siness due to r fall is during ok lon g Wate ussions e signs to s of disc on s of d n team - Lot inal ver si e alizati o De l ivery f ‘give n’ to r f design - pr essure ’v ers ions o ctivitie s - Time ‘illegal te sting a rk ing on ra tion of t he tea m - Wo t prepa within fficien p focus - No e to kee difficult - Very SIT Bonn / Agile SAP: Mission Impossible? 5
  • 6. Agile? Intro Why are we here? Agile? How to start? A day at the office Experiences Arrival SIT Bonn / Agile SAP: Mission Impossible? 6
  • 7. 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 SIT Bonn / Agile SAP: Mission Impossible? 8
  • 8. What is Scrum? SIT Bonn / Agile SAP: Mission Impossible? 9
  • 9. '()*+,-#(&./)$&0+122/3/#$34+.)+567/$#77+!"/0/.4+ Deliver Competitive Advantage with a Business Process Platform Business Agility 8 Operational Efficiency Business Process Reengineering Business Network Transformation Enterprise Resource Planning Business Process Platform 1990s 2000s 2010s © SAP AG 2009. All rights reserved. / Page 4
  • 10. 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” SIT Bonn / Agile SAP: Mission Impossible? 11
  • 11. Smart use cases? www.smartusecase.com SIT Bonn / Agile SAP: Mission Impossible? 12
  • 12. What is smart? Create Round up project software proposal Propose Scope Realize Realize Realize Realize Finalize Manage Deliver Write Maintain working project plan software software Smart: Sander Hoogendoorn, Principal Technology Officer, Capgemini SIT Bonn / Agile SAP: Mission Impossible? 13
  • 13. Smart iterations What product(s) do we want to deliver? Are we up to Plan speed? Define done Is our process optimal? Are the product(s) done? Propose Scope Realize Realize Realize Realize Finalize Manage Build Evaluate Deliver product(s) using product cycle Visualise progress SIT Bonn / Agile SAP: Mission Impossible? 14
  • 14. How to start? Intro Why are we here? Agile? How to start? A day at the office Experiences Arrival SIT Bonn / Agile SAP: Mission Impossible? 15
  • 15. 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 SIT Bonn / Agile SAP: Mission Impossible? 16
  • 16. Design together with business
  • 17. Modeling smart use cases
  • 18. Estimating smart use cases
  • 19. Product Backlog SIT Bonn / Agile SAP: Mission Impossible? 21
  • 20. Determine velocity
  • 21. A day at the office Intro Why are we here? Agile? How to start? A day at the office Experiences Arrival SIT Bonn / Agile SAP: Mission Impossible? 23
  • 22. Daily scrum meeting
  • 23. Project wall with dashboard Dashboard to track single smart use cases Project pie chart How many points How far are we? realized per iteration Done / Total How many points realized on daily basis Burn down chart 25
  • 24. Pair programming/ customizing
  • 25. Project Burn down chart SIT Bonn / Agile SAP: Mission Impossible? 27
  • 26. Project statistics /2 SIT Bonn / Agile SAP: Mission Impossible? 28
  • 27. Pair testing
  • 28. Demo end of each iteration
  • 29. Evaluate
  • 30. Experiences Intro Why are we here? Agile? How to start? A day at the office Experiences Arrival SIT Bonn / Agile SAP: Mission Impossible? 32
  • 31. Lessons learned Key take aways • 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 SIT Bonn / Agile SAP: Mission Impossible? 33
  • 32. Experiences agile SAP Key take aways • 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 SIT Bonn / Agile SAP: Mission Impossible? 34
  • 33. Tips to apply agile SAP within your project Key take aways • 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 SIT Bonn / Agile SAP: Mission Impossible? 35
  • 34. Enthusiastic on project and approach
  • 35. Questions? e k Bro d en n van Twa V dB rlan ede 15 RN CIBE olklaan rk Mee us 843 dhoven tb Pos AV Ein 952 5600 29 735 90 0)6 2 90 l + 31 ( )40 23 90 91 ciber.n M : 31 (0 0 232 oek@ + 4 r T : 31 (0) .den.b om F : + n.van nl ot.c twa .ciber. .blogsp E : ww k w broe k I : wanvd @tbroe t : ter Tw i t SIT Bonn / Agile SAP: Mission Impossible? 37

×