InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.
The starting keynote at Velocity Conference Europe 2014 was all about how human error is too often the easiest way to explain away a failure and how a different approach is needed. Steven Shorrock, European Safety Culture Programme Leader at Eurocontrol, explained why a Systems Thinking approach applied to safety is a better answer.
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.
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.
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
At the Agile Tour Brussels conference, Luc Taesch facilitated a workshop about understanding and listening. He applied "cognitive science" or "neuroscience" for IT Professionals, and provided solutions to help them dealing with interrupting thoughts and feelings.
At GOTO Amsterdam 2013, Russ Miles did a lightning talk about building the right thing in 5 questions: the 4 questions from impact mapping “Why? Who? How? and What?” and one additional question “What assumptions underpin everything?”. InfoQ did an interview with him about building the right thing using simplicity.