BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Prioritization Content on InfoQ

Articles

RSS Feed
  • ‘Debt’ as a Guide on the Agile Journey: Organizational Debt

    In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to organizational debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.

  • Q&A with Vasco Duarte on the #NoEstimates Book

    In the book NoEstimates: How to Measure Project Progress Without Estimating Vasco Duarte explores how NoEstimates can help to manage projects with a focus on value and predictability, report progress quickly and often, and adapt plans constantly based on existing data.

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

  • Why Companies Need to do a Better Job of Prioritizing Features

    When everything is high priority, nothing is high priority, and we fall into a miasma of finger pointing and misplaced expectations. Here is why companies need to do a better job of prioritizing features. Wikipedia defines diffusion of responsibility as "... a sociopsychological phenomenon whereby a person is less likely to take responsibility for action or inaction when others are present

  • The Resurrection of Product Risk Analysis

    Product risk analysis (PRA) is not only useful in testing but is also applicable during the various phases of sequential or agile system development. This article introduces a different application of PRA that elevates it from project level to domain level. It shows how you can go from risk and requirement-based testing to risk and requirement-based development.

  • The Prioritization Divide: With Numbers or Without?

    While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.

BT