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

  • Using Large-Scale Scrum (LeSS) with Feature Teams to Ship Your Product Every Sprint

    An interview with Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility. Larman also explained how organizations can work with feature teams, and gave examples of how teams and stakeholders can be in direct contact with their customers and users and can work together to ship their product every sprint.

  • Q&A with Claudio Perrone on PopcornFlow / Evolve and Disrupt

    At the Agile Eastern Europe 2015 conference Claudio Perrone gave a keynote titled "Evolve and Disrupt". InfoQ interviewed Perrone about continuous evolution, servant leadership, popcorn flow (an approach to continuous evolution through rapid experimentation), and doing experiments to make change more continuous.

  • Using Blocker Clustering, Defect Clustering, and Prioritization for Process Improvement

    When work gets delayed (it’s blocked), it is of particular interest to look for ways to improve the smooth flow of work by resolving the causes of that delay. In the long term, finding ways to eliminate the root causes of these delays is a superior solution. This article discusses clustering blockers and provides ways to prioritize those blockers that have the most impact or are the quickest wins.

  • The Essence of Flow

    How do you get good flow? A common scenario in a software company is that too much is going on at once. We need a shift in mindset, to go from focus on resource efficiency to focus on flow efficiency. This article presents concrete examples on how to achieve flow by limiting WIP, reduce wait times and arrange cross-functional teams.

  • How a Flow Manager Helps Teams Deliver, Fast and Smoothly

    As agile software delivery practices and management evolve, so, too, do the roles. kanban has introduced the idea of managing flow, one of the method’s core practices. With talented developers, quality advocates and user-experience designers, teams know how to deliver valuable software. But as we improve service delivery using kanban, who manages flow?

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

  • Using Experiments and Data to Innovate and Build Products Customers Actually Use

    An interview with Jan Bosch, professor of software engineering and director of the Software Center at Chalmers University of Technology, about the benefits that companies can get from increasing delivery speed, the next steps that organisations can take after adopting Agile and DevOps, using experiments to innovate, practices for experimentation and how organisations can become more innovative.

  • Migrating Your Team to Visual Project Management Software

    Visual project management tools can provide greater flexibility within development lifecycles and improved quality of the overall product through smarter distribution of tasks, but migrating from a scrum-only application to a visual PM tool can be jarring. This article presents six tips for making a smooth transition and two case studies of development teams that have already done so.

  • Dealing with Politics in Agile or Lean Teams

    InfoQ interviewed Katharine Kirk about how agile or lean can increase politics and how she combines ideas from agile and lean with eastern and tribal philosophy to deal with people issues that arise. InfoQ also asked her to give a different perspective and practical advice for addressing and navigating politics in organizations.

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

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

BT