BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Continuous Improvement Content on InfoQ

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

  • Continuous Learning as a Tool for Adaptation

    The fifth and capstone article in a series on how software companies adapted and continue to adapt to enhance their resilience explores key themes with a special view on the practicality of organizational resilience. It also provides practical guidance to engineering leadership and recommendations on how to create this investment.

  • Put the Feedback back into “Demo & Feedback”

    As agilists, we know the importance of showing our work and getting feedback as early as we possibly can. That feedback guides what we do next. To get what you need to meet the desires of your stakeholders, this article looks at the demo and the feedback part of that session and provides suggestions for creating amazing demo & feedback sessions.

  • Surviving Zombie Scrum

    The book Zombie Scrum Survival Guide by Christiaan Verwijs, Johannes Schartau, and Barry Overeem aims to support teams that are stuck in Zombie Scrum. It helps them to understand why things are the way they are and provide them with experiments to get out of this state of Zombie Scrum by enabling collaboration with stakeholders, working increments, autonomy for teams, and continuous improvement.

  • Becoming an Exceptional Manager

    The book Manager in Shorts by Gal Zellermayer describes principles of management in hi-tech, focusing on people, processes, and culture. It provides tips and ideas that readers can use to develop their leadership skills and learn how to manage technical people and become an exceptional manager.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.