03 agile transformer pack - mpirics€¦ · implementing scrum & agile development daniel...

2
03 AGILE TRANSFORMER PACK

Upload: others

Post on 05-Jun-2020

14 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 03 AGILE TRANSFORMER PACK - mpirics€¦ · Implementing Scrum & Agile Development Daniel Haslinger, MSc is a Certified Scrum Trainer™ (CST) of the Scrum Alliance and has collected

03 AGILE TRANSFORMER PACK

Page 2: 03 AGILE TRANSFORMER PACK - mpirics€¦ · Implementing Scrum & Agile Development Daniel Haslinger, MSc is a Certified Scrum Trainer™ (CST) of the Scrum Alliance and has collected

Culture Hacking Implementing Scrum & Agile Development

Daniel Haslinger, MSc is a Certified Scrum Trainer™ (CST) of the Scrum Alliance and has collected many years of experience with Scrum. In the last cou-ple of years, Daniel has intensively dealt with agile software development and worked as developer, consultant and coach actively in Scrum projects, as well as Scrum Master and Product Owner. He also holds the certification as SAFe Program Consultant. As an agile Coach he helped several organizations with the introduction of agile methods like Scrum, from small Startups to major enter-prises. Through training and catalyst coaching and consulting Daniel helps companies with their agile transformation and brings in his rich experience from many previous projects. Daniel professionally develops software now for over 10 years in the field of Java. He intensively deals with agile practices and helps development teams to apply these successfully and use them for continuous improvement.

Dr. Andreas Wintersteiger is a Certified Scrum Trainer™ (CST) and Certified Enterprise Coach™ (CEC, formerly known as CSC) from Scrum Alliance and a Certified SAFe™ Program Consultant (SPC). He is a computer scientist with more than 25 years of experience and has been prac-ticing Agile for more than 15 years now, since the term “Agile” was coined. Together with his team at Objectbay, he has helped major organizations worldwide to implement Scrum and agile practices in more than 70 cases from startups to SMEs to multina-tional corporations. He is the author of three books, this white paper is an extract from his latest book “Scrum: Your definitive Guide to Success” (2016).

Like with the implementation of any other type of process model, there are also several options to implementing Scrum, which can be combined with each other even.

Firstly, there is the simple “Roll-Out model”, in which a Scrum pilot project is started to gain experience. Typical-ly, organizations focus all their attention on this and evaluate the effect of Scrum in their company based on this pilot. In many cases however, this is only of limited significance since pilot projects are often somewhat unrealis-tic. Plus, as is often seen, a pilot project is too critical to be typical. Nevertheless, after a period of approximately three to six months roll out starts to occur with other teams, organizational units or products or projects. In this model Scrum will always bring forth the problems at the interfaces between old and new. The rollout is therefore "accelerated" through experience from the inside out.

The “Big Bang” is the second option, opposed to the first one. Here, the whole organization will be suddenly changed with an effective date to apply Scrum. All affected teams start their first sprint on the same day. With the Big Bang approach typically upfront experiences of coaches are required in the practical implementation of Scrum which is also necessary, because in this variant much more is at stake. The preparation for this scenario is more complex, since it is even started at a scaled level.

Note: Many teams start in pilot mode as a "submarine" - that is, initially invisible to management. However, in understanding the mechanism of Scrum, this approach generally discouraged. We advise you to do a top-down approach with the earliest possible involvement of management - Scrum is indeed a framework for change management, and for changes to occur in management commitment will be necessary.

© Copyright 2016 Objectbay Group. All rights reserved.

Product Backlog Refurbishment

Eine gute Scrum Implementierung steht und fällt mit einem sauber gepflegten Product Backlog. Die Inhalte des Product Backlogs beschreiben künftige Lieferungen auf eine Art und Weise, die klare Ziele für Entwicklungsteams absteckt und gleichzeitig durch gekonnte Priorisierung den Produkterfolg maßgeblich steuert.

In unseren langjährigen Tätigkeit als Berater und Coaches mussten wir immer wieder feststellen, dass viele der Probleme die in agilen Organisationen vorherrschen auf das Product Backlog zurück zu führen sind, auch wenn dies auf den ersten Blick oft nicht so scheint.

In unserem eintägigen Product Backlog Refurbishment arbeitet einer unserer Experten einen ganzen Tag lang mit Ihnen bzw. Ihrem Product Owner an der Verbesserung Ihres Product Backlogs.

Gesteigerter ROI

Um den wirtschaftlichen Erfolg eines Entwicklungsvorhabens zu steuern müssen Prioritäten gesetzt werden. Wir zeigen Ihnen diverse Werkzeuge, die Ihnen bei der Priorisierung helfen können und wenden diese gleich direkt auf Ihr aktuelles Product Backlog

Backlog Refinement mit dem Team

Mit Hilfe von Product Backlog Items, für deren Formulierung häufig “User Stories” verwendet werden, werden Anforderungen ins Team transportiert. Je besser die Teammitglieder verstehen, was die Lieferung enthalten soll, desto besser und motivierter werden Sie an der Umsetzung arbeiten können. Dafür führen wir an diesem Tag ein komplettes Backlog Refinement Meeting mit Ihren Teammitgliedern durch, dessen Ziel es ist, das Product Backlog für die nächsten Sprints vorzubereiten.

Haben Sie Fragen? Rufen Sie uns an +43 (0) 72 29 / 630 63 - 0 oder schreiben Sie uns eine E-Mail: [email protected] Gerne besprechen wir mit Ihnen die Details unseres Product Backlog Refurbishments!

Leistungsumfang Beobachtung wichtiger Meetings Befragung sämtlicher am Entwicklungsprojekt beteiligter Rollen Analyse bestehender Abläufe Erstellung eines Berichts mit Beobachtungen, Symptomen und konkreten Handlungsvorschlägen zu deren Verbesserung Gesamtumfang: 2 Tage (bzw. 4 Halbtage) plus Erstellung des Berichts

Voraussetzungen Ein geplantes bzw. laufendes Entwicklungsprojekt Ein vorhandenes Product Backlog Verfügbarkeit der Teammitglieder (2h)

Vorteile Anwendung aller Praktiken an Ihrem Backlog Effektivere und effizientere Planungsmeetings Gesteigerte Motivation der Teammitglieder durch klare Ziele und Akzeptanzkriterien der User Stories

Investition EUR 1.150,- zzgl. gesetzlicher USt. und evtl. anfallender Kosten für die Anreise außerhalb von Wien und Linz.

03 AGILE TRANSFORMER PACK