Erfolgsfaktoren für die agile Software Entwicklung im Vertragsumfeld Vorstellung eines SAP Standard Co-Innovations Projektansatzes (SCDP*), das agile Methoden und traditionelles Wasserfall Modell verbindet Roland Kreß, SAP SE Nov 10 th, 2015 *: Strategic Customer Development Project
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 2
Motivation Status Quo Agile Seit 2010 kommt SCRUM als agile Methode bei der Standard SW Entwicklung zum Einsatz Source: Status Quo Agile Studie zu Verbreitung und Nutzen agiler Methoden Durchgeführt 2014 von der GPM Deutsche Gesellschaft für Projektmanagement e.v. in Kooperation mit der Hochschule Koblenz http://www.hs-koblenz.de/rmc/fachbereiche/wirtschaft/forschungprojekte/forschungsprojekte/status-quo-agile/ 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 3
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 4
Starting Point: Co-Innovation Projects with SAP Standard Development Dim 1: Type of co-innovation Project Research/Invent 1:1 Co-Develop Development Dim 2: Degree of Intensity Information Level Review Level Collaboration Level Dim 3: Level of Commitment SAP presenting strategies, roadmaps and schedules to Customer / Customer is sharing concepts, requirements etc. SAP providing concepts, prototypes, UI s and final developments for Customer review/feedback SAP & Customer are strong interacting during the whole DEV live cycle of a standard release Without legal binding DEV Commitment (FBA*) on Release Level on Topic Level on Requirement Level (Backlog) Potential Customer interaction during a co-innovation with SAP Offer Site visits Provide Input e.g. Concepts, Process descriptions, Best Practices, UI s,.. Review Architecture, High Level Designs and Prototypes, UI s Join DEV Sprint reviews Participate in SAP testing Validate the Solution Implement the Solution Serve as a Reference With DEV Commitment (SCDP Contract) *: Feedback Agreement 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 5
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 6
SCDP Methodology Transition Waterfall -> Agile Approach Software Delivery Evaluation Evaluation Contract Negotiation Development & Test Specification Design Realization Test Customer Acceptance and Delivery Customer Acceptance Component Validation / Assembly Project Life cycle High Level Scope Review and Approval Review Spec Review Design Code Review Unit/Module Test SAP SAT/SIT Customer AT Installation Checks Reviews & Checks Customer Sign Off SOW Sign-off Specification Sign-off Change Requests Software Acceptance Sign-off Final Acceptance 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 7
SCDP Methodology Transition Waterfall -> Agile Approach Product Definition Software Delivery Evaluation Evaluation Contract Negotiation Development & Test PDEF Contract Specification Backlog Design Realization Test Customer Acceptance and Delivery Customer Acceptance Component Validation / Assembly Project Life cycle High Level Scope Viable Scope Review and Approval Review Backlog Spec Review Design Code Review Unit/Module Test SAP SAT/SIT Customer AT Installation Checks Reviews & Checks Customer Sign Off SOW Sign-off Specification Backlog Sign-off Change Requests Software Acceptance Sign-off Final Acceptance 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 8
SCDP Methodology Transition Waterfall -> Agile Approach Product Definition Software Delivery Evaluation Evaluation Contract Negotiation Development & Test PDEF Contract Realization in Specification Design Realization Backlog Sprints Test Customer Acceptance and Delivery Customer Acceptance Component Validation / Assembly Project Life cycle High Level Scope Viable Scope Review and Approval Review Backlog Spec Sprint Review Planning Code (+ HL Review Design) Sprint Design Reviews Unit/Module SAP+Custom. Test SAP SAT/SIT Customer AT Installation Checks Reviews & Checks Customer Sign Off SOW Sign-off Specification Backlog Sign-off Change Requests Software Acceptance Sign-off Final Acceptance 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 9
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 10
Evaluation Phase Evaluation & Contract Set-Up Mandatory Required: Board Approval Quote from SAP S Customer Commitment Homepage: Every customer commitment beyond SAP s standard offering is an exception, and requires approval by the SAP Executive Board High Level Scope -> Details on next slide(s) Planned Schedule -> Details on next slide(s) Payment Terms Change Request Process Business Case Template for SCDP approval High Level Cost / Revenue Scheduling Risks Acceptance Procedure Governance & Engagement -> Details on next slide(s) Customer SAP Country 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 11
Evaluation Phase - Planned Schedules Go-Live DC Pilot EWM 9.0 DC Implementation EWM 9.2 RTC PWH Implementation Go-Live PWH Pilot ECC 6.0 EHP6 SP05 +notes 2013 2014 2015 ECC 6.0 EHP6 SP11 SP12 SP14 1.6.13 SCDP 11.11.14 timeframe Evaluation PDEF Realization CR s Accept. contingency EWM 9.2 Realization Test + Valid. 2013 2014 2015 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 12
Evaluation Phase - Planned Schedules Go-Live DC Pilot EWM 9.0 DC Implementation EWM 9.2 RTC PWH Implementation Go-Live PWH Pilot ECC 6.0 EHP6 SP05 +notes 2013 2014 2015 ECC 6.0 EHP6 SP11 SP12 SP14 1.6.13 SCDP 11.11.14 timeframe Evaluation PDEF Realization CR s Accept. contingency EWM 9.2 Realization Test + Valid. 2013 2014 2015 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 13
Evaluation Phase High Level Scope Starting Point: Business Requirement List Customer -> BR already covered -> No real BR -> Software Requirement - Standard worthy -> SCDP candidates - Customer specific Execution: 1. SAP Workshop(s) with Customer -> to agree on most important SW Req s -> to fix High Level Solution 2. High Level Effort Estimation on Net DEV Effort -> Input Cost Plan Framework Condition: Management Agreement to restrict DEV Scope to ~XXXX PD net DEV effort 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 14
Evaluation Phase Governance & Engagement Model The Governance Model to be defined on 3 Levels Board Level Senior Management Level Program/Project Management The SAP internal Engagement Model to be defined is consisting of 1 Delivery Program with few Customer facing roles 1-N supplying Development Areas with agile DEV organization behind Team- of- Ten 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 15
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 16
Product Definition Phase Product (=Contract) Backlog Output PDEF Phase Input PDEF Phase 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 17
Realization Phase Agile Development in Sprints 2013 Oct Nov. 2014 Dec. Jan. Feb. March April May June July EWM + ECC: Sprint 1 Sprint 2 15.12. DEV Close ECC DEV Close EWM Sprint 3 Sprint 4 24.2. EWM: Sprint 5 Planned realization end for SCDP Backlog Sprint 6 Sprint 7 Sprint 8 Sprint 9 28.4. Preparation. Sprint Planning SAP internal Planning of the next sprint by identifying Customer s Contract Backlog items to be realized in Sprint X No involvement of Customer SAP will inform the Customer about the the Sprint Planning result & potential changes later on Customer will be expected to prepare themselves for the Sprint Demo based on this information's Execution Sprint Execution SAP Development of the items identified in the Sprint Planning Requests for more detailed information out of the Scrum Teams have to be posted to Customer assigned team members Customer Team members are expected to respond in a timely manor No Customer involvement in the SAP internal Sprint Review meetings (Sprint Closing) Demo/Review Sprint Demo/Review After the SAP finalization of some Sprints a process demo per topic for Customer s Business/IT experts will be organized by SAP in order to get early Feedback on developments Required Major Adjustments have to be formalized & tracked via Change Requests Process Customer team members will be enabled to have hands-on SAP s test system to test the SCDP backlog items during the demo sessions 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 18
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 19
Test Phase Customer Acceptance Test - Process SAP creates internal Test Cases Initial TC s provided by SAP 1.4. Customer checks & finalizes TC s Finalized TC s provided by Customer 30.5. TC s accepted by SAP 15.6. SCDP Functions provided for Acceptance Test 11.8. 11.8. 22.8 5.9. Test WDF SCDP AT / Wave 1 Re-Test Emergency Correction. close EWM 12.9. 29.9. 12.10. SCDP AT / Wave 2 SCDP SW Acceptance 15.10. Software Delivery 11.11. SAP EWM internal Test Re-Test 5.7. 22.8. 12.9. System Switch Corrections implemented in SP01 Test Preparation Test Execution Test Follow-up SAP obligation Customer obligation 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 20
Topics Motivation Status Quo Agile Starting Point: Co-Innovation Projects with SAP Standard DEV SCDP Methodology: Transition Waterfall -> Agile Approach SCDP Project Phases Evaluation Contract Set-up Details on main Assets (G&E Model, High Level Scope, Schedule) Development & Test Product Definition Agile Development in Sprints Customer Acceptance & Delivery SCDP Success Factors 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 21
SCDP Success Factors Combined Methodology People DEV Content ERP EWM SAP Customer Contingency Hybrid Communication Roles Customer Funding G&E Model 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 22
Success Factor Trust and Confidence Quote Customer s team lead out of a SAP internal SCDP Success Story: The SCDP framework defines a strong, collaborative working model to support the power of working as a team and the development of trust and confidence in each other s organizations. It enables a WIN-WIN situation delivering Customers the solution they need and SAP with a standard solution for the market at large. Success Store on SAP Jam page: https://jam4.sapjam.com/blogs/show/qfr2r9w4lx5bcwo3emzbtf 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 23
Thank you Contact information: Roland Kreß, SAP SE Chief Project Expert - Development +49(0)160 360 3452 2015 SAP SE or an SAP affiliate company. All rights reserved.
2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 25
2015 SAP SE oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet. SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx. Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Produkte können länderspezifische Unterschiede aufweisen. Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informationszwecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren. Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden. Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen. 2015 SAP SE or an SAP affiliate company. All rights reserved. Strictly Confidential 26