Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage Continuous Improvement Content on InfoQ

  • Five Things to Remember When Upgrading Your Legacy Solution

    Legacy software is still employed, even though it frequently fails to meet critical demands and core business operations. By choosing the right modernization strategy and software development teams, you can easily cut down on high legacy software maintenance costs and increase productivity.

  • Engineering Digital Transformation for Continuous Improvement

    Engineering The Digital transformation leverages manufacturing's successful track record of improving productivity and quality and organizational change management principles. It's a training program designed to reduce the barriers to change, enable teams to understand good design patterns, and ultimately allow organizations to create a systematic approach to continuous improvement.

  • The Three Symptoms of Toxic Leadership and How to Get out of It

    None of us are born toxic leaders, but anyone can easily become one. In the past several years, workplaces have started to feel the effects of “toxic leadership.” Now is the time to educate everyone on the importance of speaking right, doing right, treating each other right in the workplace, and above all, being a non-toxic leader.

  • Resetting a Struggling Scrum Team Using Sprint 0

    Sprint 0 can be a great mechanism in Agile transformations to reset existing teams which are not delivering value, exhibiting a lack of accountability, or struggling with direct collaboration with customers. This article shares the experiences from doing a Sprint 0 with an existing team which was struggling to deliver, helping them to align to a new product vision and become a stronger team.

  • Facilitating Feedback That's Psychologically Safe

    This article focuses on feedback with regards to a plan or proposal - ways to make it easier to give and receive feedback, so the psychological safety of the team can increase. The aim is to give you insights, models, structures and practical things to try, in order to facilitate feedback that boosts psychological safety in your team(s).

  • Preventing Transformational Burnout through Collaboration, Transparency, Feedback, and Coaching

    Burnout is not only an individual issue; it happens in teams and organizations. This article explores probable sources of mental breakdowns, lack of motivation and confidence, along with types of burnout, and describes the role agile coaches and organizational leaders can therefore play in addressing burnout.

  • Building Your Own Agile Team Maturity Assessment

    An agile maturity assessment can help teams come to a common understanding of what agile maturity looks like and what steps they can take to get there. In this article, we are going to dive into the value of assessing things, with concrete examples you can use, and will help you learn how to build an assessment for your teams and/or organization that is fit-for-purpose.

  • Using the Plan-Do-Check-Act Framework to Produce Performant and Highly Available Systems

    The PDCA (plan-do-check-act) framework can be used to outline the performance, availability, and monitoring to enable teams to ensure performant and highly available applications. These include infrastructure design and setup, application architecture and design, coding, performance testing, and application monitoring.

  • 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.

  • 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.

  • 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.