BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Feedback Content on InfoQ

  • Faster, Smarter DevOps

    Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and a transition plan. Derek Weeks discusses some of the benefits and approaches to getting there.

  • Continuously Improving Your Lean-Agile Coaching

    This article describes the challenges faced in starting a group of internal lean-agile coaches and some outcomes such as self-assessment radars, mentoring sessions, and a few lessons. If you are considering a career as a lean-agile coach, you can use it to assess where you are and the next steps you can take. If you already are a lean-agile coach, you can use this to improve your coaching.

  • Peer Feedback Loops: How to Contribute to a Culture of Continuous Improvement

    This third article in a series on peer feedback loops explores how feedback can be used to encourage a culture of continuous improvement. It presents another three methods to do peer feedback and closes with some recommendations for getting started and going.

  • Investing in Impact - Portfolio Management for Agile Deliveries

    Ben Williams and Tom Roden are exploring how you can use agile and lean principles in portfolio management to increase business agility. InfoQ interviewed them about getting project managers involved in agile journeys, using product reviews to decide what to develop, working with hypotheses in portfolio management, measuring actual impact of software products and managing product portfolios.

  • Peer Feedback Loops: How We May Benefit and What is Needed to Realize Their Potential

    This second article in a series on peer feedback loops explores the benefits and what is needed to realize peer feedback, an effective means to encourage a culture of continuous improvement. It focuses on the general benefits, specific techniques and provides three more methods to experiment with peer feedback.

  • Peer Feedback Loops: Why Metrics and Meetings Are Not Enough

    This is the first in a series of articles that will show how to build peer feedback loops, an effective means to encourage a culture of continuous improvement. Starting with a problem statement and some background on feedback, followed by explaining why metrics and meetings are not enough, the article describes the first three methods on how to design and facilitate peer feedback sessions.

  • 7 Habits of Highly Effective Monitoring Infrastructures

    There is a right way and a wrong way to engineer effective telemetry systems and there is a finite combination of practices which — whatever your choice of individual tools — are predictive of success. If you are building or designing your next monitoring system, take a look at this short list of habits exhibited by the most successful monitoring systems in the world today.

  • Q&A on the Book Scenario-Focused Engineering

    The book Scenario-Focused Engineering describes a customer-centric lean and agile approach for developing and delivering software-based products. It provides ideas to understand customer needs based upon end-to-end experiences and for designing products in a customer-focused way using a fast feedback cycle.

  • The Swiss Army Knife for Technical Leads

    Working as Technical Lead is very exciting, every day you have new challenges, new problems to solve and a lot of satisfactions. This article presents some tips in order to improve and empower your teams. There are several techniques to ensure the quality of the products we are working on, but the most important and powerful at the same time is without any doubt the feedback loops.

  • How to Remain Agile When You Have to Sign a Contract?

    Agile development based on a contract that has been accepted by lawyers seems impossible. The nature of traditional purchasing and contracting processes does not match the Agile principles. This is a case story of how a supplier cooperated with a client to develop a huge project in an Agile way, by cutting it into smaller pieces and prepare a matching contract based on mutual trust.

  • Culture is the True North - Scaling at Jimdo

    A lot of the pain that large and medium-sized organizations are facing boils down to scaling. It is not difficult to have 5-10 people working together in one room. However, as your business becomes more successful and your hiring increases, you will start to see problems. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.

  • The Kanban Survivability Agenda

    This third and last article in the series on the Kanban “nine values, three agendas” model explores the survivability agenda. The values associated with this agenda are understanding, agreement, and respect; these say much about the philosophy that underlies Kanban, the humane, start with what you do now approach to change.

BT