Day 1

Lectures:Ilan Kirschenbaum

SM Role - the Basics

You will learn what is being Agile (instead of just doing Agile). How each role, ceremony, and artifact in Scrum helps you deliver the highest value with maximum business agility. 

This one day workshop is part of the Scrum Master Week. You may choose to attend the entire week, or pick and choose the right days for you.

Add a comment


Day 4

Lectures: Ilan Kirschenbaum & Anat Alon

Leading Agile Teams

SM as a servant leader: So, you have no authority over the team members, but you are still expected to change their behavior and even their mindset. An although you understand the Why, you know the What, you still cannot get them to do what you want. Bummer! Or maybe not? In this day we will focus on the challenge of leadership without authority. How to evolve as a leader, learn practical tools to influence and to create a mindset-shift.

This one day workshop is part of the Scrum Master Week. You may choose to attend the entire week, or pick and choose the right days for you. 

Add a comment


Day 3

Lectures: Lior Friedman & Ilan Kirschenbaum

Retrospective Game Retreat

You will experience different games and activities to use in your retrospectives. This toolkit will help you push the team/s forward to continuous improvement.

This one day workshop is part of the Scrum Master Week. You may choose to attend the entire week, or pick and choose the right days for you.

Add a comment


Day 2

Lectures: Anat Alon & Naama Gafni-Lifshitz

SM as Facilitator

You will learn how to set the stage and provide clear boundaries within each ceremony. Heck, this practical knowledge will help you in any meeting, not just Scrum. With this knowledge you will get the team to collaborate with each other and with you.

Add a comment


5 days

Lectures: Lior Friedman / Ilan Kirschenbaum / Elad Sofer / Anat Alon / Naama Gafni-Lifshitz / Erez Cohen / Alon Linetzki



Scrum is: Lightweight, Simple to understand and Difficult to master״, according to the Scrum Guide.

So.. Are you the scrum master? You have a big a challenge! The scrum guide itself says your role to master Scrum is difficult.. 

What makes it is so difficult? People! This role is focused on people. Influencing people without power and without authority. And as a people's person you know that being efficient doesn't make you necessarily effective. That's a hard sell.

Our next event - December 15th-19th, 2019


Add a comment

Metrics that Matter for Agile Teams: The Measures You Should Use (but Probably Don’t)

Have you ever had a gut feeling a project is about to go off course but no way to validate (or invalidate) that feeling? Has your team ever been burned by an inaccurate estimate or unreasonable expectation? Have you ever wished you could peer a bit into the future? How can metrics be used safely in coaching Agile teams? How can you know whether things are getting better or worse?


Add a comment

A Master Class for Senior Managers and their Coaches

Do people around you waste valuable time and energy not taking ownership for obvious and important problems?

  • You strive to be efficient but encounter resistance and defensiveness around you
  • You want to improve productivity but keep rehashing old issues
  • You try to introduce change but banging your head on the wall hurts 

Now, with with The Responsibility Process®—the world’s first how-to approach for understanding, taking, and teaching personal responsibility—you can confidently build a culture where people take responsibility and demonstrate ownership.


Add a comment

First you write the Test, than you make it pass, and finally you improve the code. Sounds simple, right? The endless loop of Test Driven Development has become one of the leading practices of modern agile developers. Yet it’s hard to explain its benefit until you give it a try.
In this day we going to cover the core principles of TDD and how you should use them to improve the code you write and maintain.
What will you learn? Get to know the basics of the TDD cycle; Practice writing effective unit tests for complex scenarios; Experience how TDD can improve your team’s ability to obtain and access fast feedback.

Add a comment

Behavior Driven Development (BDD) is about helping business and technology expert collaborate to deliver the best possible solutions. In recent years BDD alongside TDD has helped many teams significantly improve their development speed, their overall quality and to satisfy the business expectation.

In this workshop we will explore the foundations of the BDD method, from its theory to its more practical aspects. We will practice scenario writing leveraging the Given/When/Then syntax.

And we will learn how to turn those into an effective automated test suite that will improve the quality of our system.

Add a comment

Our system is big and complex, it’s not feasible to write automated Unit tests for it. 

Often developers shy away from writing unit tests due to their fear of breaking existing

functionality and the perception that it will take a lot of time and effort to actually do it. 

However, when we don't write unit tests the problems tends to increase.

And while most teams will agree that this loop need to be broken, the fear, will stop most of them from even trying. 

In this workshop:

  • we will learn how to write unit tests in a legacy system. 
  • We will focus on the common issues that make legacy code hard to test.
  • We will understand how these can safely and surely be removed.
  • We will stop fearing changes in our system
  • and we will master those techniques by practicing on real life scenarios. 
Add a comment

We’ve all encountered our share of bad code in our day to day work. Bad code means bugs, delays and unexpected costs popping at the worst possible time. Clean code is the remedy for bad code.
This workshop is a hands-on introduction to the fields of clean code and software craftsmanship – the art of writing maintainable, cost-effective code that is readable, correct for both humans and machines. 

Add a comment

The term “Microservice” is one of the most popular and most misunderstood concepts in modern software architecture. How small is a microservice? Does it have to be REST-compliant? Can different microservices share a database? And who made this stuff up anyway?

Add a comment
Page 2 of 2