BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Teamwork Content on InfoQ

  • Business, Design and Technology: Joining Forces for a Truly Competitive Advantage

    The list of industries being disrupted by digital technologies is growing. To embrace this new digital world, companies need to change their practices and the way they use technology.

  • From a Project to a Product Approach Using LeSS at Agfa Healthcare

    By changing the inner workings from a project perspective to a product perspective Agfa Healthcare established a less complicated process using a single backlog for the entire organisation. Main advice is to try to avoid setting up silos where they do not belong. When applying LeSS it is important to stick to its basic rules even though they are, in most organisations, very disruptive.

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

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

  • How Agile Has Changed Test Management

    Agile methods have many traditional test management activities built into them. With desired agile team traits like self-organising, role blurring and skill diversification, the nature of test management is changing. We have to question whether the role of Test Manager should exist in effective agile organisations and how the activities which have long made up the role are divested?

  • Emotion and Cognition

    Agile values "individuals and interactions over processes and tools." Understanding individuals and how they interact requires insight into how and why people make decisions. The mind works more like a network than a computer. Emotion influences cognition-often from the driver’s seat. This is why emotional intelligence (EQ) is so crucial to Agile development.

  • Staying Connected When Working Remote

    Working remote can give you freedom and independence as you can work when and where you want. But working alone and being distant from people that you work with can result in loneliness and can make you feel disconnected. InfoQ interviewed Pilar Orti about the advantages and disadvantages of remote working, staying connected while working remote and creating trust.

  • Q&A with Sandro Mancuso about The Software Craftsman

    In the book The Software Craftsman, Professionalism, Pragmatism, Pride Sandro Mancuso explores how craftmanship plays a role in agile software development. The book contains stories, examples and practical advice for software developers and other professionals involved in software projects to achieve technical excellence and customer satisfaction.

  • Impediment Busting: Designing an Impediment Removal Process for Your Organization

    Lean Product Development takes an end-to-end focus on the flow of work through a system. Rather than focus on traditional measures such as capacity utilization, it proves more effective to focus on how work is moving through the system. This article discusses what impedes the flow of work, and how we manage impediments to the flow of work.

  • Coding Culture: How To Build Better Products by Building Stronger Teams

    Software developers spend a tremendous amount of time and energy focused on how to build the best possible products. We obsess over what web framework to use or whether to go with a NoSQL or SQL database. While these questions are important, they often neglect to address an equally important aspect of software development: culture.

  • Inviting over Imposing Agile

    We are at a crossroads in the agile-adoption narrative. Early in the story teams were the “bottom-up” vector for agile spread. Next the way agile spread started to shift away from teams to executives and “management”. Recent developments move us towards consultancy for bring agile to larger enterprises that struggle with change. Which way is agile going to go next?

BT