Metrics are engrained in kanban. They play a role in several kanban practices like visualizing and managing flow, and support the agenda’s for sustainability, service orientation and survivability. At the Lean Kanban Central Europe 2014 Conference Wolfgang Wiedenroth talked about the power of metrics. In his presentation he provided may examples of using metrics with kanban.
Kanban is often used to manage work, but the concepts of kanban can also be used to guide a journey of change in an organization. This is a case study of an insurance company that used kanban to get change done to improve visibility and predictability and engaging their people.
Teams can share their experiences with other teams and coaches through storytelling. Agile coaches can facilitate a process of sharing experiences to empower teams and help them becoming self-organized said Patrick Steyaert and Wim Bollen. They showed a technique based upon archetype construction to draw learning’s from team stories which teams can use to design and travel their own agile journey.
When organization use kanban mainly for visualization of the work they may be missing out on benefits, says Matthew Philip. Introducing a flow manager role can help teams to reflect and find solutions to the problems that they are facing, thus catalyzing change in the organization.
Creating and maintaining a Quality Management System (QMS) can be difficult, certainly when organizations have multiple product lines where different regulations and standards are applicable. InfoQ interviewed Willem van den Biggelaar about the benefits of having a QMS, dealing with multiple regulations, assuring adherence, how a QMS can support agility and deploying a QMS in an agile way.
Successful adoption of agile is related to the approach that is used to introduce changes in the organization. Organization can do a top down “mandated” implementation or use a different approach. Kanban can be used as a way to kick start agile, allowing teams to opt-in to agile practices when they feel ready for it to create a sustainable new way of working .
Agile coaches often use a “hands-off” descriptive approach when coaching teams. The question is if such a coaching approach is always the best solution when teams are adopting agile? Would there be situations where prescriptive “hands-on” coaching could be more effective? How could you do it?
Software development can be viewed as collaborative knowledge work. Such a view calls for different ways to manage organizations and the people who work in it. Bob Marshall wrote several blog posts about the antimatter principle. InfoQ interviewed him about this principle and the practices to use it to attend to the needs of people.
Adopting agile is an organization change which involves management. It is said that management buy-in is crucial for agile to succeed and that a lack of management support can be a barrier in agile transformations. There are different ways for management to support agile in enterprises.
Kanban helps organizations to get insight into their work-in-progress, and establish a pull system where demand and capability can be balanced. A first step is to find out what the real capability is and visualize the flow. InfoQ interviewed Florian Eisenberg about evolutionary change and how you can balance demand and capability in organizations.
Agile is about a mindset and a contiguous improvement of everything said Yves Hanoulle. InfoQ did an interview with him about the habits that people have and what you can do to get into the habit of improving.
The 2013 international conference in Central Europe about Lean and Kanban (LKCE13) included presentations about change management, systems thinking, leadership, learning, and teamwork, and case studies from larger organizations that have applied Lean and Kanban. InfoQ interviewed Arne Roock about deployment of Lean and Kanban in agile software development.
How can you combine Scrum with a project constrained by a fixed price and completion date? Tim van Baarsen discusses his experience of completing a fixed-everything tender through continuing to work with Scrum behind the scenes.
Having stable teams can be beneficial for agile software development. Several views on establishing and nurturing stable teams, and dealing with team dysfunctions.
Two video lessons covering agile coaching and organizational change were released by Pearson/Addison-Wesley in the last quarter of 2012. They provide a different way to increase knowledge on agile adoption for visual and audible learners.