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.
To thoroughly remove waste in a process you need flow to deliver just in time, and mindfulness and situational awareness in organizations to handle problems with processes and built in human intelligence. Organizations apply concepts from flow to develop what is needed and when it is needed and use pull to prevent inventories. What they also need is “Jidoka”: mindfulness and situational awareness.
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.
Julian Harty is delivering a keynote talk at the upcoming Agile Pune conference focusing on the work he has been doing using agile approaches to improve education outcomes in developing nations. InfoQ interviewed him about his work and his upcoming keynote titled "If not now, when? If not you, who?"
In stead of feature farming, we need to deliver better outcomes and focus on the business results that we need to deliver. Measurements should provide insight into the outcomes because that is what is important. The Mobius loop can be used to define appropriate measurements.
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.
Agile testing can be used when developing software for automotive systems. To adopt agile techniques in automotive the automotive SPICE V-model needs to be adopted to agile. One result from combining agile and SPICE as Xavier Martin presented at the QA&Test 2014 conference is that “intensive automated testing and client demonstrations helps to produce better products, rising clients satisfaction”.
Testing teams and their managers need to unlearn the traditional mindset and practices when they want to adopt an agile way of working says Navneet Goyal. At the International Conference on Software QA and Testing on Embedded Systems he gave a talk about how test teams should adapt themselves in agile projects.
Organizations should create an environment where people feel empowered and trusted, with a culture where leaders can thrive says Pawel Brodzinski. An interview in which Pawel shares his view on leadership and culture, explains what it is that makes leaders thrive in organizations and what organizations can do to create an environment where leadership would emerge.
Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.
Devices are becoming increasingly interconnected through the internet where they are communicating directly with each other. Testing such machine to machine (M2M) systems can be difficult due to their complexity and the usage of different platforms, as Peter Varhol explained in his talk about testing in the M2M world at the QA&Test 2014 conference.
By using Model Driven Development component tests could be skipped and integration and system testing went a lot smoother, said Bryan Bakker in the presentation Model Driven Development (MDD) and its impact on testing. Main results from the MDD approach are a reduction of the amount of testing and increased reliability of the code that was generated from a mathematical model.
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.