‘Good judgement is the result of experience. Experience is the result of bad judgement’ ― Fred Brooks

At Agile Rebels we believe that real learning happens by experiencing. In order to enable your team to start using Scrum framework right after the course, we invite you to the practical training. It is as much about gaining skills to use Scrum, as to understand what are its goals and main benefits. When it is resolved the team can improve and enrich the software development process consciously. The important characteristic of the workshop to be considered is the inspiration and motivation to cooperate within the team and with Scrum usage.

No event found!


too long; didn’t read. Can’t be asked, huh?;)

two day intense workshop.

for Scrum Enthusiasts, Teams and everyone who wants to understand and apply empiricism and self-organisation.

focused on practical understanding of the power and true benefits of the Scrum framework


you will be able to

learn the difference between traditional and agile development methodologies

understand behaviors, characteristics and importance of Scrum roles

feel the value of Scrum values

understand the importance of Done and its role in building transparency

make Scrum events a valuable input in software development process

learn how the Scrum artifacts support agile planning

experience the mechanics of Scrum framework

consciously use inspection and adaptation mechanics for improvements

understand behaviors, characteristics and importance of Scrum roles


what’s it really about

Complexity and empiricism. Scrum theory and principles. Why Scrum? The difference between incremental and prescriptive development. Empirical process control.

People. Teams. Self-organisation. Scrum values. Role of boundaries and feedback loops in developing self organisation.

Scrum in your organisation. How to introduce Scrum in your team and organisation. Reducing waste. Taking action.

Scrum framework. Roles, artifacts and events that enable new management paradigm. Timeboxing. Dos and don’ts. Predictability and empirical model. Risk management. Progress monitoring.

Scrum events value. Facilitation and helpful techniques for productive team meetings.

Increment. Done, undone work. Technical Debt. Quality. The importance of transparent Definition of Done. The consequences of having certain standards in organisation.

Scrum Master’s skills and mindset. How to grow teams. Which behaviors help and how to use data to develop successful teams. Essential skillset. Scrum Master – technical/non-technical.


everyone interested in broadening the usage and efficiency of Scrum

Scrum Masters

leaders in Agile organizations



Our Reviews