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.

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.

Peeter Marvet

Teaching young hackersPeeter Marvet

I bet we all started with games, mods and trying to make the environment around us cool/fun/interesting. Now we are going to schools and trying to make everybody learn “programming” – this trend must stop NOW. What are the cool activities that might require IT skills – from solving puzzles to building robots & better paper airplanes? And how to turn these activities into “formats” that can become viral among teachers and students? Peeter has been speaking to teachers after helping to localize some Codecademy courses and would like to bridge the gap.

BIO: Peeter might have been the first in Estonia to talk about agile in mainstream media – back in 2005. Likes blending together code, design & usability, but could be best in selling really expensive stuff to very large clients. With vision. Is often feeling depressed (and unemployed) by the fact, that he has never had a chance to work in real development.

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.

Dmitri Troshkov

Typescript sugar with nuts 

You will learn how to write compile time safe JavaScript code and be confident in it. In TypeScript you can use classes, enumerations, modules, describe nested structures and still be able to use dynamic nature of JavaScript And the most attractive is that you do not have to learn new language!
The world where you come from, does not matter: Java, .NET, PHP, Ruby… TypeScript is friendly with everyone and all popular IDE-s support that.

Introduction: what, when by whom, strongest “selling” parts of TS.
About me.
What project did I remake to use TS language.
What are the problems with JS?
TypeScript can be just JavaScript.
Demo: How to start using TS in VisualStudio.
Demo: Remaking small JS code piece to TS code and benefits.(VS)
Other IDE-s supporting TS.
How to set-up TS support in JetBrains WebStorm.
Small comparison with other frameworks which compile to JS.
TypeScript pluses.
Compiler is open source.
Some theoretical dive into TS constructions. (I will reduce the amount comparing to DevClub)
Demo: Generics
Demo: External type definitions
Demo: WebEssentials. The same in NodeJS by it’s nature.
Small demo: tricks with Any and Structural Typing by mocking function, object and constructor.
Resources.
Questions.”

 

BIO: From childhood had three passions: physics, IT and theatre. Got good results in state physics contest. For a long time played in amateur theatre before and after university.
Studied Physical Information Technology and Applied Physics in Tartu University. Now studying Computer Systems in Tallinn University of Technology.
Working in IT almost 10 years. Started from test automation and now trying to do everything as senior developer in Fits.me.
Physicists need to explore and see picture of nature very thoroughly to do conclusions. I think the same approach should be in IT industry.

Targo Tennisberg

Agile product development in public sector

“Agile” and “public sector contracts” are often considered to be mutually exclusive terms. However, it is possible to make it work and reap the associated cost savings. We are currently using about 80% of “handbook Scrum” doing public sector work, and we consider this an optimal level.
In addition, we are doing active development for multiple simultaneous customers with their own independent budgets and individual crazy wish-lists while maintaining a common core product.
The talk describes our journey and the current situation: how did we get here and why did we make these particular choices? What did we choose to keep of Scrum and what are we leaving out? How do we juggle and unify the multitude of requirements, plan our work and deliver the results? Also mentioned: the importance of good tools, customer relationship management, and clear technical vision.

 

BIO:

Targo has been involved in the software industry for 18 years, working in both technical and management roles, and on projects involving from just a handful to up to thousands of people. He is currently working as a software architect in Nortal, inventing more efficient methods for public sector information management.

You can read his thoughts on software and other related matters at http://www.targotennisberg.com/tarkvara/ (in Estonian).

Marek Laasik

Agile pitfalls in large organizations, how to not fail the programs

You will gain insight into more common pitfalls and learnings from running large architectural programs in agile environment and how to make them successful from company perspective.

Session will give an insight to the practical side of running a large programs in agile environments.

– How to manage the expectations of stakeholders, set achievable goals and deliver real products in predictable time-frame.
– Difficulties in defining the business value, making it clear and understandable for everyone.
– Role of a product owner in this environment and requirements for other roles.
– Avoiding duplication of work and making sure that the time is spent in the right place.

The talk is based on the real life experience in running the programs that have involved around 100 developers and multiple scrum teams.

 

BIO: Currently on a VP of Engineering position in Fortumo, one of Estonian companies offering mobile and micro-payments in the world around 80 countries.

Previously have been working as a project manager in EMT working on the data services and actively involved in introduction of early mobile portals, MMS and some other services to Estonian market.

After that have been working for 8.5 years in Skype, actively been involved in project and program management, also participating heavily in introduction of agile methods to Skype and running very large programs in Agile environment.

Jaan Pullerits – KEYNOTE speaker

The Soul of a Developer

List of subjects discussed in no particular order:

– The soul of a developer – what sort of people common developers are.
– Way of thinking – binary logic.
– Introversion
– Attention disorders
– Laziness
– Teamwork
– Rivalry
– Trust
– Management communication barrier
– Motivation
– Developer burnout

BIO: Software developer in various companies for over 10 years. Worked in both agile and waterfall companies. Doing hobby projects in various areas of programming and computer arts.

 

Stanislav Gorski

Development process that works

Stanislav will talk about how they crafted their development process at Desk Rock taking the best from different agile development methodologies. He would like to share their experience and talk about how they managed to achieve better performance and quality through the experiments with the process and tools.

BIO: Stanislav is a software developer at Desk Rock – young but very ambitions software development company. He primarily works with Ruby on Rails and develops modern web apps for Desk Rock’s customers.

SPONSORS

Gold
KN


Bronze

codeborne