Slide 1

Slide 1 text

Konstantin Diener | [email protected] | @onkelkodi … das richtige Produkt bauen Wichtiger als die Technik

Slide 2

Slide 2 text

Wie bauen wir die richtige So ft ware?

Slide 3

Slide 3 text

Konstantin Diener CTO und Gründer von cosee

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Our highest priority is to satisfy the customer through early and continuous delivery of valuable so ft ware. Agile Manifesto

Slide 9

Slide 9 text

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Agile Manifesto

Slide 10

Slide 10 text

Business people and developers must work together daily throughout the project. Agile Manifesto

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

Frühes Feedback durch Iterationen.

Slide 14

Slide 14 text

Viele der Praktiken aus XP & Co sind heute weit verbreitet.

Slide 15

Slide 15 text

Continuous attention to technical excellence and good design enhances agility. Agile Manifesto

Slide 16

Slide 16 text

… das bekommen wir schon ganz gut hin!

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

DevOps Die „agile Insel“ endet nicht beim Betrieb.

Slide 21

Slide 21 text

Techniken wie Continuous Delivery helfen uns bei frühem Feedback.

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Heute bauen wir o ft Internet- Anwendungen …

Slide 26

Slide 26 text

… und sind o ft keine Dienstleister mehr, wie die Unterzeichner des Agilen Manifests.

Slide 27

Slide 27 text

Our highest priority is to satisfy the customer through early and continuous delivery of valuable so ft ware. Agile Manifesto

Slide 28

Slide 28 text

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Agile Manifesto

Slide 29

Slide 29 text

Business people and developers must work together daily throughout the project. Agile Manifesto

Slide 30

Slide 30 text

Wir haben keine Fachbereiche mehr, die unser Backlog füllen.

Slide 31

Slide 31 text

Wo kommt das „richtige“ Product Backlog her?

Slide 32

Slide 32 text

WHAT should we do? WHY are we doing it? HOW are we doing it? Martin Eriksson

Slide 33

Slide 33 text

User Story Mapping Je ff Patton

Slide 34

Slide 34 text

Je ff Patton, User Story Mapping, https://jpattonassociates.com/

Slide 35

Slide 35 text

60%–90% unserer Ideen haben keine positiven Auswirkungen http://radar.oreilly.com/2015/03/what-should-replace-the-project-paradigm.html

Slide 36

Slide 36 text

There is nothing quite so useless as doing with great e ff iciency something that should not be done at all. Peter Drucker

Slide 37

Slide 37 text

Simplicity – the art of maximizing the amount of work not done – is essential. Agile Manifesto

Slide 38

Slide 38 text

Aber warum ist Produktentwicklung so unsicher?

Slide 39

Slide 39 text

https://svpg.com/four-big-risks/ value risk Kunden werden es kaufen bzw. Benutzer werden es benutzen. usability risk Benutzer finden heraus, wie es benutzt wird. feasibility risk Wir können es bauen (Zeit, Fähigkeiten, Technologie). business viability risk Es funktioniert für unsere Firma.

Slide 40

Slide 40 text

Vision Statement Kurze Beschreibung der Vision/Idee Zielgruppe Welches Marktsegment/Ziel- oder Nutzer- gruppe soll das Produkt ansprechen? Dieser Punkt kann auch in Form einer Persona beschrieben sein. Bedürfnisse/Probleme Welche Bedürfnisse der Zielgruppe werden befriedigt? In welcher Form schafft das Produkt Wert für den Benutzer oder empfindet er es als wertvoll? Welche Emotionen weckt das Produkt? Top Features Welches sind die drei bis fünf wichtigsten Funktionen? Gibt es ein Alleinstellungsmerkmal (USP)? Geschäftsmodell Wie wird mit dem Produkt Geld verdient? Wer sind die zahlenden Kunden? Was ist der Kunde bereit zu bezahlen und wie bezahlt er? Konkurrenz Gibt es Organisationen am Markt, die ein ähnliches Produkt anbieten? Differenznutzen Was bietet das Produkt mehr, weniger oder anders gegenüber vergleichbaren Produkten? angelehnt an http://www.romanpichler.com/tools/vision-board cosee_VisionStatement_Plakat2019_ Druck.indd 1 15.11.18 10:17

Slide 41

Slide 41 text

What are the most important costs inherent in our business model? Which Key Resources are most expensive? Which Key Activities are most expensive? Revenue Streams Through which Channels do our Customer Segments want to be reached? How are we reaching them now? How are our Channels integrated? Which ones work best? Which ones are most cost-efficient? How are we integrating them with customer routines? For what value are our customers really willing to pay? For what do they currently pay? How are they currently paying? How would they prefer to pay? How much does each Revenue Stream contribute to overall revenues? Channels Customer Relationships Customer Segments channel phases: 1. Awareness How do we raise awareness about our company’s products and services? 2. Evaluation How do we help customers evaluate our organization’s Value Proposition? 3. Purchase How do we allow customers to purchase specific products and services? 4. Delivery How do we deliver a Value Proposition to customers? 5. After sales How do we provide post-purchase customer support? Mass Market Niche Market Segmented Diversified Multi-sided Platform examples Personal assistance Dedicated Personal Assistance Self-Service Automated Services Communities Co-creation For whom are we creating value? Who are our most important customers? What type of relationship does each of our Customer Segments expect us to establish and maintain with them? Which ones have we established? How are they integrated with the rest of our business model? How costly are they? Value Propositions Key Activities Key Partners Key Resources Cost Structure What value do we deliver to the customer? Which one of our customer’s problems are we helping to solve? What bundles of products and services are we offering to each Customer Segment? Which customer needs are we satisfying? What Key Activities do our Value Propositions require? Our Distribution Channels? Customer Relationships? Revenue streams? Who are our Key Partners? Who are our key suppliers? Which Key Resources are we acquiring from partners? Which Key Activities do partners perform? What Key Resources do our Value Propositions require? Our Distribution Channels? Customer Relationships? Revenue Streams? characteristics Newness Performance Customization “Getting the Job Done” Design Brand/Status Price Cost Reduction Risk Reduction Accessibility Convenience/Usability categories Production Problem Solving Platform/Network types of resources Physical Intellectual (brand patents, copyrights, data) Human Financial motivations for partnerships: Optimization and economy Reduction of risk and uncertainty Acquisition of particular resources and activities is your business more: Cost Driven (leanest cost structure, low price value proposition, maximum automation, extensive outsourcing) Value Driven (focused on value creation, premium value proposition) sample characteristics: Fixed Costs (salaries, rents, utilities) Variable costs Economies of scale Economies of scope www.businessmodelgeneration.com The Business Model Canvas On: Iteration: Designed by: Designed for: Day Month Year No. types: Asset sale Usage fee Subscription Fees Lending/Renting/Leasing Licensing Brokerage fees Advertising fixed pricing List Price Product feature dependent Customer segment dependent Volume dependent dynamic pricing Negotiation( bargaining) Yield Management Real-time-Market This work is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Slide 42

Slide 42 text

WHAT should we do? WHY are we doing it? HOW are we doing it? Martin Eriksson

Slide 43

Slide 43 text

Vision Statement Kurze Beschreibung der Vision/Idee Zielgruppe Welches Marktsegment/Ziel- oder Nutzer- gruppe soll das Produkt ansprechen? Dieser Punkt kann auch in Form einer Persona beschrieben sein. Bedürfnisse/Probleme Welche Bedürfnisse der Zielgruppe werden befriedigt? In welcher Form schafft das Produkt Wert für den Benutzer oder empfindet er es als wertvoll? Welche Emotionen weckt das Produkt? Top Features Welches sind die drei bis fünf wichtigsten Funktionen? Gibt es ein Alleinstellungsmerkmal (USP)? Geschäftsmodell Wie wird mit dem Produkt Geld verdient? Wer sind die zahlenden Kunden? Was ist der Kunde bereit zu bezahlen und wie bezahlt er? Konkurrenz Gibt es Organisationen am Markt, die ein ähnliches Produkt anbieten? Differenznutzen Was bietet das Produkt mehr, weniger oder anders gegenüber vergleichbaren Produkten? angelehnt an http://www.romanpichler.com/tools/vision-board cosee_VisionStatement_Plakat2019_ Druck.indd 1 15.11.18 10:17

Slide 44

Slide 44 text

WHAT should we do? WHY are we doing it? HOW are we doing it? Martin Eriksson

Slide 45

Slide 45 text

Produktprinzipien erleichtern die Entscheidungen.

Slide 46

Slide 46 text

Das alles ist Product Discovery.

Slide 47

Slide 47 text

Produktentwicklung besteht aus Discovery und Delivery.

Slide 48

Slide 48 text

https://www.producttalk.org/2017/02/evolution-product-discovery/ Discovery Was bauen wir? Delivery Wie bauen wir es?

Slide 49

Slide 49 text

Je ff Patton, User Story Mapping, https://jpattonassociates.com/

Slide 50

Slide 50 text

The only way to know you’ve picked the right strategy is to validate it with customers. Martin Eriksson

Slide 51

Slide 51 text

Das ist kein One-O ff …

Slide 52

Slide 52 text

… sondern wie Continuous Delivery auch Continuous Discovery.

Slide 53

Slide 53 text

Verstanden! Das macht aber unser Product Owner …

Slide 54

Slide 54 text

If you’re only using your engineers to code, you’re only getting half their value. Marty Cagan

Slide 55

Slide 55 text

https://svpg.com/four-big-risks/ value risk customers will buy it or users will choose to use it usability risk users can figure out how to use it feasibility risk we can build it (time, skills, technology) business viability risk works for our business

Slide 56

Slide 56 text

value risk usability risk feasibility risk

Slide 57

Slide 57 text

usability risk feasibility risk Product Owner

Slide 58

Slide 58 text

feasibility risk Product Owner Designer

Slide 59

Slide 59 text

Product Owner Designer Entwickler

Slide 60

Slide 60 text

Product Trio

Slide 61

Slide 61 text

Continuous Discovery Habits Teresa Torres

Slide 62

Slide 62 text

Na, gut. Aber wir dürfen das in der Firma gar nicht!

Slide 63

Slide 63 text

… Technology is increasingly being driven by bottom-up, rather than top-down adoption. The New Kingmakers

Slide 64

Slide 64 text

If IT decision makers aren’t making the decisions any longer, who is calling the shots? The answer is developers. The New Kingmakers

Slide 65

Slide 65 text

Letzten Endes ist es nicht euer Job, alle Anforderungen abgearbeitet zu haben – sondern die Welt zu verändern. Je ff Patton

Slide 66

Slide 66 text

No content