BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Culture Content on InfoQ

  • The First Few Months of a New Team

    Last January, the OutSystems R&D group introduced a new team, called DevOps. Now that the team has been working together for a few months, we thought it would be a good time to reflect on the journey so far and share it with the community. The article explains how we organized ourselves, shares some data from our first project and presents some of the major lessons we learned along the way.

  • Article Series: Patterns of DevOps Culture

    Healthy organizations exhibit similar patterns of behavior, organization and improvement efforts. In this series we explore some of those patterns through testimonies from their practitioners and through analysis by consultants in the field who have been exposed to multiple DevOps adoption initiatives.

  • Practical Postmortems at Etsy

    We take a look at Etsy's blameless postmortems, both in terms of philosophy, process and practical measures/guidance to avoid blame and better prepare for the next outage. Because failures are inevitable in complex socio-technical systems, it’s the failure handling and resolution that can be improved by learning from postmortems.

  • The Pitfalls that You Should Always Avoid when Implementing Agile

    Moving from traditional project management to agile is a paradigm shift. From push to pull systems from a control-and-command culture to a trust culture where authority is delegated. A good structure with some control mechanisms will most likely help you get the wanted results quicker. This article discusses the role that management plays in organizations that have decided to adopt agile.

  • Q&A with Paul Swartout on the Evolution of Continuous Delivery and DevOps

    InfoQ reached out to "Continuous Delivery and DevOps: A Quickstart Guide" book author Paul Swartout in order to find out what have been the major changes in this space (and in the book) in the last couple of years. Swartout shares his view on cultural challenges to DevOps adoption and how the rise of mobile and microservices impacts Continuous Delivery approaches, among other topics.

  • Why We Fail to Change: Understanding Practices, Principles, and Values Is a Solution

    There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We see virtually no impact of agile or lean on the bottom line of success rates of improvement initiatives, because organizations often look for recipes. We need to change our mindset, and focus on the principles that people follow and values they share and the bigger whole: organizational culture.

  • Q&A with Benjamin Wootton on DevOps Landscape in 2015

    InfoQ talked with Benjamin Wootton, DevOps consultant, to get an update on his view of the DevOps landscape in 2015. Wootton shares his experience, low hanging fruit to kickstart DevOps transformations, how to leverage monitoring, cloud and containers. Also how the market is lacking engineers with the required attitude and skill set for DevOps.

  • Q and A on The Scrum Culture

    Dominik Maximini researched the cultural aspects of organizations that are using Scrum. He published the findings of his research, together with principles for implementing Scrum and suggestions on how to apply these principles and a case study of a Scrum transformation, in the book The Scrum Culture.

  • Staying Connected When Working Remote

    Working remote can give you freedom and independence as you can work when and where you want. But working alone and being distant from people that you work with can result in loneliness and can make you feel disconnected. InfoQ interviewed Pilar Orti about the advantages and disadvantages of remote working, staying connected while working remote and creating trust.

  • Q&A with Sandro Mancuso about The Software Craftsman

    In the book The Software Craftsman, Professionalism, Pragmatism, Pride Sandro Mancuso explores how craftmanship plays a role in agile software development. The book contains stories, examples and practical advice for software developers and other professionals involved in software projects to achieve technical excellence and customer satisfaction.

  • Using Storytelling in Organizational Change

    Telling stories can inspire people to make change happen in organizations. By co-writing the company’s future story you can embrace current strengths to explore future opportunities. Storytellers should step into their story to become their story whilst telling it says Hans Donckers. At the Dare Festival Antwerp 2014 he gave a presentation about storytelling and shared leadership.

  • Inviting over Imposing Agile

    We are at a crossroads in the agile-adoption narrative. Early in the story teams were the “bottom-up” vector for agile spread. Next the way agile spread started to shift away from teams to executives and “management”. Recent developments move us towards consultancy for bring agile to larger enterprises that struggle with change. Which way is agile going to go next?

BT