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 by Vassili

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!

Brendan Marsh – keynote

brendan-talking (2)Spotify Running: Lessons learned from building a ‘Lean Startup’ inside a big tech company

This is the story of how a small, cross-functional team (with only 1 developer!) worked closely with our customers on a weekly basis to discover the right thing to build, before we built anything and eventually shipped an innovative new feature that was praised by customers and the press alike. If you’ve read the Lean Startup, have been inspired by their stories and wonder “wow that’s really inspiring, now how the heck do I actually DO this?!”, then this presentation is for you. (Here’s a hint: It ain’t easy, but is doable!)

Brendan Marsh is an Agile Coach at Spotify and the coordinator of Spotify’s Innovation guild. Brendan has been coaching the team behind the new Spotify Running feature, which started life as an exploratory project with the goal of discovering what the ideal running experience is for Spotify’s running community. The feature has since been rolled out to Spotify’s 60 million users.

Brendan is passionate about Innovation, Lean Startup thinking and empowering teams to achieve greatness.

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

Elar Lang

Hope management in web applications from pentester’s point of view

Quite often we can read from news that someone got hacked, some data (including pics!) was leaked. Quite often web applications are built with hope “nothing bad will happen”. Quite often users use web application in hope “nothing bad will happen with my data”. I call it all: “hope management”.

As an user – you hope that no one will guess your credentials and web applications keep your data securely.
As a developer – you hope that no one will hack your code, you know enough about security, frameworks-libraries you are using in your project are secure (because they are so widespread and famous!).
As a project manager – you hope all project members are producing only quality and secure software, no one will hack it and the client will be happy.
As a consumer – you hope development company produces secure software and during security test testers find all vulnerabilities.
As a security tester – you hope your scanner can find all vulnerabilities.

Once you have security incident – who is guilty? Attacker – because he/she is bad? Developer – because he/she wrote the code? Admin? Tester? Project manager? Consumer?

As web application security tester, web application security trainer and ex-developer, I will share my opinion about “hope management” in this non-technical presentation. Come and brainstorm about security-bottle-necks in softare development. Also, you may want to change your password later.

BIO: Elar was a Web Application developer about 8 years before switching to security field in the beginning of 2012. Elar is penetration tester and the main lector and course developer of 4-day Web Application Security training course in Clarified Security (In September 2014 he rounded up 1000 hours of WAS training given since 2012 March launch). Elar enjoys researching, writing Proof-of-Concepts and constantly keeps adding to the training content form real life pentesting experiences. He knows what can go wrong in Web Application as penetration tester and Web Application Security trainer and as ex-developer.

Agile Saturday XI – Session Video

Agile Saturday XI – Slides


Jacopo Romei

LiquidO – No management from the trenches

You might have heard of a new breed of organisational models, responding to the fast growing adaptability, engagement and collaboration needs within modern company structures. Or you might have simply experienced the sound problems of slowness, rigidity, bureaucracy, disengagement along with various kinds of waste and bottlenecks that “traditional” organisational models generate and suffer nowadays.


I help companies improve their flow. Lean coach in Onebip. Cocoon projects member. Author of “Pro PHP Refactoring”. I love cappella music, photo, sailing, MTB, travelling far & books.

Agile Saturday XI – Session Video

Agile Saturday XI – Session Slides

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.

Peep Pullerits

MVPs – how to build as much as needed and as little as possible

17.04.14.-452 (1)
Building software that fulfills its true purpose can be easier than you expect. Most requirements are premature and are only validated by real-world feedback. The easiest way to solve any problem is to realize you don’t need to solve it at all.

The acronym MVP gets thrown around a lot, even outside the startup world. What does it really mean to build a minimum viable product? Does it mean we can sacrifice in quality? Join me on a hackathon to find out how much product we can ship in 45 minutes.

BIO: Peep leads one of the product engineering teams at TransferWise, constantly looking for ways to make life better for customers, the business, and engineers.

Hanno Jarvet

Agile is a bad strategy or 5 things every Agile practitioner should know about strategy.Hanno Jarvet

Many people confuse strategy (the “what”) with operations (the “how”) and as a result spend time spinning their wheels without getting anywhere. Actually Agile is not a strategy at all, its an ongoing operational priority.
Agile might help you get to your destination faster, but if the destination is wrong the last thing we need is to get there sooner.

Sometimes business executives or customers come to us with vague images that are short on the what and why and rich on the how. Company strategy, product strategy, Agile strategy, strategic agility, key growth strategy, business strategy. Strategy this and strategy that. In order to help them and yourself you need to think at a higher level of abstraction.

Come and find out what strategy is and how to implement it. As a result you will know how to think strategically and help executives do the same.

Andrei Solntsev

XP for dummies: UI tests Andrei_Solntsev

Hands-on session on writing UI tests.

  • Why developers should write UI tests too;
  • Typical problems of UI tests,
  • How to resolve them and make tests stable and fast

BIO: Software craftsman @ Codeborne (Tallinn, Estonia).
Aggressive fan of extreme programming.
Creator of Selenide – open-source library for UI tests in Java.
Organizer of devclub.eu
Frequent speaker at conferences: DevClub, Agile Saturday, XP Days Kiev, SeleniumCamp, Nordic Testing Days, TopConf, DevConFu.

Andrei Solntsev

XP for dummies: unit-tests Andrei_Solntsev

A pragmatic hands-on session demonstrating how to write good unit-tests and get benefit from them.

  • Why do you need unit-tests
  • How to write good unit-tests
  • 5 myths about unit-tests

BIO: Software craftsman @ Codeborne (Tallinn, Estonia).
Aggressive fan of extreme programming.
Creator of Selenide – open-source library for UI tests in Java.
Organizer of devclub.eu
Frequent speaker at conferences: DevClub, Agile Saturday, XP Days Kiev, SeleniumCamp, Nordic Testing Days, TopConf, DevConFu.

Alek Kozlov

Introduction to SAFe (Scaled Agile Framework) – Good, Bad, UglyAlek

You can find in the Internet a lot of voices raving against this approach, as a try to commercialize Agile.

On the other side a lot of big companies are very into this model and they find it very helpful in understanding how one Agile Company should be structured.

I have reviewed SAFe model and in my session I will share pluses and minuses that I have found in it. Overall I satisfied with they way how Dean Leffingwell been systemized the “”How”” one enterprise can work in agile setting. I have some smaller concerns to share with you and, in my humble opinion, one big architectural flaw that should be changed/addressed.

Come and discuss these topics with me and take away understanding about how does this model can be used in your settings.