Although almost all the Scrum Masters in general would have world class certifications, many of the Scrum Masters play non-significant or non-impactful role!

These people know the framework well, but still won't command respect for their role from teams or the management. The important aspect many people tend to ignore is, being a Scrum Master is to be a leader of the team. A leader who doesn't have a given/traditional authority, but when rightly understood & done can change the team as well as the whole organization.

This presentation would go through the topics about what to avoid and what to focus to become a Real Scrum Master.

As recommended by Scrum Guide, the Scrum Team consists of Product Owner (PO), Scrum Master (SM) and Developers. That is for the Scrum Team.

But in any organization (small, medium or large) there would be need for management structure that’s needed to support smooth functioning of Teams, creation of teams, setting organizational priorities amongst others.

In this presentation, we will go through different hierarchical structures with regards to the above roles & their pros-cons.

Although almost all the Scrum Masters in general would have world class certifications, many of the Scrum Masters play non-significant or non-impactful role!

These people know the framework well, but still won't command respect for their role from teams or the management. The important aspect many people tend to ignore is, being a Scrum Master is to be a leader of the team. A leader who doesn't have a given/traditional authority, but when rightly understood & done can change the team as well as the whole organization.

This presentation would go through the topics about what to avoid and what to focus to become a Real Scrum Master.

This session walks through the purpose, benefits, methods and audience for the Retrospectives. It also emphasizes the importance of being a team and need of continuous improvement as a Team.
It tries to provide insights into some of the different methods to make retrospective interesting.

This session is based on my direct experience and is highly inspired by the book - Agile Retrospectives: Making Good Teams Great.

Presentation and exercise on creating stories from a business requirement.

Consider, feasibility of development, clarity of requirement & openness while creating stories.

Kill Agility by focusing on…

Current sprint AND IGNORE Long Term Product Vision

Productivity metrics like Velocity, Burndown charts AND IGNORE Quality - Working Software

Individuals AND IGNORE Team

Following Agile Processes AND IGNORE Being Agile

Independent or Management dependent Teams AND IGNORE Self Organized Teams

The focus of this session is demo of Test Driven development using SQL.

SQL is selected as a medium to demo as it is understood by many in the developer community.

Not many in Database development use TDD, this talk provides an easy method to start doing it.

Kill Agility by focusing on…

Current sprint AND IGNORE Long Term Product Vision

Productivity metrics like Velocity, Burndown charts AND IGNORE Quality - Working Software

Individuals AND IGNORE Team

Following Agile Processes AND IGNORE Being Agile

Independent or Management dependent Teams AND IGNORE Self Organized Teams