InfoQ Homepage Agile Content on InfoQ
-
Software Engineering at Google: Practices, Tools, Values, and Culture
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.
-
Inspect & Adapt – Digging into Our Foundations of Agility
Inspecting and adapting are fundamentals in agile practices. Yet, there are wide interpretations of how either is done well. It is a matter of our heart and soul – but the answer lies between our ears. In this article, we invite you to dip your toe into the deep waters of the internal inspect & adapt mechanisms. This article can be summarised in four words: Think. And think again.
-
Evolutionary Architecture from an Organizational Perspective
Creating an architecture that can evolve over time is not simply a technical challenge, and requires collaboration with non-technical people in an organization to ensure the software adapts as needed.
-
Agile Transformation: an Integral Approach
The book Agile Transformation - Using the Integral Agile Transformation Framework to Think and Lead Differently by Michael Spayd and Michele Madore provides an integral approach to agile transformations. The integral approach operates on all levels, from individuals to teams to the whole enterprise, helping us take multiple perspectives on situations and to think and act from multiple worldviews.
-
‘Debt’ as a Guide on the Agile Journey: Organizational Debt
In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to organizational debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.
-
Keeping Technology Change Human
When we are at the forefront of so much change, it's easy to forget that other people around us find change more challenging. This article is a reminder to look beyond the code and processes, to consider how tech team actions can affect our users in emotional ways. It seeks to establish a few ways of thinking to help bring others along with us when working through technology change.
-
The Game Master's Framework for Software Development
The Game Master Framework for Software (GeMs) combines role-playing concepts with software development, effectively creating a framework to deliver software in complex and chaotic environments. GeMs allows you to use your skills from playing Warhammer, WoW, Dungeons, or dragons, and C’thulu, to create software. GeMs combes gaming tactics with software creation.
-
Applying the “Whole Product Model” to the “Technology Adoption Life Cycle”
In order to develop products customer love, product managers need to truly understand how their “whole product” delivers value and when to address which customer segment. Two models that are very powerful when applied together, and that a product manager can use to develop extraordinary products, are The Whole Product Model and The Technology Adoption Life Cycle.
-
The Flow System: Leadership for Solving Complex Problems
The Flow System elevates Lean Thinking in an age of complexity by combining complexity thinking, distributed leadership, and team science into the Triple Helix of Flow, which organizations can use to become more innovative, adaptive, and resilient. This second article on The Flow System dives into the three helixes of complexity thinking, distributed leadership, and team science.
-
How Journaling Puts Leadership in Action
Have you ever wondered how keeping a journal (or even a so-called “diary”) and business-related topics go together? In this article, Cosima Laube explores how regular structured writing for the sake of reflection and learning looks, and shares her own experience with different journaling variants and techniques, as well as some science and meta-level views.
-
Increasing Developer Effectiveness by Optimizing Feedback Loops
We can think of engineering as a series of feedback loops: simple tasks that developers do and then validate to get feedback, which might be by a colleague, a system (i.e. an automation) or an end user. Using a framework of feedback loops we have a way of measuring and prioritizing the improvements we need to do to optimize developer effectiveness.
-
Compiled, Typed, Ruby-Inspired Crystal Language is Ready for Production - Q&A with Beta Ziliani
The Crystal language is ready for production, 12 years after inception. Crystal is compiled for performance, typed for safety, and Ruby-like for productivity. Due to the strong type inference, developers need only sparse type annotations. We interviewed the head of the Crystal team on the language tradeoffs, the present features and the language roadmap.