Kanban is an evolutionary change management method which leads teams/companies
to a Kaizen culture of continuous improvement. The evolutionary approach overcomes
the inevitable resistance to change and reduces the fear of the persons involved. The
Kanban mechanics help to solve problems and encourage people to continuously
improve their work processes until optimization is part of their everyday work.
Welcome to the wonderland of Kanban and Kaizen! So much for the theory! The
reality, however, is quite different. In my talk I will share my observations and
experiences with Kanban change initiatives. I will talk about change approaches that
do not work and I will come up with some examples that seem to work very well. If
you are in the lucky position that you are working with highly motivated teams in
which everybody lives the principles of Kanban in every second of their (work) life
then you should probably listen to another presentation. However, if you find
characters in your team like e.g. a husband and father who is afraid to lose his job, and
a young graduate who doesn't seem to care about your fancy sticky notes, and an
experienced engineer who thinks this Kanban thing could maybe work out in the end,
etc. you will probably gain some insights into successfully performing an evolutionary
change initiative with Kanban.
by Ralph Miarka
During our Scrum transition we realized that without major changes we might not be
able to finish our stories according to their priority and that work could be left undone
when specialists drop out. We provide insights on how a group of people changed
from specialized individuals to a collaborating team. We present initial worries, like:
Does everyone have to know everything? We introduce a coaching system, its values,
principles and practices. We show how the team charter played an important role and
how the team evolved it. The team felt that motivation, collaboration and quality
by Boris Gloger
Implementing Scrum wholeheartedly within an organization sooner or later rises
questions of „traditional“ Human Resource Management: How do career options
change, what about the loss of power by transforming positions into roles, how do we
allocate goals and money between teams and individuals? Without finding proper
solutions, these questions may become a crucial test for teams and companies. We
will put the spotlight on the implications of Scrum on HR-tools from recruiting to exit
culture. How can they be adapted to agile requirements and how do we have to
define leadership in this setting?
Methoden und Interventionstechniken aus der Systemischen Beratung, Mediation und
Psychologie, umgelegt auf Scrum Rollenbilder. Welche Techniken und „Tricks“ aus
dem Umfeld sind tauglich in der Praxisanwendung für Product Owner, Scrum Master
und Teammitglieder und Manager? Übung anhand von typischen Situationen aus
by Mitch Lacey
Scrum is an agile project management framework used to deliver software to
customers quickly and with high quality. Those are not its only benefits however.
When used correctly, companies can release systems in shorter time, saving their
customers money while increasing profits themselves. In this talk, Mitch Lacey, former
Microsoft employee and Certified Scrum Trainer, will show you how he has done this
and has seen companies implement Scrum to help them, and their customers, realize
cost savings while bringing products to market faster and with higher qualit
About 5 years ago, RBI Vienna has changed the sofware development lifecycle from a
waterfall based model to an iterative model. Now looking back it is clear that two
goals (improve qualtity of requirement specifications and amend the collaboration
within and between project teams) have not been reached to a satisfying degree.
Therefore RBI Vienna is now on the transition from an iterative software development
lifecycle to a more agile approach. Currently there is an initiative to introduce Scrum in
Software development projects. This lecture will show the initial situation in RBI, the
goal of the initiative, the concrete approach how to reach this goal, the first
experiences and the next steps.
Wie bzw. ob man mit Scrum Projekte aus einer groben Schieflage oder Krise retten
kann und wo die Grenzen liegen. Themen: 1-Wochen Sprints versus zu viel „tax“ bzw.
Overhead; Vertrauensbildung; phasenweise Abnahme; Transparenz schaffen; spezielle
Anforderungen an Product Owner, Scrum Master und Team in diesen Situationen.
Rund um den Begriff des „selbstorganisierten Teams“ rankt sich ein Gewirr aus
romantischen Weltanschauungen, halb-religiösen Ritualen und basisdemokratischen
Träumereien. Sie alle mögen im Kern etwas Gutes verfolgen. Im
Unternehmenskontext führt dieses Gewirr aber oft zum vorschnellen Entschluss „Das
funktioniert bei uns nicht.“
Lasst uns dieses Gewirr entflechten und Selbstorganisation nüchtern betrachten: Als
effektiven Weg der Zusammenarbeit von Wissensarbeitern. In diesem kurzen
Workshop werden wir gemeinsam der Bedeutung auf den Grund gehen. Wir werden
Beispiele und Methoden kennenlernen die Selbstorganisation zu organisieren.
by Gáspár Nagy
Behavior Driven Development (BDD) and Specification by Example are recent trends in
the agile community. SpecFlow is a tool for the for .NET ecosystem that supports the
implementation of the ideas behind those methodologies.
SpecFlow builds upon the success of Cucumber, the famous BDD tool from Ruby
&Rails. SpecFlow provides integration to Visual Studio, MonoDevelop, NuGet and
This session gives a brief introduction to using SpecFlow and shows the latest
The session provides a hands–on demonstration how to get from zero to your first
automated specification in a .NET project with an outside–in approach.
It also shows the most common usage scenarios and possible integrations common
22nd October 2011