InfoQ Homepage Culture & Methods Content on InfoQ
-
Improving Speed and Stability of Software Delivery Simultaneously at Siemens Healthineers
In this article, we focus on the software delivery process at Siemens Healthineers Digital Health. The process is subject to strict regulations valid in the medical industry. We show our journey of transforming the process towards speed and stability. Both measures improved at the same time during the transformation, confirming research from the “Accelerate” book.
-
Break the Cycle of Yesterday's Logic in Organizational Change and Agile Adoption
Change in most organizations today seems to be locked in the paradigm of yesterday’s logic – repeating the same top-down, command driven approaches that consistently fail to achieve the expected benefits. The environment today requires new approaches drawing on concepts from modern management approaches. This article introduces a number of ideas and approaches to break out of the old paradigm.
-
Software Testing in the World of Next-Gen Technologies
The introduction of next-gen technologies like AI, Big Data, Robotics and IoT have quickly redefined the way the world looks at software technology. Some of the biggest impacts of these changing trends can be seen in the software testing industry. This article discusses how these emerging technologies need some new approaches, and changes to existing approaches to software testing.
-
Leveraging the Agile Manifesto for More Sustainability
This article explores what sustainability means exactly, the current status of sustainability of the major agile organizations (Agile Alliance and Scrum Alliance), and the impact of software development on sustainability. The main focal point of this article is using the principles of the Agile Manifesto to guide actions that contribute to more sustainability.
-
Improving Testability: Removing Anti-Patterns through Joint Conversations
Code is always testable, but the cost may be high, and the effort exhausting. We can change code to be highly testable by identifying anti-patterns and fixing them. And developers can make the code fit the test requirements, by having discussions with the testers who actually test it.
-
How to Recognise and Reduce HumanDebt
We know TechDebt is bad; chances are HumanDebt is worse, and once you’ve seen it, you can’t “unsee” or ignore it. What is now needed is a focus on the humans who do the work. Psychological safety in teams is key. The “people work” -both at an individual, but especially at a team level- is the key to sustainability and growth of high-performing tech teams.
-
Thoughtfully Training SRE Apprentices: Establishing Padawan and Jedi Matches
This article shares how Padawans and Jedis can inspire and teach us how to help people of a wide variety of backgrounds, ages, and experience levels to observe and understand failures in production. It covers practical lessons learned and shares how you can create and rollout a program for SRE Apprentices within your organization. It also shares feedback from the SRE Apprentices themselves.
-
A Journey in Test Engineering Leadership: Applying Session-Based Test Management
This article shows how modifying Session-based Test Management to our context helped us gain more visibility into our testing. Having a structured yet flexible approach to test management allowed us to make better, more timely decisions about the testing, and gave us more opportunities to influence quality decisions earlier in the process.
-
GitHub’s Journey from Monolith to Microservices
This article explores GitHub's recent journey towards a microservices architecture. It takes a deeper look at GitHub’s historical and current state, goes over some internal and external factors, and discusses practical consideration points in how Github tackled their migration, including key concepts and best practices of implementing microservices architecture.
-
How to Work Better Together: Building DEI Awareness in Tech
We have a diversity problem in technology. Many of our visions and standards of success are centered around one group of people, even though there are many groups contributing to global advancement and growth. The main reason for this is legacy, similar to legacy code. We can overcome this inherited debt by educating ourselves and planning time to do work to rebuild and replace our “legacy code”.
-
Outcome Mapping - How to Collaborate with Clarity
To truly improve, organizations need to deliver change to people, process, and tools. To make change effective, they need to identify where that change is needed, what the map of their current state looks like, and what is the best next step to make progress. Outcome mapping helps align teams to a clear goal, gain an understanding of the landscape, and develop a clear plan of action.
-
Lessons Learned about Developer Experience from the Platform Adoption Metrics @ Naranja
With the intent of improving the product-based approach to their internal platform, Naranja has implemented an automated metrics solution that captures essential figures that describe how their teams are doing in terms of adoption, up-to-dateness and applicability of the solutions their Developer Experience creates. This enables better collaboration on their technology roadmap.