We are people who love Agile. We want to share experiences and unite like-minded people. For us this is the only natural way to think, work and sometimes to live.

Posts in category Uncategorized

Jaan Pullerits – CyberCat Creations

Building microservices with Esticade framework

Easiest way to get started with microservices.
How to start using benefits of microservices without worrying about REST APIs, port mapping, configuring endpoints and firewalls or service discovery. We explore the benefits and pitfalls of Esticade framework and show how to achieve scalability, reliability and optimal performance with Esticade (and microservices in general), with minimal time and effort.

BIO: Developer for more than ten years, have been working with many technologies and languages.

Björn Kimminich – Kuehne + Nagel (AG & Co.) KG

#NoComments /* about the worthlessness of comments in clean code */

What #NoEstimates is for agilists, #NoComments should be for all developers who <3 clean code!

Comments are – at best – a necessary evil” (Uncle Bob, “Clean Code”) – Over the years I gathered quite a collection of examples for bad code comments. The most precious gems among them I would like to share with you. You will listen in on developer monologues and dialogues, try to analyze cryptic bylines, experience different levels of UnCamelCasing(tm) skill and fight your way through a redundant, useless and misleading inline thicket. You will also hear about well-meant tools and plugins that should not even exist if the mantra #NoComments would be valued as it should be.

BIO: Björn Kimminich is working in the area of software development for Kuehne + Nagel for over 8 years where he is now responsible for Global IT Architecture. He is doing Clean Code trainings with Kuehne + Nagel’s globally distributed development staff since 2011. As a side job he lectures software development at the UAS Nordakademie where he teaches Java to engineering students as their first programming language.

Jaanus Soots – Skype

My personal experience with innovation in product team

This is the story where I was against hacking in team but after 1 year became the innovation champ do push it across the company.
I got my new product and team who was willing to do hacking. As a product manager with full of backlog, delayed delivery and high pressure from managers I was against of any new distractions. But that how it started. After long journey and many complicated experiments we ended up with fantastic outcome. Lot of internal improvements, many new customer features in live and patent taken for one invention.

BIO: more than 20 years on IT field and last 6 years in Skype

Hanno Jarvet – Jarvet Consulting

Defining and executing a portfolio strategy

How to come up with a successful portfolio strategy and how to execute it?
Hanno JarvetHow does a Chief Product Owner turn the company strategy into a portfolio strategy and build a suite of products and services to satisfy new and existing customers? What are some common pitfalls in aligning the organisational structure, governance, budgeting and legal issues and what to do about it?

In a perfect world everyone in our organisation knows what and why it should be achieved, has clarity around which decisions need to be made by whom and has the necessary competence, information, resources and authority to do it. Usually this is not the case. I will share practical examples, tools and models that I have used to help organisations make progress in executing their portfolio strategy.

Kristjan-Hans Sillmann – Telia Eesti (will co-present with Alek Kozlov)

The agile journey of Telia Estonia: experiments and discoveries

How to deal with 150 projects on a waiting list, if they are on the same level of importance and urgency? How to help business overcome the fear of building only small part of their grand vision? How to grow intrapreneurship in the hierarchic and matrix organization and support the people in their new roles?
In this talk you’ll hear what experiments we had, what we learned from these, where we failed and where we succeeded.

BIO: “I have 16 years of experience in software development, I’ve been a developer and a project manager. For 11 years, I’ve also been a lecturer in Tallinn University of Technology.
For the last 2,5 years I’ve been responsible for IT development process improvements in Telia Eesti. In my view, improvements in IT development cannot be enforced, they can only be sold out to the leaders, managers and teams. I think this can be done by a Lean-Agile evangelist who will train, mentor and coach people.
My favourite topics are: Lean thinking, principles and practices; startup mentality in the enterprise; agile Product Ownership and scoping (eg story mapping); DevOps & continuous delivery.”

BIO: Alek Kozlov Product Success Catalyst and Designer. I love to see how people uncover innovation by finding very simple and elegant solutions. But even more I love to see how these innovations help to understand and spin new business models.

Ari Tikka – Gosei OY

From Tayloristic to Agile organization

What is common to Ford factories around 1900 and the collapse of Nokia Mobile Phones 2011? What leads most corporations towards Tayloristic organization? What is the other path to success?

“What is common to Ford factories a hundred years ago and Nokia about 20 years ago? In our session we explain the logic that takes the vast majority of leaders and corporations towards Tayloristic organization. We will also show the necessary and adequate changes to move from Tayloristic to Agile organization. Agile Adoptions tend to fall back to the old status quo. This happens for several reasons. First, a partial adoption introduces changes, which make the socio­techno­-economical system inconsistent and uneconomical. Second, partly because of the previous, the old status quo remains more comfortable for the individuals, and the new practices do not sustain. Third, the fundamental leadership assumptions have been cemented in the culture.
We will shed light on Taylorism versus Agile using several approaches: Ouchi’s theory of organizational control, Hackmann’s research on High­Performance Teams, Lean product development, Large­Scale Scrum, Complexity theory, history of Leadership, and our 20+ years of experience.”

BIO: After studying structural mechanics Ari built fault tolerant embedded real time systems for ten years. He has been full-­time organizational therapist since 1997. He has deep experience in organizational and group dynamics. He likes to explore and publish about patterns and unconscious phenomena in organizations. Ari is working with international Large­Scale Scrum (LeSS) adoptions, and contributing actively to the framework. In private life Ari listens to strange classical music (now playing), lifts iron, runs after the ball and tries to sit quietly in zen meditation.

April 16, register now!

Hear ye, hear ye – after a short break Agile Saturday is back and it’s almost here!

So clean your schedule for April 16th and see you at the Agile Saturday XII at Hotel Euroopa!

Register at Eventbrite

To all the newcomers – come and see what the fuss around Agile is all about; to all the oldies  – come and hear what your peers and colleagues have to say about recent developments and news in the Agile scene.

So here is what we have for you on the XII Agile Saturday:

The first Keynote is Brendan Marsh from Spotify talking about “Spotify Running: Lessons learned from building a ‘Lean Startup’ inside a big tech company”

In the management track we have:

Hanno Jarvet from Jarvet Consulting talking about “Defining and executing a portfolio strategy”

Kristjan-Hans Sillmann and Alek Kozlov talking about “The agile journey of Telia Estonia: experiments and discoveries.”

Ari Tikka from Gosei OY talking about “From Tayloristic to Agile organization”.

In the technical track we have:

Björn Kimminich from Kuehne + Nagel talking about “#NoComments /* about the worthlessness of comments in clean code *.”

Jaan Pullerits from CyberCat Creations talking about “Building microservices with Esticade framework.”

But this is not all- we also have:

Jaanus Soots from Skype talking about “My personal experience with innovation in product team.”

Filips Jelisejevs talking about “What are they hiding from you – dark(er) side of SCRUM and Building Xanadu.”

Priit Kaasik from FlowHow talking about “Too many ways to improve Scrum? Take them all!”

And of course there is going to be an afterparty as well so you can mingle some more with all the great people you met during the day.

Sounds good so far? Well this is still not all- we have more speakers coming, so stay tuned for more updates about the agenda and speakers!

You may also check our FB page for updates.

See you already on the 16th of April!

Jürgen Münch – keynote

Creating Value with Software: A Blueprint for Continuous ExperimentationJuergen Muench

Finding the right scope for product development in order to build products that customers want is crucial for success. An important approach for steering development towards the right scope is to continuously conduct experiments. Insights from such experiments directly influence frequent iterative deliveries. Success cases from industry show that such an approach helps companies to gain competitive advantage by reducing uncertainties and rapidly finding product roadmaps that work. However, defining and conducting the right experiments can be challenging:

How can we identify the relevant questions we need to answer for making good product decisions? How can we find the right hypotheses to test? How can we define metrics that inform product decisions? How can we justify the efforts for experimentation? How can we link the experimental findings with product decisions and dynamically change a product roadmap? This talk answers the questions above and provides a step-by-step blueprint to put continuous experimentation into action.

BIO: Jürgen Münch is a Professor of Software Engineering at Reutlingen University, Germany, and a Research Director in the Department of Computer Science at the University of Helsinki, Finland. He specializes in software engineering, in particular data- and value-driven software development, product management, agile engineering, and innovation. Results are documented in five books and more than 150 refereed publications. Jürgen has been a principal investigator of numerous research and development projects. He regularly teaches product management courses and helps companies to develop innovation capabilities and new digitally-enabled products and services.

Register now to the next Agile Saturday  http://bit.ly/1Ybv3oK and see you already on the 16th of April!

Call for Papers is open for Agile Saturday 12 (April 16th)

Hello all Agile Saturday fans, friends and speakers!

3583_10152229281150199_1384616662_nWe are glad to tell you that after a short break we are back! So book the date in your calendar (16th of April) and submit your abstract or several abstracts as the Call for Papers is now open!

We invite you to share your experience (good, bad and ugly) and submit an abstract or several abstracts to present on XII-th Agile Saturday in Tallinn, Estonia on 16th of April.

The Submission will close on the 17th of March.

If you have any questions don’t hesitate to ask – team@agile.ee.



Priit Liivak


What is it?

Dojo is the Japanese term for “place of the way”, but it mostly describes a training place for
martial arts. For us, it is a training place to learn more about writing good quality code and
gaining tremendously valuable insights into the way other people solve problems.

Who is invited?

Code Dojo is open to everyone. Regardless of your skill level or your job description in
Outlook email signature, you are welcome. This includes junior testers, senior architects,
project managers, analysts, lead programmers so well versed in their craft that the only
challenge they have in their daily work is the tough decision which flavor of syrup to add
to their coffee on this particular morning, programmers yet to discover the joys of Extract
Method refactoring shortcut key and you. Especially you!

Why do it?

To become better, practice you must! Two hours in a Code Dojo will teach you far more than
a month grinding out one Model-View-Controller after another. Solving seemingly simple
problems in different ways and under different restrictions will challenge your mind, seeing
how other people steer their solutions to glorious victory through the rocky Red-Green-
Refactor cycles will broaden your own approach and improve your skills. You are guaranteed
to walk away with multiple invaluable insights.

How do we practice?

We will solve a kata, a simple programming challenge using Test-Driven Development
methods. You are free to come and practice alone. I strongly encourage you to bring a friend
or find a partner in the Dojo and work on the kata together as a pair. To make things even
more fun, we also try randori, free-style practice where multiple people line up to solve the
kata on a single computer. The first person writes a failing test, the second person makes the
failing test pass and then writes the next failing test before passing the turn to next person in

I have never used Test-Driven Development. Can I still participate?

Yes! You should definitely come. If you are not familiar with TDD, you can try solve the kata
without it, but be warned, you will be missing out on a lot of fun. I recommend pairing up
with someone or taking a turn in the randori line when you think you have gotten the gist of
it. Test-Driven Development methods used in Code Dojo are very easy to learn.

Which programming languages do I have to use?

You can use any programming language you are familiar with. Unit testing frameworks exist
for most languages (Java = JUnit, C# = NUnit, JavaScript = Jasmine, Scala = ScalaTest, Ruby
= Test::Unit, etc.) and for nearly all of them IDE support is available. So you can write your
tests in your favourite programming language (or the one you want to practise) and run them
in your favorite development environment.