InfoQ Homepage learning Content on InfoQ
-
Kick-off Your Transformation by Imagining It Had Failed
Large scale change initiatives have a worryingly high failure rate, the chief reason for which is that serious risks are not identified early. One way to create the safety needed for everyone to speak openly about the risks they see is by running a pre-mortem. In a pre-mortem, we assume that the transformation had already failed and walk backward from there to investigate what led to the failure.
-
Learning from Bugs and Testers: Testing Boeing 777 Full Flight Simulators
The aviation industry has developed the habit of scrutinizing every reported event in order to prevent another occurrence, to understand the root causes and suggest changes to design, process, or better training. This article goes over a couple of noticeable accidents and shows you techniques that could be applied to software development.
-
Q&A on the Book Fail to Learn
The book Fail to Learn by Scott Provence explores how we can learn from failure and how trainers and course designers can use gamification to foster failure and learning in their educational environments. When playing games it's ok to try out something, lose the game, learn from it, and restart and try something else.
-
Q&A on the Book Learning to Scale
The book Learning to Scale by Régis Medina explores how to apply lean as an education system to scale companies and help people think about their work and learn together to create value. It provides an enterprise model built on how people learn and grow based on the idea that when people understand what they do and why they do it, they become better in what they do and the company moves faster.
-
Game Based Learning - The Five Dysfunctions of a Daily Stand-up Meeting
Does your Daily Scrum suffer from ’storytelling' or 'problem solving’ symptoms, as well as Sprint Goal amnesia? Does your Daily Scrum Therapy take longer than 15 minutes, but still no relevant information is being shared? The authors prescribe a cure with an Agile Game especially designed to improve your Daily Scrum: The Daily Stand-up Game.
-
Q&A on the Book Creating your Dojo
Dion Stewart & Joel Tosi have written a book about creating a dojo to help teams get better at delivering software products. A dojo is an immersive learning environment where whole teams improve their practices on a range of skills. Dojos are more effective than traditional classroom learning because the whole team works together in the context of their own product and organization.
-
Designing Chaos Experiments, Running Game Days, and Building a Learning Organization: Chaos Conf Q&A
The second Chaos Conf event is taking place in San Francisco over 25-26 September. In preparation for the conference, InfoQ sat down with a number of the presenters, and discussed topics such as the evolution and adoption of chaos engineering, key people and process learning from running chaos experiments, and what the biggest blockers are for mainstream adoption.
-
Agile around The World - A Journey of Discovery
People in different parts of the world exhibit behaviours that can either fit with agile or be an impediment. David Spinks and Glaudia Califano are travelling the world to explore how national cultures impact agile adoption.
-
How Developers Can Learn the Language of Business Stakeholders
This article explores how business stakeholders and developers can improve their collaboration and communication by learning each other's language and dictionaries. It explores areas where there can be the most tension: talking about impediments and blockers, individual and team learning, real options, and risk management.
-
Q&A on the Book Internal Tech Conferences
The book Internal Tech Conferences by Victoria Morgan-Smith and Matthew Skelton is a practical guide on how to prepare, organise, and follow-up on internal tech conferences. It shows how to run internal events that enable sharing and learning across teams and departments, and explores the benefits that such events can bring.
-
Cultivating a Learning Organisation
This article explores how creating an internal culture of experimentation and learning enabled a company to keep pace with the rapid iterations in tech that have become the regular way we do business. It shows that psychological safety is a key component of the learning organisation; employees need to be able to experiment and learn from any outcome - without fear that failure will be punished.
-
Q&A on the Book Elastic Leadership
The book Elastic Leadership by Roy Osherove shows how teams have a need for different types of leadership depending on the state that they are in and what can be done to grow teams towards true self-organization. It provides values, techniques, and practices that leaders can use in their daily work.