BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • What Makes Joy,Inc Work? Part 2 – Disciplined Project Management

    This is the second of three articles exploring the culture and practices that makes Menlo Innovations such a joyous workplace. This article examines their highly disciplined and rigorous approach to project management.

  • Q&A on Agendashift with Mike Burrows

    Agendashift is a values-based Kanban approach to organizational transformation, covering delivery, change and leadership. An interview with Mike Burrows on how Kanban and Agendashift can strengthen each other, making changes stick in organizations, the depth of Kanban survey, the value of Kanban practices, end-to-end process views, leadership, and doing sustainable change with Kanban.

  • Delivering Software with Water-Scrum-Fall

    Water-Scrum-fall is usually described as an hybrid agile way of working. According to Andy Hiles water-Scrum-fall is a gated and phased delivery approach for software where Scrum is used as the main development management method. It can be used as a stepping stone to agility, to become a living breathing agile organisation.

  • Q&A on Real World Kanban

    The book Real World Kanban by Mattias Skarin provides four case studies where kanban is used to visualize, provide insight and improve product development. InfoQ interviewed Skarin about the essence of kanban and lean, why flexibility in organizations is needed, doing continuous improvement, how visualization can help to understand problems, and advice on how to get started with kanban.

  • What Makes Joy,Inc Work? Part 1 - the Menlo Way

    Having read Joy,Inc and heard Rich Sheridan talk about the Menlo Innovations way, I wanted to understand if this was real and if so how the ideas could be applied elsewhere so I spent a week there. This is the first of three articles and looks at what the Menlo way is and how it evolved.

  • Context is King: What's your Software's Operating Range?

    Francisco Torres shares from experience how users might change how one sees the context of a project and why it is important to define a software’s operating range: the set of quality properties in which a software system can successfully run.

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

  • Q&A on the book Leading the Transformation

    In the book Leading the Transformation: Applying Agile and DevOps Principles at Scale executives Gary Gruver and Tommy Mouser share their experiences with applying lean and agile development methodologies in enterprise development teams.

  • The CTO’s New Innovation Playbook

    In a time of rapid business and technological change, CTOs and other technology leaders are increasingly looking to new methods to drive their digital technology agendas. Creating a new innovation playbook for innovation requires an understanding of the widening disjuncture that disconnects corporate R&D spending from innovation - while also harnessing the rise of new “innovation enablers.”

  • Q&A on Save our Scrum

    The book Save our Scrum by Matt Heusser and Markus Gärtner provides advice for teams to implement Scrum. It explores what teams that are having difficulties doing Scrum can do to get out of trouble and find better ways to use Scrum. An interview about the knowledge level of people that are doing Scrum and "saving Scrum", pursuing business value, how Scrum fails, and adopting and tailoring Scrum.

  • The Five Qualities of Application Delivery Done Right

    This article explains the goals of proper application delivery using immutable infrastructure: automated, flexible, scalable, secure and transparent; and how to take gradual steps toward those goals.

  • UED: The Unified Execution Diagram

    Today’s software applications have a lot of concurrent tasks that are distributed over multiple threads, processes, processors and PCs. This article introduces a visual modeling technique to describe and specify the application’s execution architecture. Within Philips Healthcare the Unified Execution Diagram has proven to be very useful for designing and documenting the execution architecture.

BT