november, 2009 i xp days germany, karlsruhe · agile product management @ sap november, 2009 i xp...

22
Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

Upload: others

Post on 19-Jul-2020

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

AgileProduct Management@ SAPNovember, 2009 I XP DAYS GERMANY, Karlsruhe

Christian SchmidkonzChief Development Architect, SAP AG

Page 2: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 2

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 3: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 3

PRODUCT PORTFOLIO LAYER(1 corporate product portfolio)

Product Portfolio ManagementP2PPP

OPTIMIZEDEFINE DEVELOPINVENT DEPLOY

Highest PrioPortfolio Cases

PortfolioIterative Planning

1. ______2. ______3. ______4. ______

Portfolio Case Backlog___________________________________________________________________

Business CaseProduct VisionFeature Plan….

To be analyzedTo be detailedTo be verified

Portfolio

Product Definitionper Portfolio Case

Page 4: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 4

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 5: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 5

Product IdeaMotivationBusiness ValueTargetsRough Scope

Product DefinitionProduct Vision

Page 6: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 6

Approx. 3-20 “Features”Approx. 200 to 2.000 pd’sE.g. Epics, XL Use Cases,XXL Requirements,HL Scenarios

Product Definition“Feature Plan”

Page 7: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 7

Product DefinitionProduct and Release Backlog

Market/Customer InputUCDRelease BacklogHigh Level ArchitectureStakeholder/Management

Release Backlog = Scope1. ______2. ______3. ______4. ______5. _____6. _____7. _____8. _____9. _____10. _____11. ______12. ______13. ______14. _____15. ______16. ______

......Future Release_____________________________________________________

Product Backlog

Page 8: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 8

Product DefinitionRelease Backlog

Release Backlog = Scope1. ______2. ______3. ______4. ______5. _____6. _____7. _____8. _____9. _____10. _____11. ______12. ______13. ______14. _____15. ______16. ______

......Future Release_____________________________________________________

Product Backlog

Approx. 20 to 50pd‘sPrioritizedEstimatedE.g. Themes, UseCases, Scenarios,XL RequirementsTo be completedin releaseschedule

User Interface

Business Logic

Database

X

X

X

Page 9: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 9

With Dev TeamBreakdownDefinition of DONEPre-EstimateRough Design

Product DefinitionDetailed Product Backlog for Sprint

Release Backlog = Scope1. ______2. ______3. ______4. ______5. _____6. _____7. _____8. _____9. _____10. _____11. ______12. ______13. ______14. _____15. ______16. ______

......Future Release_____________________________________________________

Product Backlog

Approx. 20 to 50pd‘sPrioritizedEstimatedE.g. Themes, UseCases, Scenarios,XL Requirements

PrioritizedEstimatedTo be completed in 1 SprintE.g. User Stories, smallUse Cases, Requirements

Page 10: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 10

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 11: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 11

Product DevelopmentScrum Process Flow

Sprint

SprintReview

SprintPlanning

SprintRetrospective

Feedback/Info on requestBacklog to zeroBacklog preparation, BreakdownAcceptance, DONEMarket/Customer, Stakeholder

Page 12: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 12

Release Burndown by theend of each SprintClear Product StatusVelocity & ForecastRisk Management

Product DevelopmentRelease Burndown

0

200

400

600

800

1000

Start Sprint1

Sprint2

Sprint3

Sprint4

Sprint5

Sprint6

Sprint7

Sprint8

Scope - Target for Release\Project =Prioritized High Level Backlog

DeferredTarget Release\

project Date

Person Days or“Story Points”Release Backlog = Scope

1. ______2. ______3. ______4. ______5. _____6. _____7. _____8. _____9. _____10. _____11. ______12. ______13. ______14. _____15. ______16. ______

......Future Release_____________________________________________________

Product Backlog

Page 13: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 13

Product DevelopmentScaling Scrum

Product-Team

Scrum Master

Info Dev

Development

Q-Management

Production

Product Owner

ProductOwner

ProductOwner

ProductOwner

ProductOwner

Potentially ShippableProduct Increment

Page 14: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 14

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 15: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 15

PRODUCT PORTFOLIO LAYER(1 corporate product portfolio)

Product Portfolio ManagementP2PPP

Go To Market

OPTIMIZEDEFINE DEVELOPINVENT DEPLOY

Program ManagementPROGRAM LAYER(100+ concurrentprograms)

Agile ProductManagement

Validation Ramp-UpP2RTest

Maintenance

D2T

D2IMS

EoRD2T TestD2T D2PProduct

DefinitionArchitecture

Definition

P2D

Long-Term ResponsibilityKnowledge TransferMarket Input/AdoptionNext Release

Page 16: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 16

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 17: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 17

A Strong Product Owner

Reflecting Customers and Users voiceFrequent input and reviews with CustomersIn alignment with Stakeholders and ManagementOptimized on Customer/ Business Value andProfitability

Release BacklogPlanning Poker for Business ValuePrioritization Methodology (e.g. Kano, ..)Continuously updatedRelease Burndown including a Forecast (Velocity)Risk Management

A Conception of a High Level RoadmapA Product Vision and Product Backlog

Sufficient time for project (full-time)Exclusive time for the teamIntermediate Checks with Teams (on request)Offers a Consultation-Hour

Time for his Scrum Team

More coarse granularity for faraway itemsSufficient detail for near time itemsSprint PreparationBacklog Breakdown with TeamUser StoriesDONE and Acceptance Criteria (REQ)

An up to date Product Backlog

A Strong Product Ownerhas…

Page 18: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 18

Agenda

1. Portfolio2. Product Definition3. Product Development4. Go To Market5. A Strong Product Owner6. Scrum in the Context of Lean

Page 19: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 19

Scrum in the Context of Lean

Scope

Con

cret

enes

s

Scrum is an implementation of theagile development methods:an open development framework with clear roledefinitions, a very simple process model and a clearset of rules.

Page 20: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 20

Scrum in the Context of LeanAs Implementation of Lean on Team Level

Lean Scrum

FlowBacklog Items/TasksFocused working, task centric, 100% assignment to projectProduct Creation Process Map

TaktScrum Iterations/SprintsDaily Scrum

Pull

Prioritized Backlog at all timeTeam pulls Backlog according the capacity for the next sprintWork commitmentTasks are pulled by team

Zero Defects

Usable software after each sprint (takt)Done criteriaContinuous integrationQuality control in team

ContinuousImprovement

RetrospectivesBlock list

Page 21: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 21

Thank you!

Christian SchmidkonzAgile Center of Expertise

Dietmar-Hopp-Allee 1669190 Walldorf

[email protected]

Page 22: November, 2009 I XP DAYS GERMANY, Karlsruhe · Agile Product Management @ SAP November, 2009 I XP DAYS GERMANY, Karlsruhe Christian Schmidkonz Chief Development Architect, SAP AG

© SAP 2009 Agile Product Management @ SAP/ Page 22

Copyright 2009 SAP AGAll 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 AG. The information contained hereinmay 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logosare trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construedas constituting an additional warrant.