Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Agile Conferences Content on InfoQ

  • Sustaining Fast Flow with Socio-Technical Thinking

    To sustain a fast flow of changes over long periods of time, organizations address both the social and technical, socio-technical, aspects of reducing complexity. Examples are incentivising good technical practices to keep code maintainable, architecting systems to minimize dependencies and maximize team motivation, and leveraging platforms to preclude whole categories of infrastructure blockers.

  • On a Quest to Sustainable Happy Profit: How to Create a Sustainability Framework That Works for You

    Being sustainable is not just about the product itself, which is built to endure over time. It’s also about the people, time and energy involved in the process, and the consumption that its existence requires. If any single part of the process cannot be maintained over time, it’s unsustainable. Green Recovery can act as an enabler, and when we focus on what matters we can make a dent.

  • Installing a Robust Dev Culture for the Micro-app Environment

    While consumer-facing apps have increased, a bigger increase is taking place within enterprises, with so-called “micro-apps” that are used to create customized solutions. Continuous release environments place developers in a state of regimented activity, leaving insufficient time for micro-app projects. Here's how companies can create a cultural shift that incorporates micro-app development.

  • Building an Effective and Enjoyable Remote Onboarding Experience

    The onboarding experience will make up the new hire’s first impression of your team and company, so it’s really the ideal place to set standards, and therefore requires thoughtful planning, patience, and compassion. In this article, I will dive into some of my own learnings as I onboarded new team members remotely as well as my own wonderful experience joining a new organisation in 2021!

  • Embracing Agile Values as a Tech and People Lead

    Having worked as a software developer, the agile community has been a great source of inspiration to me to find better ways of working. In my first leadership role, I incorporated the agile mindset which helped me to get everyone working towards a joint goal: refactoring an inherited codebase for scalability, while enabling cross functional teams to work as autonomously as possible.

  • How the Financial Times Approaches Engineering Enablement

    Companies need teams working on infrastructure, tooling and platforms; the way they work has to change so that they do not become a bottleneck. These teams need to be about enabling product teams to deliver business value. Investment in this area pays off as it speeds up many other teams and allows product-team engineers to focus on solving business problems that provide value to the organisation.

  • Creating Psychological Safety in Your Teams

    Psychological safety is a work climate where employees feel free to express their questions, concerns, ideas and mistakes. We cannot have high-performing teams without psychological safety. In this article, you will learn practical ideas, interesting stories, and powerful approaches to boost psychological safety in your team.

  • Mitigating Inside and Outside Threats with Zero Trust Security

    As ransomware and phishing attacks increase, it is evident that attack vectors can be found on the inside in abundance. Zero Trust Security can be thought of as a new security architecture approach where the main goals are: verifying endpoints before any network communications take place, giving least privilege to endpoints, and continuously evaluating the endpoints throughout the communication.

  • Getting Rid of Wastes and Impediments in Software Development Using Data Science

    This article presents how to use data science to detect wastes and impediments, and concepts and related information that help teams to figure out the root cause of impediments they struggle to get rid of. The knowledge discovered during research includes an expanded waste classification, and the use of trends to uncover undesired situations like hidden delayed backlog items and defects trends.

  • Avoiding Technical Bankruptcy: a Whole-Organization Perspective on Technical Debt

    Technical debt is not primarily caused by clumsy programming, and hence we cannot hope to fix it by more skilled programming alone. Rather, technical debt is a third-order effect of poor communication. What we observe and label “technical debt” is the by-product of a dysfunctional process. To fix the problem of accumulating technical debt, we need to fix this broken process.

  • Remote Ensemble Testing - How an Experiment Shaped the Way We Work

    This article shares how an experiment evolved into a common practice at the workplace, using an experimental approach with remote ensemble testing to get teammates on our cross-functional team more involved in the testing activities of the jointly created product. This all started in the times of a global pandemic where the entire team was working from home.

  • Growing an Experiment-Driven Quality Culture in Software Development

    Have you ever faced a challenge at work that you weren’t sure how to tackle? Experiments to the rescue! In a complex environment like software development, no one can tell what might work, so we have to try things out. Read this article to learn about key challenges, insights and lessons, and get inspired for your own path to experimentation.