BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Continuous Improvement Content on InfoQ

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

  • Untangling the Enterprise With Continuous Delivery

    John Kordyback explains why you should and how you can introduce Continuous Delivery into a typical enterprise, where dozens of systems adopted over the years generate massive complexity. Learn how value-stream mapping and Lean Startup thinking help to create a deployment process which serves as a solid foundation for further improvements on the whole software change lifecycle.

  • Bug Fixing Vs. Problem Solving - From Agile to Lean

    Lean has proved to be instrumental in moving beyond Agile to set up a practice of continuous improvement with direct effects on team performance and engagement. Making a clear distinction between bugs and problems has proved to be instrumental in this improvement.

  • 3 years of Kanban at Sandvik IT: Sustaining Kanban in the Enterprise

    This second article in the “3 years of Kanban at Sandvik IT” series focuses on the lessons that the System Development Office learned when sustaining the Kanban method during this 4 years journey. Presented are four qualities that Sandvik IT identified as key when setting-up relevant, and long-term, kanban systems in the enterprise: Stickiness, Clarity, Curiosity and Influence.

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

  • Reliable Auto-Scaling using Feedback Control

    Philipp K. Janert explains how to reliably auto-scale systems using a reactive approach based on feedback control which provides a more accurate solution than deterministic or rule-based ones.

  • 3 years of Kanban at Sandvik IT: The Story of an Improvement Journey

    This is the story of an enterprise-wide Kanban implementation. It explains why Sandvik IT chose the Kanban method; how it was deployed using a kick-start concept; how it was followed-up using a depth-of-kanban assessment; and the effects so far. The article includes links to concrete and step-by-step information on how to run these kick-starts and assessments

  • Kanban’s service orientation agenda

    This second article in the series on the Kanban “nine values, three agendas” model explores the service orientation agenda. Building on the sustainability agenda, this agenda adds the values of customer focus, flow, and leadership. Individually, each of these brings some challenge; collectively, they can represent to a significant sense of direction, a much more outward-looking approach to change.

  • The Sustainability Agenda in Kanban

    This first article in the series on the Kanban “nine values, three agendas” model, explores the sustainability agenda: a common approach to Kanban adoption at the level of individuals and teams, often motivated by the need for relief from unsustainable practices and workloads. This sustainability agenda draws on the Kanban values transparency, balance, and collaboration.

  • Retrospectives Applied as “PROspectives"

    We can view situations in our work as opportunities from which to learn how to better handle similar situations in future, by looking back and asking “How will I deal with future situations like this to improve my results?” PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements.

  • Scrum for Education - Experiences from eduScrum and Blueprint Education

    Schools use Scrum to help students to learn more effectively and develop themselves in an enjoyable way. The self-organized student teams work in sprints to learn subjects and evolve the learning process. Results from the agile way of working are improved quality of education, higher grades and motivated students. InfoQ interviewed people from several schools involved in teaching with Scrum.

  • Interview with Brian Murray from Yammer about Lean Startup and using Minimum Viable Products

    Enterprises want early and frequent customer feedback to be able to understand their needs and be able to deliver products that create value for them. Brian Murray explains how Yammer uses Minimum Viable Products to test their business customer hypotheses, and why they focus so much attention on the architecture of their products.

BT