A lot of the pain that large and medium-sized organizations are facing boils down to scaling. It is not difficult to have 5-10 people working together in one room. However, as your business becomes more successful and your hiring increases, you will start to see problems. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.
The people’s Scrum by Tobias Mayer is a collection of essays covering topics like self-organizing, team working, craftsmanship, technical debt, estimation, retrospectives, culture and Scrum adoption. InfoQ interviewed Tobias about the importance of people, teams and self organization with Scrum and about AgileLib.net, a new initiative for sharing agile resources.
This second article in the “3 years of Kanban at Sandvik IT” series focuses on the lessons that the System Development Office learned when sustaining the Kanban method during this 4 years journey. Presented are four qualities that Sandvik IT identified as key when setting-up relevant, and long-term, kanban systems in the enterprise: Stickiness, Clarity, Curiosity and Influence.
The story of an internally driven and remarkably smooth Kanban implementation approach which quickly rewarded Siemens with real and sustainable improvements in predictability, efficiency and quality. 14
This third and last article in the series on the Kanban “nine values, three agendas” model explores the survivability agenda: the humane, start with what you do now approach to change.
A story of an enterprise-wide Kanban implementation, with step-by-step information on how to run Kanban kick-starts and assessments to install a culture of continuous improvements in the enterprise. 2
This second article in the series on the Kanban “nine values, three agendas” model explores the service orientation agenda: a much more outward-looking approach to change.
This first article in the series on the Kanban “nine values, three agendas” model, explores the sustainability agenda: a common approach to Kanban adoption at the level of individuals and teams.
Tracking projects is challenging when enterprises adopt agile in product development. Smaller work items and lower work in process improves risk management and supports agile execution and learning. 3
Lean’s major concept is reducing waste: removing anything that is not adding value to the customer from the process. Steven Peeters explains how you can apply Lean principles in an IT environment. 2
The Lean Kanban Conference took place in downtown Chicago last week, and InfoQ interviewed David J. Anderson, father of Kanban in the software development industry. 5
At the Lean Kanban conference, InfoQ asked Dr. Arne Roock how a team can evaluate whether Kanban is the right tool, and how to kick it off. Dr. Roock offers some prescriptive advice.