• built in feedback loops • product development artifacts (iterative planning, backlog, review) “Kanban is NOT a software development life cycle or project management methodology! It is not a way of making software or running projects that make software!” — David Anderson
• Agile growth outside the teams stagnates. • Focus on how (software development) not what (business) • Local optimisation of the overall workﬂow • Organisation structure remains the same • Two-class society Result: Doing agile but not being agile.
Competence culture Collaboration culture Company-oriented Reality-oriented Possibility-oriented • No culture type is better than another • Organisations typically have a dominant culture with aspects from other cultures • Culture may differ between departments within the organisation Source: The Reengineering Alternative
developers must work together daily throughout the project. • The most efﬁcient and effective method of conveying information [...] is face-to-face conversation. • Continuous attention to technical excellence and good design enhances agility. • The best architectures, requirements, and designs emerge from self- organizing teams. • Welcome changing requirements, even late in development. … Source: Agile Manifesto
Implementation Scrumban in a nutshell: • Scrum as the chosen way of working • Kanban Method to understand and continuously improve how the work is done Using scientiﬁc methods (e.g. Value Stream Mapping, Kaizen) can be starting point for next improvements.