BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Lean Content on InfoQ

  • Improving Scrum with the Kanban-Ace Framework

    The Kanban-Ace Framework welcomes Scrum, and helps teams improve their level of agility. This article explores how a Scrum team can improve by leveraging the Kanban-Ace Framework. It introduces the Akashi Bridge, a new Kanban-Ace tool that makes it possible for Scrum teams to keep the best features of Scrum while growing to higher levels of performance thanks to Kanban-Ace advantages.

  • Proper Usage of Metrics with Flow Debt as an Example

    Flow Debt is a leading indicator that provides a view of what is happening inside a delivery system; an important metric for improving software development. This article provides an example how a metric like Flow Debt can be used improperly, i.e. out of their domain, or properly, i.e. context aware usage of Flow Debt with an IT operations team.

  • Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!

    Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.

  • Product Development Mechanisms

    Steve Andrews discuses the need to empower self-managing teams to stay focused on delivering high-quality solutions using mechanisms like tenets and exit criteria.

  • Johanna Rothman on Agile and Lean Program Management

    Johanna Rothman explores how to scale lean and agile processes to work in large programs in her book - Agile and Lean Program Management: Scaling Collaboration Across the Organization. It explains how to collaborate across the organization to create and steer an adaptive, resilient program.

  • DevOps Lessons Learned at Microsoft Engineering

    Thiago Almeida from Microsoft shares how adopting DevOps practices resulted in better engineering and happier teams, and the lessons learned in that journey.

  • The Volcano - Prioritize Work for Multiple Teams & Products

    It is always a challenge to pick the correct priorities. Which one of work item A, B or C shall you do first, and why? Tomas Rybing presents the Volcano, a tool to visualize and prioritize work for multiple teams working with several products.

  • The Lean Business Analysis Manifesto Explained

    David Morris explains how Lean Business Analysis responds to the ever-increasing pace of change in an age of digital disruption. We no longer have business as usual, so why would we do business analysis as usual? The Lean Business Analysis Manifesto helps put order into the chaos that exists in many of today’s organisations.

  • Q&A on the Lean IT Field Guide

    In the book The Lean IT Field Guide Mike Orzen and Tom Paider explain how to initiate, execute, and sustain a Lean IT transformation. InfoQ interviewed them about how lean can be seen as a learning system, why managers should have both technical and social skills, how to assure that changes will sustain, and establishing a culture of engineering excellence and craftsmanship.

  • Q&A on the book Visualization Examples

    The book Toolbox for the Agile Coach - Visualization Examples by Jimmy Janlén can be used by agile software development teams to visualize and improve their collaboration and communication. InfoQ interviewed Janlén about the strengths of visualizations and how teams can use them to track progress, deal with blockers, celebrate successes and improve.

  • The Agility Challenge

    To be successful, a company needs to become an agile enterprise. In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.

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

BT