Understanding about empirical process control, scrum rules and values. Why does Scrum work? Which are the theoretical foundations and principles? How does Scrum differ from traditional software development and why is it better for product development?

How is the Scrum theory implemented through time-boxes events, roles, rules and artifacts? How can these be used most effectively? We will experience why the Scrum framework is constructed as it is and how you as Scrum Master can effectively use Scrum to control risks and create maximum value.

Learn accountabilities, responsibilities and skills required for each of the role within the Scrum framework to develop product using empiricism.

What is the meaning of “DONE” in Scrum and why is it important? discussion about Technical Debts. Participants have to learn the meaning of DONE increment by defining definitions in the workshop.

Learning by doing is the key factor here. Participants work in a group like real scrum teams. They learn by practicing Scrum on a live project. Small Scrum team plays roles, create artifacts to understand transparency and use events for inspection and adaptation.

Since Scrum is a process framework and to make process works, organization has to work a lot in resolving people and team problem. There will be lot group discussions around certain challenges that majority of organization faces while adopting Scrum.

Why is change hard and what can be done to make it real? What are the organizational changes that are needed to see the benefits of Scrum?

An empowered Scrum Master can bring in positive change but change becomes difficult when the change agent is not pragmatic.

Let’s understand the advantages and disadvantages of the agile way of working. We will also have a discussion around the various models for organizational agility and ways to adopt it. The focus will be on owning a roadmap for organizational agility vs renting processes.