Scrum, Kanban and Scrumban
Use and purpose of Scrumban
Main Differences to Scrum
Main Differences to Kanban
The Agile Manifesto
The Pillars of Scrum
The Pillars of Kanban in Software development
Agile Thinking with “Shu-Ha-Ri”
Mastering complex Systems
More accurate Predictability
Taking organizational culture in Mind
Kaizen and Human endeavor
Identify the real Problems
Better understanding of speed & quality
Making agile Improvements holistic and sustainable
Intentional Architecture
Understand profitable Organizations
Scrum Roles, Artifacts and Time boxes
Decentralized Thinking systems
Kaizen and A3 Thinking
Kanban’s core Practices
The four Principles of Kanban
Kanban Artifacts
Scrumban Roles, Artifacts and Events
Flow metrics
support crews and organizations in speeding up their conversion to plain Scrum;
reduce time to market, get a faster Return on Investment through early and frequently delivery of product increments, and achieve a higher quality by managing the dimension of the iron triangle in highly volatile markets;
use the Agile Values in Scrumban and agile thinking with “Shu-Ha-Ri” with Kanban’s core Practices;
apply explicit guidelines for working methods by setting the rules of flow, queuing principles, and economic prioritization.
activate new possibilities within crews and large organizations to support them in coping with the challenges that Scrum sets for them