{"id":28821,"date":"2026-04-01T11:40:21","date_gmt":"2026-04-01T09:40:21","guid":{"rendered":"https:\/\/www.pureconsultant.de\/de\/?p=28821"},"modified":"2026-04-01T11:47:27","modified_gmt":"2026-04-01T09:47:27","slug":"story-points-schaetzen-und-fehler-vermeiden","status":"publish","type":"post","link":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/","title":{"rendered":"Story Points sch\u00e4tzen und Fehler vermeiden"},"content":{"rendered":"<div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Story Points sch\u00e4tzen und Fehler vermeiden &#8211; <strong><a href=\"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points\/\">Story Points<\/a><\/strong> geh\u00f6ren f\u00fcr viele Teams zum agilen Alltag. Trotzdem k\u00e4mpfen erstaunlich viele Organisationen mit unzuverl\u00e4ssigen Sch\u00e4tzungen, politischen Diskussionen um Velocity und Frust in der Planung. Die gute Nachricht: Die typischen Probleme sind l\u00f6sbar \u2013 wenn Sie Story Points richtig verstehen, konsequent anwenden und ein paar verbreitete Irrt\u00fcmer abr\u00e4umen.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>In diesem Leitfaden erfahren Sie, wie Sie Story Points so sch\u00e4tzen, dass Ihre Planung robuster wird, Ihr Team fokussierter arbeitet und Diskussionen sachlicher werden. Sie lernen konkrete Schritte, Workshop-Formate und Praxis-Checks kennen, mit denen Sie Fehler vermeiden und Ihre Sch\u00e4tzqualit\u00e4t systematisch verbessern.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--image\">\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"948\" height=\"402\" src=\"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection376.svg\" alt=\"Story Points sch\u00e4tzen und Fehler vermeiden\" class=\"wp-image-28823\"\/><figcaption class=\"wp-element-caption\">Story Points sch\u00e4tzen und Fehler vermeiden<\/figcaption><\/figure>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">1. Grundlagen: Was sind Story Points \u2013 und was nicht?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Kurzdefinition:<br class=\"\">Story Points sind eine relative Ma\u00dfeinheit, mit der ein agiles Team den Gesamtaufwand einer User Story bewertet \u2013 basierend auf:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Umfang<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Komplexit\u00e4t<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Risiken und Unsicherheiten<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wichtige Klarstellungen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points sind kein Zeitma\u00df (keine Stunden, keine Tage).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points sind teamindividuell \u2013 5 Punkte bedeuten in Team A etwas anderes als in Team B.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points sind eine Entscheidungsgrundlage f\u00fcr Planung, keine exakten Prognosen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Wozu Story Points \u00fcberhaupt?<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Story Points helfen Teams dabei, \u2026<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sprints realistisch zu planen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Unsicherheit sichtbar zu machen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>fachliche Komplexit\u00e4t fr\u00fch zu erkennen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussionen weg von \u201eWie lange dauert das?\u201c hin zu \u201eWas steckt wirklich drin?\u201c zu lenken<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Sie unterst\u00fctzen Entscheider, weil:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Lieferf\u00e4higkeit besser absch\u00e4tzbar wird (Roadmaps, Releases)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abh\u00e4ngigkeiten und Engp\u00e4sse fr\u00fcher sichtbar werden<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Priorisierung auf Nutzen vs. Aufwand fundierter m\u00f6glich ist<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">2. Suchintention verstehen: Was wollen \u201eStory Points\u201c-Suchende wirklich?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wer nach \u201eStory Points sch\u00e4tzen und Fehler vermeiden\u201c sucht, hat in der Regel ein sehr praktisches Anliegen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie sch\u00e4tze ich richtig?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWarum passt unsere Velocity nie zur Realit\u00e4t?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie verhindere ich, dass sich das Team \u201ahochsch\u00e4tzt\u2018?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie erkl\u00e4re ich dem Management, dass Story Points keine Stunden sind?\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Die meisten Leser wollen konkrete Handlungsempfehlungen, keine agile Grundlagentheorie. Genau darauf ist dieser Leitfaden ausgerichtet: klare Schritte, Checklisten, Beispiele.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">3. Die h\u00e4ufigsten Missverst\u00e4ndnisse \u00fcber Story Points<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Schlechte Sch\u00e4tzungen entstehen selten durch das Werkzeug, fast immer durch falsche Erwartungen. Typische Missverst\u00e4ndnisse:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">3.1 Story Points = versteckte Stunden<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Viele Teams beginnen mit Story Points, behalten aber innerlich ihr Denken in Stunden:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201e1 Punkt = 2 Stunden\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201e13 Punkte = etwa 3 Tage\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Problem:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Druck, \u201ep\u00fcnktlich\u201c zu liefern<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Scham oder Rechtfertigungsdruck, wenn Stories \u201e\u00fcberziehen\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussionen \u00fcber individuelle Performance<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Konsequenz:<br class=\"\">Die Vorteile relativer Sch\u00e4tzung gehen verloren. Story Points werden zur schlecht getarnten Zeitsch\u00e4tzung.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Besser: Story Points konsequent relativ nutzen:<br class=\"\">\u201eIst diese Story ungef\u00e4hr so aufwendig wie unsere 5-Punkte-Referenzstory \u2013 oder deutlich weniger\/mehr?\u201c<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">3.2 Story Points als Produktivit\u00e4ts-Messgr\u00f6\u00dfe<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ein weiterer Klassiker: Velocity wird als KPI f\u00fcr Teamleistung oder als Benchmark zwischen Teams genutzt.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eTeam A hat 60 Punkte, Team B nur 35 \u2013 warum ist Team B so langsam?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWir m\u00fcssen unsere Velocity steigern.\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Folgen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teams beginnen, h\u00f6her zu sch\u00e4tzen, um besser dazustehen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories werden k\u00fcnstlich gesplittet oder zusammengefasst.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fokus verschiebt sich von Wertsch\u00f6pfung zu \u201ePunkte-Maximierung\u201c.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ergebnis: Forecasts werden unbrauchbar, Vertrauen br\u00f6ckelt.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Merksatz:<br class=\"\">Story Points sind ein internes Planungswerkzeug, kein Controlling-Instrument.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">3.3 Einheitliche Skala \u00fcber mehrere Teams hinweg<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Unternehmen versuchen h\u00e4ufig, eine \u201eunternehmensweite Story-Point-Skala\u201c einzuf\u00fchren, um Projekte, Abteilungen oder Lieferanten vergleichen zu k\u00f6nnen.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Problem:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teams arbeiten mit unterschiedlichen Technologien, Dom\u00e4nen, Reifegraden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ein \u201e8 Punkte\u201c-Task im Data-Team ist nicht mit \u201e8 Punkten\u201c im Frontend-Team vergleichbar.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Endlose Diskussionen \u00fcber Definitionen, kaum Mehrwert.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Besser:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points strikt teamlokal verwenden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>F\u00fcr unternehmensweite Steuerung lieber andere Ma\u00dfe (z. B. Durchlaufzeiten, Fertigstellungsgrade, gesch\u00e4ftlicher Outcome) nutzen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">4. Story Points richtig einf\u00fchren: Schritt-f\u00fcr-Schritt<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie Story Points neu einf\u00fchren oder \u201eretten\u201c m\u00f6chten, gehen Sie strukturiert vor.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 1: Ziel kl\u00e4ren \u2013 gemeinsam mit Stakeholdern<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Beantworten Sie im Kreis aus Product Owner, Scrum Master\/Agile Coach, Team und Management:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wof\u00fcr wollen wir Story Points nutzen?<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sprintplanung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Release-Planung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Kapazit\u00e4tsabsch\u00e4tzung?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wof\u00fcr wollen wir Story Points bewusst nicht nutzen?<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Individuelle Leistungsbewertung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teamvergleiche?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Halten Sie diese Entscheidungen fest und kommunizieren Sie sie an alle Beteiligten.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 2: Referenz-Stories definieren<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Das Herz guter Sch\u00e4tzung ist ein gemeinsames Bezugsraster.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Vorgehen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ol class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Nehmen Sie 5\u201310 abgeschlossene User Stories aus der Vergangenheit.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>W\u00e4hlen Sie 3\u20135 Stories, die das Team \u201egut kennt\u201c.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ordnen Sie ihnen gemeinsam Story-Point-Werte zu, z. B.:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>1 Punkt: minimaler Aufwand, fast trivial<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>3 Punkte: typischer kleiner Task<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>5 Punkte: mittlere Komplexit\u00e4t, Standard-Fall<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>8 Punkte: gr\u00f6\u00dferer Baustein mit sp\u00fcrbaren Risiken<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Dokumentieren Sie diese Referenz-Stories im Wiki oder Backlog.<\/li>\n<\/div><\/ol>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Diese Referenzen dienen k\u00fcnftig als \u201eMesslatte\u201c, an der Sie neue Stories ausrichten.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 3: Einheitliche Bewertungskriterien festlegen<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Klare Kriterien verhindern endlose Debatten. Typische Dimensionen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>fachlicher Umfang (Anzahl Use Cases, Szenarien)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>technische Komplexit\u00e4t (Integrationen, neue Technologien, Architektur-\u00c4nderungen)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Risiken\/Unsicherheit (unklare Anforderungen, Drittanbieter, Legacy-Systeme)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abh\u00e4ngigkeiten (andere Teams, externe Partner)<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ein Praxisansatz:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Definieren Sie gemeinsam 3\u20135 Leitfragen, die bei jeder Sch\u00e4tzung beantwortet werden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Beispiel:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie neu ist dieses Thema f\u00fcr uns?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie gut verstehen wir die Anforderungen?\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eWie viele Komponenten\/Systeme sind betroffen?\u201c<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 4: Passende Skala w\u00e4hlen (Fibonacci &amp; Co.)<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Bew\u00e4hrt haben sich diskrete Skalen, z. B.:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fibonacci-Folge: 1, 2, 3, 5, 8, 13, 20, \u2026<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>oder eine reduzierte Variante: 1, 2, 3, 5, 8, 13<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Warum keine feinere Skala (z. B. 4, 6, 7, 9)?<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Dunkelgr\u00fcne Genauigkeit ist Illusion \u2013 man sch\u00e4tzt nur vermeintlich pr\u00e4ziser.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gr\u00f6bere Stufen zwingen zu klaren Entscheidungen und Diskussion.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Empfehlung:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>F\u00fcr Einsteiger-Teams: 1, 2, 3, 5, 8, 13<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sehr reife Teams mit hohem Durchsatz k\u00f6nnen bei Bedarf 20 erg\u00e4nzen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 5: Gemeinsames Sch\u00e4tzverfahren festlegen (Planning Poker)<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Planning Poker ist in vielen Teams Standard, weil es Diskussion und Beteiligung f\u00f6rdert:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ablauf:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ol class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Product Owner stellt die Story vor (Ziel, Akzeptanzkriterien).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Team kl\u00e4rt Verst\u00e4ndnisfragen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Jeder w\u00e4hlt verdeckt eine Karte (Story Point aus der Skala).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Alle decken gleichzeitig auf.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Bei gro\u00dfen Abweichungen erkl\u00e4ren Extremwerte ihre Sicht.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Zweite Abstimmung.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wert festlegen, sobald Konsens oder pragmatische Einigung erreicht ist.<\/li>\n<\/div><\/ol>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Tipps:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Zeitbox je Story (z. B. max. 5 Minuten).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories mit massiv abweichenden Sch\u00e4tzungen markieren und ggf. neu schneiden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussion auf Verst\u00e4ndnis und Risiken fokussieren, nicht auf \u201eRecht haben\u201c.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Schritt 6: Team-Velocity empirisch aufbauen<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Velocity ist der Durchschnitt der in einem Sprint erledigten Story Points.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Vorgehen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ol class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Die ersten 3\u20135 Sprints bewusst als Kalibrierung sehen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Velocity jedes Sprints retrospektiv festhalten:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>geplante Punkte<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>tats\u00e4chlich abgeschlossene Punkte (Definition of Done erf\u00fcllt)<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Durchschnitt berechnen, z. B. Mittel aus den letzten 3 Sprints.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diese Zahl nur (!) intern nutzen, um k\u00fcnftige Sprints zu planen.<\/li>\n<\/div><\/ol>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wichtig:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Velocity ist eine Folgegr\u00f6\u00dfe, kein Ziel.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Kein Zielwert wie \u201eWir m\u00fcssen auf 60 Punkte pro Sprint kommen\u201c definieren.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">5. Typische Fehler beim Sch\u00e4tzen mit Story Points \u2013 und wie Sie sie vermeiden<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Im Alltag wiederholen sich bestimmte Muster. Wenn Sie diese kennen, k\u00f6nnen Sie bewusst gegensteuern.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5.1 Anforderungen zu unklar \u2013 aber trotzdem sch\u00e4tzen<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Symptome:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Viele Fragen im Planning<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussionen im Kreis<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>H\u00e4ufige Nacharbeiten im Sprint<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Risiko:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sch\u00e4tzungen basieren auf Vermutungen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories \u201eexplodieren\u201c im Sprint.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Was tun?<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories mit hohem Unsicherheitsgrad als Spike oder Exploration markieren.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erst eine kleine Explorations-Story (z. B. 3 Punkte) umsetzen, Erkenntnisse dokumentieren, dann eigentliche Umsetzung sch\u00e4tzen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Product Owner verpflichtet sich, unklare Stories nicht in den n\u00e4chsten Sprint zu ziehen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5.2 Stories zu gro\u00df lassen<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Epics oder \u201eMonster-Stories\u201c mit 20+ Punkten sind ein Warnsignal.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Probleme:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Blockieren den Sprint.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erschweren Fortschrittsmessung.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erh\u00f6hen Risiko und Unsicherheit.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Regel:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Alles \u00fcber 13 Punkten muss in kleinere Stories geschnitten werden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ziel: Stories so schneiden, dass sie innerhalb eines Sprints sicher abschlie\u00dfbar sind.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Praktische Splitting-Ans\u00e4tze:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>nach Use Cases \/ Varianten<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>nach Schnittstellen \/ Komponenten<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>nach fachlichen Dom\u00e4nen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>nach technischen Schritten (z. B. Backend, Frontend, Migration \u2013 mit Vorsicht)<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5.3 Management misst Teams an Velocity<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Velocity zum Zielwert wird, gehen die Probleme los:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teams erh\u00f6hen Sch\u00e4tzwerte.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sch\u00e4tzungen werden politisch.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Prognose-Qualit\u00e4t sinkt.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Gegenma\u00dfnahmen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Klar kommunizieren: Velocity dient nur zur Selbstplanung des Teams.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>F\u00fcr Management andere Metriken etablieren:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Time-to-Market<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Durchlaufzeit (Lead\/Cycle Time)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Business-Outcomes (z. B. Features, die tats\u00e4chlich genutzt werden)<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5.4 Individuelle Leistung aus Story Points ableiten<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Versuchskonstruktionen wie:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201eEntwickler X macht nur 10 Punkte pro Sprint, Entwickler Y 20 Punkte.\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>sind fachlich unsauber:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points sind Teamma\u00df.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Contribution variiert nach Art der Aufgabe, nicht nur nach \u201eMenge\u201c.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Viele Beitr\u00e4ge (Refinements, Reviews, Pairing, Coaching) sind nicht direkt in Story Points abbildbar.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Besser:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Individuelles Feedback \u00fcber Qualit\u00e4t der Zusammenarbeit, Kommunikation, Ownership.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teamleistung \u00fcber erreichte Sprintziele und Wertbeitrag bewerten, nicht \u00fcber Story Points.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5.5 Sch\u00e4tzaufwand explodiert<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Manche Teams \u201eersticken\u201c im Estimation-Ritual:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>halbt\u00e4gige Planning-Marathons<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Detaildiskussionen \u00fcber jede Kleinigkeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>st\u00e4ndige Re-Sch\u00e4tzungen<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Konsequenz:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Frustration im Team<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wertsch\u00f6pfung leidet<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Akzeptanz von Story Points sinkt<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Empfehlungen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Refinement-Meetings (Backlog Grooming) nutzen, um Stories vor dem Planning zu kl\u00e4ren.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Nur Stories f\u00fcr die n\u00e4chsten 1\u20132 Sprints vollst\u00e4ndig sch\u00e4tzen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Kleinst-Stories (z. B. 0,5\u20131 Punkt) bei Reife des Teams auch mal pauschal behandeln (z. B. alles offensichtlich Kleine = 1 Punkt).<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">6. Praxisleitfaden: So verbessern Sie Ihre Story-Point-Sch\u00e4tzungen kontinuierlich<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Gute Sch\u00e4tzung ist keine einmalige Aktion, sondern ein Lernprozess.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">6.1 Sch\u00e4tz-Review in der Retrospektive<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Nehmen Sie regelm\u00e4\u00dfig 1\u20132 Stories aus dem letzten Sprint in die Retrospektive:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Welche Stories waren deutlich \u00fcber- oder untersch\u00e4tzt?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Welche Annahmen lagen daneben?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Was h\u00e4tte uns vorher auffallen k\u00f6nnen?<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Leitfragen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Haben wir Risiken \u00fcbersehen?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Waren Akzeptanzkriterien unklar?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Haben wir Abh\u00e4ngigkeiten untersch\u00e4tzt?<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ableitungen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sch\u00e4rfung der Referenz-Stories<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erg\u00e4nzung der Sch\u00e4tz-Kriterien<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Anpassung der Definition of Ready<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">6.2 Definition of Ready (DoR) etablieren<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Eine klare DoR verhindert Sch\u00e4tzungen ins Blaue hinein.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>M\u00f6gliche Kriterien f\u00fcr \u201eStory ist sch\u00e4tzbar\u201c:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ziel und Business-Value sind beschrieben.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Akzeptanzkriterien sind definiert.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abh\u00e4ngigkeiten sind benannt.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Auswirkungen auf Architektur\/IT sind grob verstanden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story ist klein genug (z. B. Sch\u00e4tzung &lt; 13 Punkte).<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Stories, die diese Kriterien nicht erf\u00fcllen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>werden nicht gesch\u00e4tzt<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>kommen nicht in den n\u00e4chsten Sprint<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">6.3 Story-Point-Kalibrierung als regelm\u00e4\u00dfigen Termin etablieren<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Gerade in wachsenden oder wechselnden Teams ist es sinnvoll, alle 2\u20133 Monate eine Kalibrierungs-Session durchzuf\u00fchren.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Vorgehen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ol class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>5\u201310 abgeschlossene Stories mit unterschiedlichem Aufwand ausw\u00e4hlen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ohne Blick auf die alten Werte neu sch\u00e4tzen lassen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abweichungen besprechen:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Hat sich unsere Wahrnehmung von \u201e5 Punkten\u201c ver\u00e4ndert?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>M\u00fcssen wir unser Referenz-Set anpassen?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ol>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ziel:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>gemeinsames Mentalmodell stabilisieren<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>neue Teammitglieder integrieren<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">6.4 Von Story Points zu belastbaren Forecasts<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Viele Entscheider fragen: \u201eWann ist Feature X fertig?\u201c oder \u201eWie viele Sprints brauchen wir f\u00fcr dieses Produkt?\u201c<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Pragmatischer Ansatz:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ol class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gesamtumfang grob in Story Points sch\u00e4tzen (Epics in Stories herunterbrechen, aufsummieren).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Mit der durchschnittlichen Velocity des Teams kombinieren:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Beispiel: 200 Story Points Gesamtumfang, durchschnittlich 40 Story Points pro Sprint \u2192 grob 5 Sprints.<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Unsicherheit transparent machen:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Best-Case \/ Worst-Case-Spanne (z. B. basierend auf min.\/max. Velocity der letzten Sprints).<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Regelm\u00e4\u00dfig nachsteuern:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wenn Stories pr\u00e4ziser werden oder neue Erkenntnisse auftauchen, Umfang aktualisieren.<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ol>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">7. Story Points in gemischten Umgebungen (IT, Fachbereich, Dienstleister)<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>In der Praxis arbeiten h\u00e4ufig mehrere Parteien zusammen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>internes IT-Team<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fachbereich<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>externe Dienstleister<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Besonders hier entstehen Missverst\u00e4ndnisse.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">7.1 Erwartungsmanagement mit dem Business<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ma\u00dfnahmen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fr\u00fch und klar erkl\u00e4ren:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Story Points sind keine Stunden.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sch\u00e4tzungen beinhalten auch Risiken und Komplexit\u00e4t.<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Visualisieren, wie aus Story Points realistische Roadmaps entstehen:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Beispiel-Charts zur Velocity-Entwicklung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Forecast-Beispiele mit Spannen<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Empfehlung:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fachbereiche in Refinements teilweise einbeziehen, damit sie den Aufwand und die Diskussionen sehen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">7.2 Zusammenarbeit mit Dienstleistern<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>H\u00e4ufige Stolpersteine:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Dienstleister sch\u00e4tzen in Story Points, werden aber nach Zeit und Material abgerechnet.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Auftraggeber erwarten \u201eharte Zusagen\u201c:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u201e100 Story Points = 50 Personentage\u201c<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Was funktioniert besser?<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Entweder:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Auf Zeitbasis vertraglich arbeiten und Story Points rein intern als Planungswerkzeug nutzen.<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Oder:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Zusammen mit dem Dienstleister ein gemeinsames Verst\u00e4ndnis von Story Points aufbauen, z. B. an gemeinsamen Referenz-Stories.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fixe Zeitbudgets mit flexibler Inhaltssch\u00e4rfung kombinieren (\u201eScope-boxing\u201c statt \u201eTime-boxing\u201c einzelner Stories).<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wichtig:<br class=\"\">Story Points sollten nicht zur versteckten Tagessatz-Verhandlung werden.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">8. Praktische Checklisten: Sind Ihre Story Points gesund?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">8.1 Schnell-Check f\u00fcr Teams<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Beantworten Sie f\u00fcr Ihr Team:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Nutzen wir Story Points prim\u00e4r f\u00fcr:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sprintplanung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Release-Planung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Prognosen mit Unsicherheitskommunikation?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Oder eher f\u00fcr:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Teamvergleiche?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>individuelle Leistungsbewertung?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Management-Reports?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn B: Alarmzeichen. Hier sollten Sie ansetzen.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">8.2 Diagnose typischer Probleme<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Problem: Sprints rei\u00dfen regelm\u00e4\u00dfig die gesetzten Ziele.<br class=\"\">M\u00f6gliche Ursachen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories zu gro\u00df oder zu unklar.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Untersch\u00e4tzte Abh\u00e4ngigkeiten.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Eingriffe von au\u00dfen (Ad-hoc-Tasks).<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ans\u00e4tze:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>DoR sch\u00e4rfen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Puffer f\u00fcr ungeplante Themen vorsehen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Historische Velocity realistischer zur Planung nutzen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Problem: Sch\u00e4tzen dauert ewig.<br class=\"\">M\u00f6gliche Ursachen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stories nicht vorbereitet.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussion driftet in technische Detail-Designs ab.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Kein gemeinsames Verst\u00e4ndnis der Skala.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ans\u00e4tze:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Refinement verbessern, klare Timeboxen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Technik-Diskussionen in separate Architektur-Sessions auslagern.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Referenz-Stories sichtbar machen (z. B. im Planning auf zweitem Bildschirm).<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Problem: Story Points werden \u201eimmer gr\u00f6\u00dfer\u201c.<br class=\"\">M\u00f6gliche Ursachen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Latenter Leistungsdruck.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Velocity wird als Metrik nach oben gemeldet.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Neue Teammitglieder sch\u00e4tzen anders.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ans\u00e4tze:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Klarstellen, dass Velocity kein KPI ist.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Kalibrierungs-Sessions einf\u00fchren.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Offen \u00fcber Druck und Erwartungshaltung sprechen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">9. Konkreter Implementierungsplan f\u00fcr Ihr Unternehmen<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie Story Points neu einf\u00fchren oder \u201eentgiften\u201c wollen, k\u00f6nnen Sie folgenderma\u00dfen vorgehen:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Woche 1\u20132: Analyse und Zielsetzung<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Interviews mit:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Product Ownern<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Team Leads<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Management<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fragen:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wof\u00fcr nutzen wir heute Story Points?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wo entstehen Konflikte?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Welche Entscheidungen sollen in Zukunft besser werden?<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ergebnis: Gemeinsames Zielbild, Entscheid \u00fcber \u201eDo\u2019s &amp; Don\u2019ts\u201c.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Woche 2\u20133: Rahmen setzen<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Schulungs-Workshop f\u00fcr:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Grundlagen Story Points<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Anti-Pattern (Velocity als KPI, Stunden-Umrechnung)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Best Practices<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erarbeiten und dokumentieren:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Referenz-Stories<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Bewertungskriterien<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Skala<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Definition of Ready<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Woche 3\u20136: Pilotierung mit 1\u20132 Teams<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>In ausgew\u00e4hlten Teams:<div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>neue Sch\u00e4tzpraxis in Refinement und Planning umsetzen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sch\u00e4tz-Review in Retrospektiven etablieren<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Management auf Trendbeobachtung einschw\u00f6ren, nicht auf Einzelwerte.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Ab Woche 6: Skalierung und Feintuning<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erfahrungen der Pilotteams aufnehmen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Vorgehen f\u00fcr weitere Teams anpassen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Guidelines im Intranet\/Wiki ver\u00f6ffentlichen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>ggf. interne Community of Practice \u201eAgile Sch\u00e4tzung\u201c aufbauen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h2 class=\"wp-block-heading\">10. Fazit: Story Points als wirksames Werkzeug \u2013 nicht als Selbstzweck<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Richtig eingesetzt, helfen Story Points Ihnen und Ihrem Team, \u2026<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>besser einzusch\u00e4tzen, was in einen Sprint passt<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Risiken fr\u00fch zu erkennen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Vertrauen in Prognosen zu erh\u00f6hen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussionen von Schuld und Rechtfertigung weg hin zu Transparenz und Lernen zu verschieben<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Sie sind jedoch kein Allheilmittel. Entscheidend ist:<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--list\">\n<ul class=\"wp-block-list\"><div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>saubere Einf\u00fchrung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>klare Kommunikation mit Stakeholdern<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>konsequentes Vermeiden typischer Fehlanreize<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie das beherzigen, werden Story Points von der Quelle st\u00e4ndiger Diskussionen zu einem leisen, aber wirksamen Planungswerkzeug.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--separator\">\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie Story Points unternehmensweit sauber etablieren oder in bestehenden Teams \u201eentwirren\u201c m\u00f6chten, lohnt sich oft ein externer Blick. Eine strukturierte Analyse Ihrer aktuellen Sch\u00e4tzpraxis, begleitet von 1\u20132 fokussierten Workshops, kl\u00e4rt typische Missverst\u00e4ndnisse schnell und schafft ein gemeinsames Verst\u00e4ndnis. Die <strong><a href=\"https:\/\/de.linkedin.com\/company\/pcgpureconsultantgmbh\">PURE Consultant<\/a><\/strong> unterst\u00fctzt Sie dabei auf Wunsch mit praxisnaher Beratung, die sich an Ihren Prozessen, Teams und Entscheidungswegen orientiert \u2013 von der ersten Bestandsaufnahme bis zur nachhaltigen Verankerung in Ihrem Projektportfolio.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Story Points sch\u00e4tzen und Fehler vermeiden &#8211; Story Points geh\u00f6ren f\u00fcr viele Teams zum agilen Alltag. Trotzdem k\u00e4mpfen erstaunlich viele Organisationen mit unzuverl\u00e4ssigen Sch\u00e4tzungen, politischen Diskussionen um Velocity und Frust in der Planung. Die gute Nachricht: Die typischen Probleme sind l\u00f6sbar \u2013 wenn Sie Story Points richtig verstehen, konsequent anwenden und ein paar verbreitete Irrt\u00fcmer [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[9],"tags":[3274],"class_list":["post-28821","post","type-post","status-publish","format-standard","hentry","category-scrum","tag-story-points-schaetzen-und-fehler-vermeiden"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant<\/title>\n<meta name=\"description\" content=\"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant\" \/>\n<meta property=\"og:description\" content=\"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/\" \/>\n<meta property=\"og:site_name\" content=\"PURE Consultant\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-01T09:40:21+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-01T09:47:27+00:00\" \/>\n<meta name=\"author\" content=\"Serhat K\u00fcpeli\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Serhat K\u00fcpeli\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"13\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/\"},\"author\":{\"name\":\"Serhat K\u00fcpeli\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#\\\/schema\\\/person\\\/b879d2f247599ce3a636522dd8344e95\"},\"headline\":\"Story Points sch\u00e4tzen und Fehler vermeiden\",\"datePublished\":\"2026-04-01T09:40:21+00:00\",\"dateModified\":\"2026-04-01T09:47:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/\"},\"wordCount\":2387,\"image\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection376.svg\",\"keywords\":[\"Story Points sch\u00e4tzen und Fehler vermeiden\"],\"articleSection\":[\"Scrum\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/\",\"url\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/\",\"name\":\"Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection376.svg\",\"datePublished\":\"2026-04-01T09:40:21+00:00\",\"dateModified\":\"2026-04-01T09:47:27+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#\\\/schema\\\/person\\\/b879d2f247599ce3a636522dd8344e95\"},\"description\":\"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection376.svg\",\"contentUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection376.svg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/story-points-schaetzen-und-fehler-vermeiden\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Story Points sch\u00e4tzen und Fehler vermeiden\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#website\",\"url\":\"https:\\\/\\\/www.pureconsultant.de\\\/\",\"name\":\"PURE Consultant\",\"description\":\"Scrum, PMO, Projektmanagement &amp; Prozessmanagement aus K\u00f6ln\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.pureconsultant.de\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#\\\/schema\\\/person\\\/b879d2f247599ce3a636522dd8344e95\",\"name\":\"Serhat K\u00fcpeli\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g\",\"caption\":\"Serhat K\u00fcpeli\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant","description":"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/","og_locale":"de_DE","og_type":"article","og_title":"Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant","og_description":"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!","og_url":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/","og_site_name":"PURE Consultant","article_published_time":"2026-04-01T09:40:21+00:00","article_modified_time":"2026-04-01T09:47:27+00:00","author":"Serhat K\u00fcpeli","twitter_card":"summary_large_image","twitter_misc":{"Verfasst von":"Serhat K\u00fcpeli","Gesch\u00e4tzte Lesezeit":"13\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#article","isPartOf":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/"},"author":{"name":"Serhat K\u00fcpeli","@id":"https:\/\/www.pureconsultant.de\/#\/schema\/person\/b879d2f247599ce3a636522dd8344e95"},"headline":"Story Points sch\u00e4tzen und Fehler vermeiden","datePublished":"2026-04-01T09:40:21+00:00","dateModified":"2026-04-01T09:47:27+00:00","mainEntityOfPage":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/"},"wordCount":2387,"image":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#primaryimage"},"thumbnailUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection376.svg","keywords":["Story Points sch\u00e4tzen und Fehler vermeiden"],"articleSection":["Scrum"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/","url":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/","name":"Story Points sch\u00e4tzen und Fehler vermeiden - PURE Consultant","isPartOf":{"@id":"https:\/\/www.pureconsultant.de\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#primaryimage"},"image":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#primaryimage"},"thumbnailUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection376.svg","datePublished":"2026-04-01T09:40:21+00:00","dateModified":"2026-04-01T09:47:27+00:00","author":{"@id":"https:\/\/www.pureconsultant.de\/#\/schema\/person\/b879d2f247599ce3a636522dd8344e95"},"description":"Verbessere dein Teamwork: Story Points sch\u00e4tzen und Fehler vermeiden leicht gemacht. Optimiere deine Prozesse \u2013 starte noch heute!","breadcrumb":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#primaryimage","url":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection376.svg","contentUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection376.svg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/story-points-schaetzen-und-fehler-vermeiden\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.pureconsultant.de\/de\/"},{"@type":"ListItem","position":2,"name":"Story Points sch\u00e4tzen und Fehler vermeiden"}]},{"@type":"WebSite","@id":"https:\/\/www.pureconsultant.de\/#website","url":"https:\/\/www.pureconsultant.de\/","name":"PURE Consultant","description":"Scrum, PMO, Projektmanagement &amp; Prozessmanagement aus K\u00f6ln","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.pureconsultant.de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Person","@id":"https:\/\/www.pureconsultant.de\/#\/schema\/person\/b879d2f247599ce3a636522dd8344e95","name":"Serhat K\u00fcpeli","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0886d2e74e7dfa20a0d9157eed001ec6efc4a799c718c80d37ebd532ec3810f1?s=96&d=mm&r=g","caption":"Serhat K\u00fcpeli"}}]}},"_links":{"self":[{"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts\/28821","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/comments?post=28821"}],"version-history":[{"count":2,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts\/28821\/revisions"}],"predecessor-version":[{"id":28824,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts\/28821\/revisions\/28824"}],"wp:attachment":[{"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/media?parent=28821"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/categories?post=28821"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/tags?post=28821"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}