Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
Agile Pilot
Questions
Development Challenges@SAPProduct Innovation Lifecycle -Introduction
Agile Pilot
Questions
DevelopmentChallenges@SAP
Product Innovation Lifecycle -Introduction
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 4
USA FranceIsrael
BulgariaChina
Japan
India
Canada Germany
SAP Corporate Profile – Facts & Figures
SAP AG*)35.000+ employeesPresence in 50+ countries32.000 customers100.000+ installations12 million users in 120+ countries€ 8,513 billion revenue in 2005
Development Locations
*) data as of March 2006
Hungary
Products/Solutions150+ Products and 40+ SolutionsMore than 25 Industry Solutionsthereof30+ languages supportedApprox. 500 developers work in parallel on a new release of a solution
Agile Pilot
Questions
DevelopmentChallenges@SAP
Product Innovation Lifecycle –Introduction
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 6
Product Innovation Lifecycle (PIL): Overview
Invent Define Develop Deploy Optimize
Solution Management
Portfolio ManagementPh
ases
Management of Internal Controls
Decision to Define
QualifiedOpportunities
Phas
e Tr
ansi
tions
Market Strategy
IndustryStrategy
ApplicationStrategy
Opportunity Prioritization
Proc
esse
s
Decision to Develop
Develop-ment
Contract
Requirements Definition
Architecture Definition
High Level Planning
Decision to Deploy
SAP-validated Product
Detailed Planning
Implementation & Unit Test
Integration & Acceptance
Test
Detailed Design
Assembly &Validation
Decision to Volume Ship
Market-validated Product
Ramp-up Planning
Knowledge Transfer
PhasedRamp-up
Decision toRe-Invent
Market acceptedProduct
Correction & Change
Staged Release Transition
Product Transition
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 7
How Agile & PIL (Product Innovation Lifecycle) Match
Invent Define Develop Deploy Optimize
Pro
ject
Exe
cuti
on
Classical –Phase-Driven
Scrum – Agile Development
Agile Pilot
Questions
DevelopmentChallenges@SAP
Product Innovation Lifecycle -Introduction
Agile PilotBasicsScrum@SAPResultsKey Concepts
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 10
Agile Pilot – Basics
PilotSchedule October 2005 to October 2006
Motivation Agile Benefits… „faster, better, cheaper“!?
KeyTargets
Evaluate how to do Scrum@SAPSupport min. 10 projectsMin. 3 different locationsMin. 3 different development areasBuild SAP Scrum knowledgeFirst process draft (PIL)
SuccessMeasures
Project business goals are met in timeTeam members love to do itManagement is satisfied with results
Set-upExternal TrainersSAP Scrum Coach + Scrum Training
SAP ScrumRules
Max. 2 Project Locations Teams with max. 15 PersonsNO high risk ProjectsAll Team membersmust have participatedin the Scrum trainingbeforehand
Scrum commitments– Do Scrum as proposed
by methodology for at least 3 Sprints
– Stick to Scrum roles– All SAP Standards are
still valid(e.g. legal, reporting ..)
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 11
Agile Pilot – Scrum@SAP
ApprovedBusiness Case
Scrum Process Flow
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 12
Agile Pilot – Scrum@SAP
40+ Projects since November 2005at 7 Development Locations
FranceRa‘anna
Sofia China
Japan
Walldorf Budapest
Bangalore
TorontoLA
5 SAPDevelopmentAreas:
October 2006(finished)
ERPSuite
Optimization
IndustrySolutions
Scrum@SAP Pilot Status
Netweaver
SmallBusinessSolutions
~9 single-site
projects
WalldorfRa‘annaBudapestTorontoSofia
Walldorf-BudapestWalldorf-BangaloreWalldorf-SofiaWalldorf-MontrealWalldorf-MinskLA-Karmiel-WalldorfBangalore-Ra‘anna-Walldorf
~32 multi-site
projects
Montreal
37+ (>90%) Projectswere
(very) successful
4 Projects (<10%) stopped (Scrum) …
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 13
Agile Pilot – Scrum@SAP
Enhanced SAP Scrum best practices
Commitments
Project preparation and set-up as usual
Team
Product Owner
Scrum Master
Stakeholders
SAP Standards
Product Backlog
Sprint Backlog
IncrementalDevelopment
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 14
ScrumMaster
“Classic I”Product
Owner
Team(<=16)
Agile Pilot – Scrum@SAP Project Variants
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 15
Team(<=16)
Team(<=16)
Team(<=16)
Agile Pilot – Scrum@SAP Variants
Scrumof
Scrum
“Classic II”ScrumMaster
ProductOwner
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 16
Agile Pilot – Scrum@SAP Variants
ScrumMaster
ProductOwner
“Classic III - combi”
Team(<=16)
One Person =
+
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 17
Team IV Bangalore+WalldorfTeam II Walldorf
Team I Walldorf
Agile Pilot – Scrum@SAP Variants
“BIG I”
Team V Bangalore
Team IIIBangalore+Walldorf
OverallScrumMaster
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 18
“BIG II”
Agile Pilot – Scrum@SAP Variants
TeamIRa’anna TeamVBangalore
TeamIIRa’anna
Team III Walldorf
TeamVIBangalore
Scrum of Scrum
OverallScrumMaster
5ProductOwner
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 19
Agile Pilot – Results
SAP Scrum Benefits
on Project StatusIssues and problems became visible very earlyClear Status for all
Scrum Improvements for Projects
Transparency Communication
Benefits lead to an unexpected high number ofScrum Pilot Projects
of all actors in theprocess
Solution Management and DevelopmentOne Product Owner per teamStakeholders in Sprint Review
increased for mostPilot Projects
High Team motivationSome Teams finished Sprints earlierMost Teams delivered earlier more than was expected
Productivity
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 20
Scrum Learnings
Agile Pilot – Results
SAP-specific adoptions for Scrum (PIL)
Strong key roles
SAP Scrum Rules are key
Team experience +
Team size
Change Management
Product OwnerTraining
Adoption to Agile takes
time …
CommonSAP Scrum „message“
Some keep falling backto old habitsSAP Scrum Coach is key
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 21
Keep roles, responsibility, discipline and trustScrum set-up for biggerprojectsA good Product BacklogEstablish a Team learningcultureIntercultural topics
Scrum Challenges
Agile Pilot – Results
Training
Retro-spectives
CoachingCoachingCoaching
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 22
Agile Pilot – Results
Scrum Pilot Results
Scrum@SAP from 2007 onScrum is part of PILScrum will be an optionSAP Scrum Key ConceptsAgile plans:Scrum@SAP + XP
3 Development Areas decided toexpand Scrum extensively in 2007
Scrum Pilot already changed to anintroduction of Scrum
40+ Pilot Projects at7 SAP Development Locations
500+ trained Scrum Practitioners
Key Targets and SuccessMeasures are met
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 23
3Coaching …
Info Session + Discussion
Common Agreement and Commitment
Training + Coaching
SAP Scrum Key Concepts
Scrum BasicsAdvanced Scrum Master
TechniquesProduct Owner Excellence
Diversity/Intercultural
1Preparation forAgile
2Agile Trainingfor all Roles
Coach = Scrum Master Original Scrum Master takes over
Coach steps outFinal Project Retrospective
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 24
Local Scrum Coaches
SAP Scrum Key Concepts
France1Ra‘anna
1-2Sofia
China
Japan
1-2Montreal3-5Walldorf
1-2Budapest
2-3Bangalore
LA+Toronto
Enable Locations
Ensure Local Project Support
Education for Local Coaches
Tasks are tobuild local communitiesdo local training + coachingenhance local knowledge andexpertiseact as contact for the world-wide Agile SAPNetwork
Agile Pilot
Questions
Development Challenges @ SAP
Product Innovation Lifecycle - Introduction
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 26
THANK YOU FOR YOURATTENTION !
QUESTIONS – SUGGESTIONS – DISCUSSION
Christian [email protected]
© SAP AG 2006, XP days 2006/ AgileDevelopment@SAP/ Christian Schmidkonz/ 27
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.
Copyright 2006 SAP AG. All Rights Reserved