SPM1 - Introductie
•Download as PPTX, PDF•
1 like•619 views
De slides van de eerste bijeenkomst Software Product Management. Door deze slides te bestuderen krijg je een beeld van wat je kunt verwachten tijdens de najaarscursus SPM. Voor meer informatie: spmcursusnajaar2017.weebly.com
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to SPM1 - Introductie
Similar to SPM1 - Introductie (20)
Recently uploaded
Recently uploaded (20)
SPM1 - Introductie
- 1. Introduction to Software Product Management Bijeenkomst 1 Sjaak Brinkkemper Garm Lucassen 7 maart 2017
- 2. Introductie in Software Product Management • Sessie 1 van de cursus Software Product Management • Georganiseerd vanuit – Universiteit Utrecht – Nederlands Instituut voor de Software Industrie – International Software Product Management Association – Software VOC • https://www.nisi.nl/ • http://www.nederlandict.nl/ • http://www.ispma.org/ 2
- 3. Agenda • Introductie • SPM competence model • Oefening & pauze • Requirements management • Release planning • Oefening & pauze • Product planning • Portfolio management • Oefening & pauze • Agenda & huiswerk 3
- 4. Doelstellingen • Deelnemers bekend maken met de kennis en theorie op het gebied van software product management. • Deelnemers vaardigheden bij brengen voor het efficiënt en effectief kunnen werken als product manager. • Deelnemers voorbereiden op een snel veranderende werkomgeving. Hoe ga je om met Agile? • Deelnemers in staat stellen om de functie software product management binnen het softwarebedrijf te professionaliseren. • Uitwisselen van ervaringen met product managers van andere bedrijven. • Certificaat van deelname • Internationaal SPM-certificaat, zie http://ispma.org/ 4
- 5. Huiswerk • Ter voorbereiding van de volgende bijeenkomst • Vertrouwelijk • Geen criterium voor certificaat • Cursistenpresentaties • Actieve deelname zorgt voor meer resultaat van de cursus 5
- 6. Certificering • International Software Product Management Association: Standardization of Education and Certification • The International Software Product Management Association (ISPMA) is an open group of experts from industry and research with the goal to foster software product management excellence across industries. • Syllabus v1.3 available • http://www.ispma.org/ 6
- 7. 7 Vakgroep Organisation and Information • Sjaak Brinkkemper • Slinger Jansen • Marco Spruit • Fabiano Dalpiaz • Jan Martijn van der Werf • Sergio España Cubillo • Marjan Askari • Sietse Overbeek • Siamak Farshidi • Erik Jagroep • Wienand Omta • Garm Lucassen • Vincent Menger • Ian Shen • Basak Aydemir • Govert-Jan Slob • Michiel Meulendijk
- 8. Onderzoeksthema Product Software: Methodology of Development, Implementation and Entrepreneurship 3 onderzoekslijnen –Development Methodology –Implementation and Adoption –Entrepreneurship 8
- 9. Teamintroductie • Sjaak Brinkkemper • Garm Lucassen 9
- 10. Deelnemersintroductie • Naam, bedrijf, functie, product • Wat zijn de grootste problemen die je tegenkomt op het gebied van software product management? • Wat hoop je in deze cursus te vinden? • 15 deelnemers, 15 reacties! 10
- 11. Deelnemers (1) Verschillende functies: • (Software) Product Manager (6) • Product Owner (1) • Business analist (3) • Operationeel directeur (1) • Servicedesk coördinator (1) • Hoofd verkoop en helpdesk (1) • Commercieel verantwoordelijke (1) • Senior sales engineer 11
- 12. Deelnemers (2) Product management zoals nu uitgevoerd: –is vooral development-gericht (12x) –is vooral marketing-gericht (1x) –Beiden (1x) –Nvt (1x) 12
- 13. Deelnemers (3) Aantal jaar ervaring in huidige functie: 13 0 1 2 3 4 5 6 7 >1jaar 1-2jaar 2-5jaar 5+jaar
- 14. Deelnemers (4) • Bedrijfsgrootte variatie: 14 0 1 2 3 4 5 6 7 0-20 21-50 51-200 200+
- 15. Deelnemers (5) • Klantenkring: Gemeenten, MKB, plantenkwekerijen, accountants, ZZP, woningcorporaties, retail, supermarktketens, ict wederverkopers, havens • Producten: CMS, CRM, ERP, middleware, burgerzaken, boekhouding, belastingaangifte, administratie, planning, veiligheid, security, onderwijs • 1 overeenkomst: iedereen ontwikkelt softwareproducten. 15
- 16. Agenda • Introductie • SPM competence model • Oefening & pauze • Requirements management • Release planning • Oefening & pauze • Product planning • Portfolio management • Oefening & pauze • Agenda & huiswerk 16
- 18. 18 Software product management (SPM) is the discipline that governs a software product over its whole life cycle, from its inception to customer delivery, in order to generate the biggest possible value to the business.
- 19. Introduction competence model • Software product management – Complex organization of requirements & tracking of changes in the design – High release frequency – Product manager has many responsibilities but little authority – Interaction with many stakeholders Need for an integrated body of knowledge: SPM Competence Model 19
- 20. Deliverable structure Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … 20 Portfolio: The complete set of products of a company
- 21. Deliverable structure Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … 21 Product: A packaged configuration targeted to a specific market
- 22. Deliverable structure Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … 22 Release: A formalized sellable version
- 23. Deliverable structure Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … 23 Requirement: Wish for a future product feature
- 24. Framework levels Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … 24 Portfolio Management Product Planning Release Planning Requirements Management Deliverable structure Business function Deliverable structure leads to business functions Responsibility for business function implies accountability for deliverables
- 26. Stakeholders 26
- 33. Oefening • Vul de ‘deliverable structure’ in voor je eigen organisatie. Geef ook aan waarvoor je verantwoordelijk bent 33 Microsoft Office Portfolio Access Communicator Excel TaalpakkettenPowerpoint ... Word 2010 Office Word 2007 ... Word Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … … Portfolio Product 2 Release 1.1 Requirement 2 Product k Release 2.0 Requirement n Product 1 Release 1.0 Requirement 1 … … … …
- 34. Agenda • Introductie • SPM competence model • Oefening & pauze • Requirements management • Release planning • Oefening & pauze • Product planning • Portfolio management • Oefening & pauze • Agenda & huiswerk 34
- 35. Stel je zelf de volgende vragen: • Herken je de processen die wij hebben geïdentificeerd in het framework? • Welke van deze processen zijn al geïmplementeerd in je organisatie? • Welke processen wil je graag implementeren of verbeteren? 35
- 36. Requirements management • “to deal with the content and administrative data of each individual requirement” • 3 processes –Requirement gathering –Requirements identification –Requirements organizing • Possibilities for Agile approach 36
- 38. Requirements gathering • Via internal stakeholders (partners, development, support, services, research and innovation) • Via external stakeholders (customers, partners, market) • Various techniques: – Stakeholder interviews – Joint Requirements Development Sessions – User groups – Customer interaction program – Etc. 38
- 40. Requirements identification • Market requirements vs. product requirements • Functional requirements, quality requirements & constraints • Customer input with new requirements (enhancement requests) or defects (software repairs) • Not: – Extensive domain knowledge & background information – Project management issues and software development processes 40
- 43. PR to MR mapping 43 Q: Who already does this? Can you show an example of how you do this in your issue tracker?
- 45. Requirements organizing • Requirements can be organized per product, release, theme, or core asset. • Organization according to the releases on the roadmap. • Tracking requirements interdependencies • Result: a list or database with product requirements 45
- 46. Release planning • “to deal with the set of requirements of each release” • 6 processes – Requirements prioritization – Release definition – Release definition validation – Scope change management – Build validation – Launch preparation 46
- 48. Requirements prioritization Techniques: • Voting round • Cost value approach • Features prioritization matrix • Etc. 48
- 49. Features prioritization matrix 49 Relative weights 2 1 1 0,5 FEATURE Relative Benefit Relative Penalty Total Value Value % Relative Cost Cost % Relative Risk Risk % Priority 1. Query invoice status. 5 3 13 8,4 2 4,8 1 3,0 1,345 2. Generate monthly in- out report 9 7 25 16,2 5 11,9 3 9,1 0,987 3. Resend outstanding invoice 5 5 15 9,7 3 7,1 2 6,1 0,957 … Totals 19 15 53 100 10 100 6 100 --
- 51. Release definition • List of selected requirements and estimated development hours 51
- 53. Release definition validation • Roadmap fit • Investments in resources • Various ways: – Presentation for the company board (and other internal stakeholders) – Business case – Return On Investment (ROI) Estimation 53
- 55. Scope change management • What to do in case of –extra requirements forced by the company board? –a delay due to an absent engineer? –an opportunity from a customer or prospect? • Implementation of a scope change process (SCRUM, PRINCE2, ASL, etc.) 55
- 57. Build validation • Internal validation • External validation (e.g. beta testing, pilot) • (Certification) 57
- 59. Launch preparation • Internal stakeholders: –Sales and marketing which features are in the new product release –Services to be able to implement the new product release –Support to be able to help customers with problems • External stakeholders –Existing customers acquire new version? –Implementation partners to be able to implement the new product release 59
- 60. Oefening 1. Geef in het SPM competence model aan welke requirements management en release planning processen je al hebt geïmplementeerd in je organisatie. 2. Geef aan welke processen je wil gaan implementeren of verbeteren. 60
- 61. Agenda • Introductie • SPM competence model • Oefening & pauze • Requirements management • Release planning • Oefening & pauze • Product planning • Portfolio management • Oefening & pauze • Agenda & huiswerk 61
- 62. Product planning • “to deal with the different releases each product has” • 3 processes –Roadmap intelligence –Product roadmapping –Core asset roadmapping 62
- 64. Roadmap intelligence 64 • What’s going on? • Make overviews of markets, customers, competitors, technology, partners
- 66. Core asset roadmapping • Management and development of a Core asset base • Examples: –Software components –Executables –Databases –Functional designs –Product documentation –Test cases 66
- 68. Product roadmap • A high-level sketch of where the company’s product(s) is/are going to give internal and external stakeholders the ability to plan accordingly • Based on themes, golden features, main components, etc. • 1 to 3 year outlook 68
- 69. Short-term… 69 Planning 2016 In 2016 worden een drietal releases gepland waarin diverse nieuwe functionaliteiten worden opgenomen. Welke release in het teken van een thema staan. De volgende releases zijn gepland: Release Thema Onderwerpen December 2015 / januari 2016 Jaarafsluiting 2015 en initiëren 2016 Alle noodzakelijke toevoegingen en wijzigingen om een correcte jaarafsluiting en jaarovergang te kunnen realiseren. Tevens een aantal functionaliteiten, welke niet meer in de release van 1 december meegenomen konden worden. 1 juni 2016 De ‘werknemer’ Uitbreidingen welke direct met de werknemergegevens te maken hebben. Naast uitbreidingen van de werknemerstamkaart, met name uitbreidingen op het gebied van de personeelsinformatie gegevens. 1 november 2016 Werkstroom ondersteuning Uitbreidingen op het gebied van verdere ondersteuning bij de salarisverwerking December 2016 / januari 2017 Jaarafsluiting Jaarwerk 2016 en jaarovergang naar 2017
- 70. … or long-term? 70 (External) commitmentCommit Planned Tentative 1.2 Q1 Q2 Q3 Q4 Q1 Q2 Q3 2013 2014 Q4 PR2 PR3 PR4 PR5 Q1 Q2 Q3 2015 PR6 Beta Q4 Q1 2016 PR1 1.3 1.4 1.5 2.0 2.1 1.0 1.1 2.0 2.1
- 72. Portfolio management • “to deal with the products in the product portfolio” • 3 processes –Market analysis –Product lifecycle management –Partnering & contracting 72
- 74. Market analysis • Market research –Focus groups –Surveys (postal/mail/telephone) –Customer panels –Observation via Support, Services, Sales & Marketing –… • Competition analysis • Research firms –Gartner –Forrester –… 74
- 76. Product lifecycle management (1) • Product portfolio assessment – Determine if your current product portfolio is meeting strategic business objectives. – Determine coverage gaps and areas of overlap. – Understand what changes may need to be made to improve competitive position. • Win/loss analysis for new products 76
- 77. Product lifecycle management (2) • Product lines • Techniques to maximize the lifetime value of your product portfolio • End-of-life / sun setting strategies 77
- 79. Partners • Implementation partners – SAP Implementation Partners: Accenture, Cap Gemini, Deloitte, etc. • Development partners – (Offshore) development partners for parts of your product • Content partners –Manufacturers, stock photos, news • Distribution partners – Microsoft Windows for Adobe (Flash, Acrobat, etc.) 79
- 80. Oefening 1. Geef in het SPM competence model aan welke product planning en portfolio management processen je al hebt geïmplementeerd in je organisatie. 2. Geef aan welke processen je wil gaan implementeren of verbeteren. 80
- 82. Agenda • Introductie • SPM competence model • Oefening & pauze • Requirements management • Release planning • Oefening & pauze • Product planning • Portfolio management • Oefening & pauze • Agenda & huiswerk 82
- 83. Agenda 83 Bijeenkomst 2 Requirements management Bijeenkomst 3 Requirements management Bijeenkomst 4 Product planning Bijeenkomst 5 Portfolio management
- 84. Agenda 84 Bijeenkomst 6 Release planning Bijeenkomst 7 Sales Channels & Business Aspects Bijeenkomst 8 Agile SPM & Intellectual Property Bijeenkomst 9 Offshoring & Marketing Bijeenkomst 10 Rol van de product manager binnen de organisatie
- 85. Huiswerk • Beschrijf de twee belangrijkste SPM-uitdagingen die je de komende tijd zou willen verbeteren. • Neem een typische product requirement mee. 85
- 86. Cursuswebsite http://spmcursusvoorjaar2017.weebly.com Slides ontvang je via mail of zijn op website toegankelijk met wachtwoord: spm17v 86
- 87. Informatie Voor meer informatie over deze cursus kunt u contact opnemen met: Garm Lucassen g.lucassen@uu.nl 030 253 6311 Copyright © 2017 Inge van de Weerd, Sjaak Brinkkemper, Kevin Vlaanderen, Garm Lucassen, Universiteit Utrecht 87
- 88. Thank you for your attention!