1.
DistributedProduct Owner team @ SYNGOStrategies for growth, communication, and customer collaborationAndrea Heck, Scandinavian Developer Conference, March 2013© Siemens AG 2013 All rights reserved. Answers for life.

2.
Speaker Andrea Heck Agile Transition Lead & Agile Coach Dipl. Inf (Univ), CSM, CSPO, CSP Siemens AG Healthcare SYNGO Hartmannstr. 16 91052 Erlangen, Germany E-mail: andrea.heck@siemens.com Twitter: @AgileAndrea Blog: http://agileandrea.com/ Answers for life.Siemens AG 2013 All rights reserved.Page 2 2013-02-15 Andrea Heck / Healthcare SYNGO

3.
Some questions we will reflect on may help you, if……you are a manager, agile transition team member, or agile coach• Will a distributed Product Owner team work?• What do we have to invest into?• How can our Product Owner team communicate better?…you are a Product Owner• Do I have the necessary knowledge, contacts and tools?• Do I spend my time on the right things?• How can we get better at involving customers?• How can we self-organize in the Product Owner team to get more aligned?Siemens AG 2013 All rights reserved.Page 3 2013-02-15 Andrea Heck / Healthcare SYNGO

4.
Distributed Product Owner team @ SYNGO Customer collaboration Product Owner team communication Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 4 2013-02-15 Andrea Heck / Healthcare SYNGO

5.
Distributed Product Owner team @ SYNGO • Get the full picture – syngo.via • Medical product development • Product and modules PO team Customer • Large-scale distributed agile collaboration transition Product Owner team communication Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 5 2013-02-15 Andrea Heck / Healthcare SYNGO

6.
BackgroundGet the full picture.The syngo.via 3D routine andadvanced reading solution helps toaccelerate workflows across allmodalities, and is suitable for both day-to-day and more challenging cases.It is efficient: by helping save valuabletime, it allows physicians to focus ontheir core tasks.It is flexible: users can customizeapplications, layouts and workflows.And it is intelligent: it delivers powerfulimage reading, and guides usersthrough the entire workflow.Siemens AG 2013 All rights reserved.Page 6 2013-02-15 Andrea Heck / Healthcare SYNGO

7.
BackgroundMedical Software DevelopmentIt is special – many regulations need tobe considered.For our topic it is important that theproblem domain is different fromwhat developers have experience in.“My developers keep telling me: but ourusers must understand our logic! – It isvery hard for them to understand thedoctors have a different work context,and a totally different way of thinking.” (a Product Owner)Siemens AG 2013 All rights reserved.Page 7 2013-02-15 Andrea Heck / Healthcare SYNGO

8.
BackgroundOur product consists of Modules that represent certain feature areas, and can be re-used in syngo.via different products Apps using the modules that are created especially for syngo.via App AppSome of the syngo.via apps arecreated by SYNGO, others are createdby other Siemens Business Units whouse our modules and deliver theiradvanced application, e.g. a CT cardiac Module Module Moduleapp.Siemens AG 2013 All rights reserved.Page 8 2013-02-15 Andrea Heck / Healthcare SYNGO

9.
BackgroundWe have done the transition to agileof a large-scale distributeddevelopment organization Gradually from 2008 A complete rollout In 2010Goals Improve time to market Improve quality of delivered products Customer centered development Increase team productivity and motivationSiemens AG 2013 All rights reserved.Page 9 2013-02-15 Andrea Heck / Healthcare SYNGO

10.
BackgroundOur target structure is Collocated feature teams Still distributed to multiple sites Suppliers as partnersProduct Owner team needs totravel and get distributedSiemens AG 2013 All rights reserved.Page 10 2013-02-15 Andrea Heck / Healthcare SYNGO

11.
Distributed Product Owner team @ SYNGO • Background of Product Owners • Product Owner team structure • Knowledge PO team Customer • Skills collaboration • Investing into supplier Product Product Owner Owners team communication Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 11 2013-02-15 Andrea Heck / Healthcare SYNGO

12.
Growing a distributed Product Owner teamBackground of Product Owners – previous roles Product Manager Requirements Engineer From Product Management Software Developer department Radiologist System Tester Radiology Technician System Engineer From hospitalFrom R&D department Product OwnerSiemens AG 2013 All rights reserved.Page 12 2013-02-15 Andrea Heck / Healthcare SYNGO

13.
Growing a distributed Product Owner teamProduct Owner team structure Product Owner teamAt transition start: Chief Product Owner Project Lead LeadNearly the whole PO team was Architectcollocated in the headquartersMany POs have to travel frequently Module Product Module Product Module ProductTheir teams are at other sites Owner* Owner OwnerIdea:Grow more Product Owners at all sites Product Product Owner Owner *App or Module  Scrum TeamsSiemens AG 2013 All rights reserved.Page 13 2013-02-15 Andrea Heck / Healthcare SYNGO

14.
Growing a distributed Product Owner team Knowledge Medical knowledge Our product! Agile Product Management Workflows in hospital Stakeholders and interfaces within the organization Context of work of users Product Owner Role Usability Requirements EngineeringUser Stories Software development context Software Quality Process and Regulations Siemens AG 2013 All rights reserved. Page 14 2013-02-15 Andrea Heck / Healthcare SYNGO

15.
Growing a distributed Product Owner teamSkills High communication skills Lead without power Listen to customers Taking decisions Team Motivation Prioritization Presentation skills – clear, Coaching understandable, WIIFY Decide based on business value / customer value Know when you need to askSiemens AG 2013 All rights reserved.Page 15 2013-02-15 Andrea Heck / Healthcare SYNGO

16.
Growing a distributed Product Owner teamInvestment into Product Owners at suppliersWe have three successful models for Product Owners at supplier sites:1. Employ a Product Owner from external with excellent problem domain knowledge – in our case, radiologist, and teach SW development, agile, and our product2. Take a long years experienced person from a leading software development role, and teach Product Owner role, customer and business topics3. Ask an experienced Product Owner from headquarters to move (temporarily) to a siteSiemens AG 2013 All rights reserved.Page 16 2013-02-15 Andrea Heck / Healthcare SYNGO

17.
Growing a distributed Product Owner teamInvestment into Product Owners at suppliersShould we do this at all?Can we trust our suppliers not to steal the product and ideas? ?  An internal employee may also leave the company and join a competitor  A supplier contract may exclude later competition on the same fieldSiemens AG 2013 All rights reserved.Page 17 2013-02-15 Andrea Heck / Healthcare SYNGO

18.
Distributed Product Owner team @ SYNGO • Whole PO team • Core PO team • Roles in Scrum Team PO team Customer • Within the Module (App) – collaboration three different models Product Owner • Travel needs team communication Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 18 2013-02-15 Andrea Heck / Healthcare SYNGO

19.
Product Owner team communicationIn the whole Product Owner team Product Owner team Workshops - one to two times per Chief year: roadmap, big features next Product Owner Project Lead Lead release, process improvement Architect Weekly sync: virtual status meeting Module Product Module Product Module Product *App or Module  Owner* Owner Owner Product Owner Product Owners Site Siemens AG 2013 All rights reserved. Scrum TeamsPage 19 2013-02-15 Andrea Heck / Healthcare SYNGO

20.
Product Owner team communicationIn the Product Owner Core Team Product Owner team Daily sync across modules. Chief Important content topics are Product Owner Project Lead Lead discussed. Locally in HQ only. Architect Weekly sync including module architects. Discuss features that Module Product Module Product Module Product concern other modules. Owner Owner Owner Locally in HQ only. Face to face personal meetings Recently we have one module PO at between Module POs or with the a different site who can only Chief PO –very helpful. participate in these meetings when he is in the HQ. He needs to travel a lot.Siemens AG 2013 All rights reserved.Page 20 2013-02-15 Andrea Heck / Healthcare SYNGO

21.
Product Owner team communicationRoles in Scrum Team System Analyst – supports Product Owner in detailed research and requirements. Documents backlog System grooming results in backlog and Analyst specification document. Architect Team-Architect – coordinates technical features, redesigns, takes care of technical debt, protects architecture Scrum Master – takes care for Developers and Testers organization, improvement, process Scrum MasterSiemens AG 2013 All rights reserved.Page 21 2013-02-15 Andrea Heck / Healthcare SYNGO

22.
Product Owner team communicationWithin the Module – model 1Module Product Owner and modulearchitect in HQ, a few teams - onsite Moduleand offsite. Architect Module PO prioritizes backlog alone Backlog grooming with teams is supported by system analyst, module architect and team architects Module PO participates in the sprint reviews with each team and accepts the resultsSiemens AG 2013 All rights reserved.Page 22 2013-02-15 Andrea Heck / Healthcare SYNGO

23.
Product Owner team communicationWithin the Module – model 2Module Product Owner in HQ, a localProduct Owner and a module architect, afew teams – all offsite on the same site. Module PO prioritizes with local PO Intense communication M-PO and local PO by virtual sync meetings and visits Backlog grooming with teams mainly by local PO Local PO participates in the sprint reviews with each team and accepts the Module results ArchitectSiemens AG 2013 All rights reserved.Page 23 2013-02-15 Andrea Heck / Healthcare SYNGO

24.
Product Owner team communicationWithin the Module – model 3Module Product Owner and modulearchitect in HQ, each team with a teamProduct Owner - onsite and offsite teams. Module Architect Module PO prioritizes top level Top level backlog grooming with team POs, and module architect Weekly virtual sync meetings of module PO, module AR, team POs Team PO accepts the results of each sprint for his/her team Module PO participates in selected Product Owner sprint reviewsSiemens AG 2013 All rights reserved.Page 24 2013-02-15 Andrea Heck / Healthcare SYNGO

25.
Product Owner team communicationTravel needs Module Product Owners travel every sprint (4 weeks) to spend a few days with their remote teams Local Product owners from sites travel to HQ to stay in contact with the rest of PO team, and with other stakeholders (5 to 10 times per year)Siemens AG 2013 All rights reserved.Page 25 2013-02-15 Andrea Heck / Healthcare SYNGO

26.
Distributed Product Owner team @ SYNGO • Different customer types • Congresses • Local collaboration sites Customer collaboration • Customer Use Evaluation sites • POs travel to special sites Product Owner team • Radiology workshop communication • Admin workshop Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 26 2013-02-15 Andrea Heck / Healthcare SYNGO

27.
Customer collaborationDifferent Customer TypesChallenge:All Product Owners need to haveaccess to different types of customers,reflecting different market segmentsIn our case Big and small hospitals distributed hospitals with common infrastructure Less and more tendency to automation of workflows Country, culture, tradition…Siemens AG 2013 All rights reserved.Page 27 2013-02-15 Andrea Heck / Healthcare SYNGO

28.
Customer collaborationCongressesProduct Owners need to travel toimportant congresses which ourcustomers visit as well, in our case e.g.ECR in Vienna,RSNA in Chicago,Arab Health in Dubai Personal customer contacts Learn from customers Organize user meetingsSiemens AG 2013 All rights reserved.Page 28 2013-02-15 Andrea Heck / Healthcare SYNGO

29.
Customer collaborationLocal collaboration sitesWe have collaboration contracts withhospitals at the cities where ourdevelopment teams are  Hospital visits for team members  Product Owners have a local contact  Sometimes local contact can be used for showing intermediate state of featuresSiemens AG 2013 All rights reserved.Page 29 2013-02-15 Andrea Heck / Healthcare SYNGO

30.
Customer collaborationCustomer Use Evaluation sitesWe do a Customer Use Evaluationbefore each product release at 15 to 20sites around the globe Each Product Owner is responsible for one site as main contact for all topics All Product Owners get summarized feedback from Customer sites All Product Owners can ask selected Customer sites about their specific topicsSiemens AG 2013 All rights reserved.Page 30 2013-02-15 Andrea Heck / Healthcare SYNGO

31.
Customer collaborationProduct Owners travel to specialsitesSome Product Owners still need quitespecific customers for their topics: Who is advanced enough or thinks abstract enough about future needs to talk about this particular topic? With whom can we talk about a topic that is still totally confidential?Siemens AG 2013 All rights reserved.Page 31 2013-02-15 Andrea Heck / Healthcare SYNGO

32.
Customer collaborationRadiology workshop Once per year, 10 -15 radiologists from customers are invited to one site for 3 days Good mixture of customer types and countries All Product Owners can present and participate They present the features of the current release for early feedback They give a preview on concepts for next release: a) useful feature? b) useable concept?Siemens AG 2013 All rights reserved.Page 32 2013-02-15 Andrea Heck / Healthcare SYNGO

33.
Customer collaborationAdmin workshop Once per year, 10 IT admins and clinical admins from customers are invited to one site for 3 days Selection criteria: long term installed site and intense usage of admin tools and features Mainly for Product Owners from the admin related module, others can participate Excellent feedback from users The Module PO gives the admins virtual money to spend on different future features and wishes => they learn how we prioritizeSiemens AG 2013 All rights reserved.Page 33 2013-02-15 Andrea Heck / Healthcare SYNGO

34.
Conclusion? Customer collaboration Product Owner team communication Growing a distributed Product Owner team BackgroundSiemens AG 2013 All rights reserved.Page 34 2013-02-15 Andrea Heck / Healthcare SYNGO

35.
Conclusion? Yes, we can! Yes, it is possible and has lots of advantages to distribute the Product Owner team with the collocated Scrum teams to the sites. However, it requires  A lot of travel for the POs in the headquarters as well as the POs at supplier sites  Careful, background and skill oriented selection of persons for the PO role  Investment into closing the knowledge gaps and improving skillsSiemens AG 2013 All rights reserved.Page 35 2013-02-15 Andrea Heck / Healthcare SYNGO

36.
Speaker Bio Andrea Heck Agile Transition Lead & Agile Coach Dipl. Inf (Univ), CSM, CSPO, CSP Siemens AG Healthcare SYNGO Hartmannstr. 16 91052 Erlangen, Germany E-mail: andrea.heck@siemens.com Twitter: @AgileAndrea Blog: http://agileandrea.com/ Answers for life.Siemens AG 2013 All rights reserved.Page 36 2013-02-15 Andrea Heck / Healthcare SYNGO