{"id":27183,"date":"2026-01-28T15:40:57","date_gmt":"2026-01-28T14:40:57","guid":{"rendered":"https:\/\/www.pureconsultant.de\/de\/?p=27183"},"modified":"2026-01-28T15:41:08","modified_gmt":"2026-01-28T14:41:08","slug":"burndown-vs-burnup","status":"publish","type":"post","link":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/","title":{"rendered":"Burndown vs. Burnup"},"content":{"rendered":"<div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Burndown vs. Burnup &#8211; In agilen Projekten geh\u00f6rt der Blick aufs Board zum Alltag \u2013 doch viele Teams k\u00e4mpfen damit, Fortschritt wirklich transparent zu machen. Burndown- und Burnup-Charts gelten als Standard, werden aber oft falsch verstanden oder nur halbherzig genutzt. Die Folge: Sch\u00f6nf\u00e4rberei, Missverst\u00e4ndnisse im Management und schlechte Entscheidungen.<br>Dieser Artikel erkl\u00e4rt praxisnah, worin sich <strong><a href=\"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-chart\/\">Burndown<\/a><\/strong> vs. <strong><a href=\"https:\/\/www.pureconsultant.de\/de\/agile\/burnup-chart\/\">Burnup<\/a><\/strong> unterscheiden, wie Sie beide Diagrammtypen korrekt lesen, welche Fehler Sie vermeiden sollten und in welchen Situationen welches Chart deutlich im Vorteil ist. So schaffen Sie eine belastbare Datengrundlage f\u00fcr Steuerung, Prognosen und Stakeholder-Kommunikation.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--image\">\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"624\" height=\"708\" src=\"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png\" alt=\"Burndown vs. Burnup\" class=\"wp-image-27185\" srcset=\"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png 624w, https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324-35x40.png 35w\" sizes=\"auto, (max-width: 624px) 100vw, 624px\" \/><figcaption class=\"wp-element-caption\">Burndown vs. Burnup<\/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\">Was ist ein Burndown Chart? \u2013 Kurz erkl\u00e4rt<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ein Burndown Chart zeigt, wie viel Arbeit in einem definierten Zeitraum noch \u00fcbrig ist.<br class=\"\">Auf der y-Achse steht der verbleibende Aufwand (z.\u202fB. Story Points, Stunden), auf der x-Achse die Zeit (z.\u202fB. Tage im Sprint).<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">Kernelemente eines Burndown Charts:<\/strong><\/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>Startpunkt: Gesamtaufwand zu Beginn (z.\u202fB. Sprintstart)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ideallinie: theoretisch gleichm\u00e4\u00dfiger Abbau der Arbeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Ist-Linie: tats\u00e4chlicher Fortschritt im Zeitverlauf<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Endpunkt: null verbleibender Aufwand = alles erledigt<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Damit beantwortet das Burndown die Frage: \u201eWie viel Arbeit m\u00fcssen wir noch erledigen, um rechtzeitig fertig zu werden?\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<h2 class=\"wp-block-heading\">Was ist ein Burnup Chart? \u2013 Kurz erkl\u00e4rt<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Ein Burnup Chart zeigt, wie viel Arbeit bereits erledigt wurde \u2013 und wie sich der Gesamtumfang entwickelt.<br class=\"\">Auf der y-Achse stehen erledigter Aufwand und Gesamtumfang, auf der x-Achse die Zeit.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">Kernelemente eines Burnup Charts:<\/strong><\/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>Linie \u201eScope\u201c: aktueller Gesamtumfang (kann steigen oder fallen)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Linie \u201eDone\u201c: kumuliert erledigte Arbeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abstand zwischen beiden Linien: noch offene Arbeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Schnittpunkt: Zeitpunkt, an dem der erledigte Aufwand den Scope erreicht<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Damit beantwortet das Burnup die Frage: \u201eWie entwickelt sich unser Fortschritt im Verh\u00e4ltnis zu einem sich ver\u00e4ndernden Umfang?\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<h2 class=\"wp-block-heading\">Burndown vs. Burnup: Der zentrale Unterschied<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Der Kernunterschied:<\/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><strong class=\"\">Burndown<\/strong> fokussiert auf die <strong class=\"\">Restarbeit<\/strong>,<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Burnup<\/strong> auf die <strong class=\"\">geleistete Arbeit im Kontext des Umfangs<\/strong>.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Die praktische 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>Im <strong class=\"\">Burndown<\/strong> ist oft nicht sofort sichtbar, ob sich der Umfang ver\u00e4ndert hat.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Im <strong class=\"\">Burnup<\/strong> erkennt man Scope-\u00c4nderungen direkt als Verschiebung der Umfangslinie.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Gerade in dynamischen Projekten mit h\u00e4ufigen \u00c4nderungen im Backlog ist das Burnup daher oft die aussagekr\u00e4ftigere Wahl.<\/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\">Wie liest man ein Burndown Chart richtig?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Achsen und Linien verstehen<\/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><strong class=\"\">X-Achse (Zeit):<\/strong> Sprinttage, Iterationen oder Kalendertage.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Y-Achse (Aufwand):<\/strong> z.\u202fB. Story Points, Tickets, Personentage.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Ideallinie:<\/strong> \u201eLeitplanke\u201c f\u00fcr einen gleichm\u00e4\u00dfigen Abbau.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Ist-Linie:<\/strong> realer Verlauf, meist zackig, da Arbeit oft in Bl\u00f6cken fertig wird.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Typische Muster im Burndown<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">1. \u201eWasserfall\u201c-Muster (lange flach, dann steiler Absturz)<\/strong><\/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>Deutet oft auf \u201ealles am Ende fertig\u201c hin<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Risiko: sp\u00e4te Erkenntnis, wenn etwas nicht klappt<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>M\u00f6gliche Ursache: Arbeiten werden erst sp\u00e4t abgenommen oder zerlegt<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">2. Stagnation \u00fcber mehrere Tage<\/strong><\/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>Kaum Tickets werden \u201eDone\u201c<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>M\u00f6gliche Ursachen:<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>Blocker, Abh\u00e4ngigkeiten, fehlende Entscheidungen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Zu gro\u00dfe User Stories, mangelnde Zerlegung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Team ist mit Nebenarbeit besch\u00e4ftigt, die nicht im Sprint Backlog steckt<\/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><strong class=\"\">3. Unter der Ideallinie<\/strong><\/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>Team ist dem Plan voraus<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Vorsicht: Pr\u00fcfen, ob Definition of Done wirklich eingehalten wird<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">4. \u00dcber der Ideallinie<\/strong><\/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>Verzug gegen\u00fcber dem Plan<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erfordert Transparenz: Was hindert das Team, was muss gekl\u00e4rt werden?<\/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\">Wie liest man ein Burnup Chart richtig?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Aufbau des Burnup<\/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><strong class=\"\">Linie \u201eScope\u201c (Gesamtumfang)<\/strong><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>Zeigt die aktuelle Gesamtmenge der geplanten Arbeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Steigt bei neuen Anforderungen, sinkt bei Scope-Reduktion<\/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><strong class=\"\">Linie \u201eDone\u201c (erledigt)<\/strong><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>Kumulierte Summe der fertiggestellten Arbeit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Steigt mit jeder abgeschlossenen User Story oder jedem Ticket<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Typische Muster im Burnup<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">1. Done-Linie steigt, Scope bleibt stabil<\/strong><\/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>Klassischer, gut \u201ekontrollierter\u201c Verlauf<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Fortschritt ist klar und Prognosen sind relativ stabil<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">2. Done-Linie steigt, Scope steigt ebenfalls<\/strong><\/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>Team liefert, aber die Anforderungen wachsen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Aussage: \u201eWir arbeiten konstant, aber das Ziel entfernt sich.\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">3. Kaum Anstieg der Done-Linie<\/strong><\/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>\u00c4hnlich wie beim Burndown: Blocker, falscher Fokus oder \u00dcberlastung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Im Burnup ist zugleich sichtbar, ob parallel der Umfang erh\u00f6ht wurde<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">4. Umfang sinkt<\/strong><\/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>Scope wird reduziert, z.\u202fB. durch Priorisierung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erm\u00f6glicht bewusste Entscheidungen: \u201eWir streichen Features, um den Termin zu halten.\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<h2 class=\"wp-block-heading\">Vor- und Nachteile: Burndown Chart<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Vorteile des Burndown<\/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>Einfach zu verstehen f\u00fcr Einsteiger<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gut geeignet f\u00fcr <strong class=\"\">kurze, klar abgegrenzte Sprints<\/strong><\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Schneller Blick: \u201eSind wir im Sprint im Plan?\u201c<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Nachteile des Burndown<\/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><strong class=\"\">Scope-\u00c4nderungen sind schwer erkennbar<\/strong><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 w\u00e4hrend des Sprints Arbeit hinzugef\u00fcgt oder entfernt wird, verschiebt sich die Startmenge \u2013 die Visualisierung kann irref\u00fchrend werden.<\/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>Gefahr der Fehlinterpretation:<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>Ein schlechtes Burndown kann als \u201eTeam arbeitet nicht\u201c gelesen werden, obwohl eigentlich der Umfang gestiegen ist.<\/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>Fokussiert stark auf \u201eRestarbeit\u201c statt auf \u201egeleistete Leistung\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>F\u00fcr Management und Stakeholder ist die positive Sicht (\u201eWas ist geschafft?\u201c) oft hilfreicher.<\/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<h2 class=\"wp-block-heading\">Vor- und Nachteile: Burnup Chart<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Vorteile des Burnup<\/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><strong class=\"\">Transparenz bei Scope-\u00c4nderungen<\/strong><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>Umfangs\u00e4nderungen werden explizit als Verschiebung der Scope-Linie sichtbar.<\/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><strong class=\"\">Gute Basis f\u00fcr Prognosen<\/strong><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>Aus der Steigung der Done-Linie kann man die durchschnittliche Liefergeschwindigkeit (Velocity) ableiten.<\/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><strong class=\"\">St\u00e4rkerer Fokus auf Wertsch\u00f6pfung<\/strong><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>Diskussion dreht sich mehr um \u201eWas haben wir geliefert?\u201c als um \u201eWie viel fehlt noch?\u201c.<\/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>Besser geeignet f\u00fcr <strong class=\"\">l\u00e4nger laufende Initiativen<\/strong> und Produkte mit sich entwickelnden Backlogs.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Nachteile des Burnup<\/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>F\u00fcr Einsteiger visuell etwas komplexer als ein Burndown<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Erfordert saubere Pflege des Scope (inkl. Dokumentation von \u00c4nderungen)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wenn mehrere Teams an einem gemeinsamen Scope arbeiten, muss die Aggregation klar geregelt sein<\/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\">Burndown vs. Burnup: Wann eignet sich welches Diagramm?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Burndown ist besonders sinnvoll, wenn \u2026<\/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>Sie <strong class=\"\">kurze Sprints<\/strong> mit stabiler Planung fahren<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>der Umfang w\u00e4hrend des Sprints nur in Ausnahmef\u00e4llen ge\u00e4ndert wird<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sie eine einfache Darstellung f\u00fcr das <strong class=\"\">t\u00e4gliche Stand-up<\/strong> ben\u00f6tigen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>das Team erst mit Visualisierung beginnt und Komplexit\u00e4t gering halten m\u00f6chte<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Burnup ist besonders sinnvoll, wenn \u2026<\/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>Sie <strong class=\"\">l\u00e4ngerfristige Produktentwicklungen oder Programme<\/strong> steuern<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>laufend neue Anforderungen entstehen oder Priorit\u00e4ten sich ver\u00e4ndern<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Management und Stakeholder <strong class=\"\">Scope-\u00c4nderungen klar nachvollziehen<\/strong> sollen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sie seri\u00f6se <strong class=\"\">Forecasts<\/strong> auf Basis von Velocity und Trends erstellen wollen<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Praxisempfehlung<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Viele Organisationen nutzen:<\/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><strong class=\"\">Burndown<\/strong>: f\u00fcr die <strong class=\"\">Sprint-Sicht<\/strong> im Team<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Burnup<\/strong>: f\u00fcr die <strong class=\"\">\u00fcbergeordnete Produkt- und Release-Sicht<\/strong> im Management<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>So kombinieren Sie operative Transparenz mit strategischer Steuerung.<\/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\">Wichtige W\u2011Fragen zu Burndown und Burnup<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Warum \u00fcberhaupt Burndown oder Burnup nutzen?<\/h3>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Weil beide Diagrammtypen helfen, typische Blindspots zu vermeiden:<\/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>Unrealistische \u201eGef\u00fchlsprognosen\u201c (\u201eWir schaffen das schon irgendwie\u201c)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>\u00dcberraschungen am Ende des Sprints oder Releases<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Diskussionen ohne gemeinsame Datengrundlage<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Wer sollte die Charts nutzen?<\/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><strong class=\"\">Product Owner \/ Product Manager<\/strong>: f\u00fcr Priorisierung und Stakeholder-Dialog<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Scrum Master \/ Agile Coaches<\/strong>: f\u00fcr kontinuierliche Verbesserung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Teammitglieder<\/strong>: f\u00fcr t\u00e4gliche Selbststeuerung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">F\u00fchrungskr\u00e4fte<\/strong>: f\u00fcr Statusberichte und Portfolio-Entscheidungen<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Wie oft sollte man auf die Charts schauen?<\/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>Im <strong class=\"\">Daily<\/strong>: kurzer Blick auf das aktuelle Sprint-Burndown<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>In <strong class=\"\">Review\/Review-\u00e4hnlichen Terminen<\/strong>: Blick auf Burnup\/Release-Sicht<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>In <strong class=\"\">Steuerungsrunden \/ Management-Meetings<\/strong>: Burnup als Grundlage f\u00fcr Entscheidungen<\/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\">Burndown vs. Burnup in Scrum, Kanban und hybriden Setups<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">In Scrum<\/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>Sprints haben einen klaren Zeithorizont, daher:<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><strong class=\"\">Sprint-Burndown<\/strong>: Fortschritt innerhalb eines Sprints<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li><strong class=\"\">Release-Burnup<\/strong>: Fortschritt \u00fcber mehrere Sprints hinweg<\/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>So wird die kurzfristige Sprintplanung mit der l\u00e4ngerfristigen Roadmap verbunden.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">In Kanban<\/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>Kanban arbeitet eher <strong class=\"\">flussorientiert<\/strong> ohne feste Sprints.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Hier ist ein <strong class=\"\">Burnup<\/strong> meist hilfreicher, etwa 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>Messung von Durchsatz (Throughput)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Visualisierung, wie sich Umfang und Liefermenge \u00fcber Zeit entwickeln<\/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>Ein klassisches Burndown passt weniger gut zu kontinuierlichem Flow ohne Sprintgrenzen.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">In hybriden Modellen (z.\u202fB. SAFe, LeSS, Projekt + Produktmix)<\/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>Burndown auf Team- oder Iterationsebene<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Burnup 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>Program Increment (PI)-Planung<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gesamtprojekt-Fortschritt<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Multiprojekt- oder Portfolio-Sicht<\/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<h2 class=\"wp-block-heading\">Typische Fehler im Umgang mit Burndown und Burnup<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">1. Charts als \u201eKontrollinstrument\u201c statt Lerninstrument nutzen<\/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>Nur auf \u201erote\u201c Verl\u00e4ufe zu schauen und Druck zu erh\u00f6hen, f\u00fchrt zu:<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\u00f6nf\u00e4rben von Daten<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Widerstand im Team<\/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>Besser: Diagramme als Ausgangspunkt f\u00fcr <strong class=\"\">Ursachenanalyse und Verbesserungen<\/strong> verwenden.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">2. Unklare Definition of Done<\/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>Wenn \u201eDone\u201c unterschiedlich interpretiert wird, sind Charts wertlos.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Stellen Sie sicher:<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>Gemeinsame, dokumentierte Definition of Done<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Strenge Anwendung im gesamten Team<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">3. Scope-\u00c4nderungen nicht sauber pflegen<\/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>Arbeitsumfang wird nachtr\u00e4glich ver\u00e4ndert, ohne ihn zu dokumentieren.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Besonders kritisch im Burndown, aber auch im Burnup.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Empfehlung:<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>Scope-\u00c4nderungen explizit festhalten<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Im Burnup sichtbar machen<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Im Sprint-Burndown zumindest im Daily ansprechen<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">4. Zu grobe User Stories<\/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>Wenige gro\u00dfe Stories f\u00fchren zu:<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>Flachem Verlauf, dann pl\u00f6tzlichem Absturz<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Schlechter Aussagekraft der Diagramme<\/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>L\u00f6sung:<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 in kleinteiligere, klar abgrenzbare Arbeitseinheiten zerlegen<\/li>\n<\/div><\/ul>\n<\/div><\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">5. Fehlende Verkn\u00fcpfung mit Entscheidungen<\/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>Charts werden zwar erzeugt, aber:<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>Niemand leitet Ma\u00dfnahmen ab<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Keine Anpassung von Scope, Priorit\u00e4ten oder Arbeitsweise<\/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>Achten Sie darauf, aus Mustern konkrete Schritte abzuleiten.<\/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\">Aufwandseinheiten: Story Points, Stunden oder Tickets?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Story Points<\/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>H\u00e4ufigste Einheit in Scrum-Teams<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Abstrakte Gr\u00f6\u00dfe (Komplexit\u00e4t, Risiko, Umfang)<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gut geeignet, um Velocity und Trends im Burnup zu analysieren<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Stunden oder Personentage<\/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>Wirken f\u00fcr Management oft intuitiver<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Gefahr: R\u00fcckfall in Mikromanagement und Scheinpr\u00e4zision<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Eher f\u00fcr Teams sinnvoll, die noch stark in klassischem Projektcontrolling verankert sind<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--heading\">\n<h3 class=\"wp-block-heading\">Anzahl Tickets<\/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>Einfachste Z\u00e4hleinheit<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Funktioniert gut, wenn Tickets relativ homogen und klein sind<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>F\u00fcr sehr unterschiedliche Ticketgr\u00f6\u00dfen weniger aussagekr\u00e4ftig<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">Empfehlung:<\/strong><br class=\"\">F\u00fcr agile Produktentwicklung in stabilen Teams sind <strong class=\"\">Story Points plus Burnup<\/strong> eine bew\u00e4hrte Kombination. In eher klassischen Projektumgebungen kann ein <strong class=\"\">stundenbasiertes Burndown<\/strong> als Einstieg helfen.<\/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\">Schritt-f\u00fcr-Schritt: Einf\u00fchrung von Burndown und Burnup in Ihrem Team<\/h2>\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><strong class=\"\">Ziel kl\u00e4ren<\/strong><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>Was wollen Sie mit den Diagrammen erreichen?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Z.\u202fB. bessere Sprint-Prognosen, transparentere Scope-\u00c4nderungen, fundiertere Management-Entscheidungen.<\/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><strong class=\"\">Einheit w\u00e4hlen<\/strong><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, Stunden oder Tickets \u2013 bewusst entscheiden, nicht zuf\u00e4llig.<\/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><strong class=\"\">Definition of Done festlegen oder sch\u00e4rfen<\/strong><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>Einigkeit herstellen, wann eine Arbeitseinheit wirklich \u201eDone\u201c ist.<\/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><strong class=\"\">Tooling aufsetzen<\/strong><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 vielen Tools (z.\u202fB. Jira, Azure DevOps, Trello-Erweiterungen) lassen sich Burndown und Burnup automatisiert erzeugen.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wichtig: Konfiguration pr\u00fcfen, damit die Diagramme die Realit\u00e4t widerspiegeln.<\/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><strong class=\"\">Regelm\u00e4\u00dfige Nutzung verankern<\/strong><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>Burndown: fester Bestandteil im Daily (max. 2\u20133 Minuten).<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Burnup: Bestandteil von Review, Planning, Steuerungsgremien.<\/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><strong class=\"\">Gemeinsame Interpretation ein\u00fcben<\/strong><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>Im Team und mit Stakeholdern regelm\u00e4\u00dfig 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>Was sehen wir?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Was bedeutet das?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Welche Anpassungen folgen daraus?<\/li>\n<\/div><\/ul>\n<\/div><\/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><strong class=\"\">Feedback einholen und nachjustieren<\/strong><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>Sind die Diagramme hilfreich?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>M\u00fcssen Einheiten, Granularit\u00e4t oder Meeting-Strukturen angepasst werden?<\/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\">Burndown vs. Burnup: Welche Fragen beantwortet welches Chart besser?<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">Burndown beantwortet vor allem:<\/strong><\/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>Wie viel Arbeit ist im Sprint noch offen?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Sind wir innerhalb dieses Sprints im Plan?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>M\u00fcssen wir kurzfristig umpriorisieren, um das Sprintziel zu erreichen?<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p><strong class=\"\">Burnup beantwortet vor allem:<\/strong><\/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>Wie viel haben wir bereits geliefert?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wie ver\u00e4ndert sich der Gesamtumfang \u00fcber die Zeit?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Wann k\u00f6nnen wir voraussichtlich ein Release oder Zielpaket abschlie\u00dfen, wenn wir mit der aktuellen Geschwindigkeit weitermachen?<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Welche Auswirkungen haben neue Anforderungen auf unsere Liefertermine?<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie sich zwischen Burndown vs. Burnup entscheiden m\u00fcssen, sollten diese Fragen den Ausschlag geben. F\u00fcr die meisten professionellen Umgebungen lohnt sich jedoch der kombinierte Einsatz.<\/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\">Fazit: Burndown vs. Burnup bewusst kombinieren<\/h2>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Burndown- und Burnup-Charts sind keine Selbstzweck-Grafiken, sondern Werkzeuge f\u00fcr bessere Entscheidungen.<\/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 Sie das <strong class=\"\">Burndown<\/strong>, um in \u00fcberschaubaren Sprints die t\u00e4gliche Arbeit zu steuern.<\/li>\n<\/div>\n\n<div class=\"m-block--container u-offset m-block--core--list-item\">\n<li>Nutzen Sie das <strong class=\"\">Burnup<\/strong>, um \u00fcbergreifend Transparenz \u00fcber Fortschritt, Scope-\u00c4nderungen und realistische Liefertermine zu schaffen.<\/li>\n<\/div><\/ul>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Entscheidend ist nicht das \u201eperfekte\u201c Diagramm, sondern ein <strong class=\"\">gemeinsames Verst\u00e4ndnis<\/strong> im Team und mit <strong><a href=\"https:\/\/www.pureconsultant.de\/de\/projektmanagement\/stakeholder\" type=\"post\" id=\"26374\">Stakeholdern<\/a><\/strong>, was die Daten bedeuten \u2013 und welche Konsequenzen Sie daraus ziehen.<\/p>\n<\/div><div class=\"m-block--container u-offset m-block--core--paragraph\">\n<p>Wenn Sie Unterst\u00fctzung bei der Einf\u00fchrung einer belastbaren Fortschrittsmessung, beim Aufsetzen sinnvoller Burndown- und Burnup-Charts oder bei der agilen Skalierung in komplexen Organisationen w\u00fcnschen, kann eine externe Perspektive helfen. Die Beraterinnen und Berater von <strong><a href=\"https:\/\/de.linkedin.com\/company\/pcgpureconsultantgmbh\">PURE Consultant<\/a><\/strong> begleiten Sie dabei, passende Metriken und Visualisierungen f\u00fcr Ihre konkrete Situation zu definieren und nachhaltig in Ihrer Organisation zu verankern.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Burndown vs. Burnup &#8211; In agilen Projekten geh\u00f6rt der Blick aufs Board zum Alltag \u2013 doch viele Teams k\u00e4mpfen damit, Fortschritt wirklich transparent zu machen. Burndown- und Burnup-Charts gelten als Standard, werden aber oft falsch verstanden oder nur halbherzig genutzt. Die Folge: Sch\u00f6nf\u00e4rberei, Missverst\u00e4ndnisse im Management und schlechte Entscheidungen.Dieser Artikel erkl\u00e4rt praxisnah, worin sich Burndown [&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":[2887],"class_list":["post-27183","post","type-post","status-publish","format-standard","hentry","category-scrum","tag-burndown-vs-burnup"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Burndown vs. Burnup - PURE Consultant<\/title>\n<meta name=\"description\" content=\"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!\" \/>\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\/burndown-vs-burnup\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Burndown vs. Burnup - PURE Consultant\" \/>\n<meta property=\"og:description\" content=\"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/\" \/>\n<meta property=\"og:site_name\" content=\"PURE Consultant\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-28T14:40:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-28T14:41:08+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png\" \/>\n\t<meta property=\"og:image:width\" content=\"624\" \/>\n\t<meta property=\"og:image:height\" content=\"708\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\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=\"10\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\\\/burndown-vs-burnup\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/\"},\"author\":{\"name\":\"Serhat K\u00fcpeli\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#\\\/schema\\\/person\\\/b879d2f247599ce3a636522dd8344e95\"},\"headline\":\"Burndown vs. Burnup\",\"datePublished\":\"2026-01-28T14:40:57+00:00\",\"dateModified\":\"2026-01-28T14:41:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/\"},\"wordCount\":1866,\"image\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection324.png\",\"keywords\":[\"Burndown vs. Burnup\"],\"articleSection\":[\"Scrum\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/\",\"url\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/\",\"name\":\"Burndown vs. Burnup - PURE Consultant\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection324.png\",\"datePublished\":\"2026-01-28T14:40:57+00:00\",\"dateModified\":\"2026-01-28T14:41:08+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/#\\\/schema\\\/person\\\/b879d2f247599ce3a636522dd8344e95\"},\"description\":\"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection324.png\",\"contentUrl\":\"https:\\\/\\\/www.pureconsultant.de\\\/wp-content\\\/uploads\\\/visual-selection324.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/scrum\\\/burndown-vs-burnup\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\\\/\\\/www.pureconsultant.de\\\/de\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Burndown vs. Burnup\"}]},{\"@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":"Burndown vs. Burnup - PURE Consultant","description":"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!","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\/burndown-vs-burnup\/","og_locale":"de_DE","og_type":"article","og_title":"Burndown vs. Burnup - PURE Consultant","og_description":"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!","og_url":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/","og_site_name":"PURE Consultant","article_published_time":"2026-01-28T14:40:57+00:00","article_modified_time":"2026-01-28T14:41:08+00:00","og_image":[{"width":624,"height":708,"url":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png","type":"image\/png"}],"author":"Serhat K\u00fcpeli","twitter_card":"summary_large_image","twitter_misc":{"Verfasst von":"Serhat K\u00fcpeli","Gesch\u00e4tzte Lesezeit":"10\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#article","isPartOf":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/"},"author":{"name":"Serhat K\u00fcpeli","@id":"https:\/\/www.pureconsultant.de\/#\/schema\/person\/b879d2f247599ce3a636522dd8344e95"},"headline":"Burndown vs. Burnup","datePublished":"2026-01-28T14:40:57+00:00","dateModified":"2026-01-28T14:41:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/"},"wordCount":1866,"image":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png","keywords":["Burndown vs. Burnup"],"articleSection":["Scrum"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/","url":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/","name":"Burndown vs. Burnup - PURE Consultant","isPartOf":{"@id":"https:\/\/www.pureconsultant.de\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#primaryimage"},"image":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png","datePublished":"2026-01-28T14:40:57+00:00","dateModified":"2026-01-28T14:41:08+00:00","author":{"@id":"https:\/\/www.pureconsultant.de\/#\/schema\/person\/b879d2f247599ce3a636522dd8344e95"},"description":"Burndown vs. Burnup erkl\u00e4rt: Finde heraus, welche Methode dein Team schneller ans Ziel bringt. Starte jetzt durch mit smarter Planung!","breadcrumb":{"@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#primaryimage","url":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png","contentUrl":"https:\/\/www.pureconsultant.de\/wp-content\/uploads\/visual-selection324.png"},{"@type":"BreadcrumbList","@id":"https:\/\/www.pureconsultant.de\/de\/scrum\/burndown-vs-burnup\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.pureconsultant.de\/de\/"},{"@type":"ListItem","position":2,"name":"Burndown vs. Burnup"}]},{"@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\/27183","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=27183"}],"version-history":[{"count":2,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts\/27183\/revisions"}],"predecessor-version":[{"id":27186,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/posts\/27183\/revisions\/27186"}],"wp:attachment":[{"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/media?parent=27183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/categories?post=27183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pureconsultant.de\/de\/wp-json\/wp\/v2\/tags?post=27183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}