Coevolving Innovations

… in Business Organizations and Information Technologies

Currently Viewing Posts Tagged requirements

What is a ‘Requirement’?

I have set out my intention before to argue that Requirements Gathering does more harm than good. The first step was to argue simply that ‘Gathering’ is a passive affair. Now I want to raise a more substantive objection. I want to explore what we mean by ‘Requirements’. I believe that what we mean:

  1. is too varied and contradictory to be useful
  2. does not differentiate between ends and means and is therefore dangerous

If I’m right, it means that the term ‘Requirements’ cannot be used effectively in practice and does more harm than good.

So, taking each point in turn.

1. What we mean by requirements is too varied and contradictory to be useful.

At its simplest a requirement is a noun

1 something required; a need.

2 something specified as compulsory.
(Oxford Compact Dictionary)

At once we can see that there is at least a dichotomy if not a contradiction.

A need can be challenged and explored. ‘Why do you need that’? ‘What goal are you trying to satisfy’? ‘Is the need you have expressed the best way to satisfy that goal’?

Something specified as compulsory is not.

Moreover, the something specified can be any ‘thing’. It can be a goal that must be satisfied (without stating how) or it may be a way of satisfying a goal, a solution, (without stating or justifying the goal or the efficiency and effectiveness of the proposed solution in satisfying it).

These two meanings are quite different from each other and I want to argue that in an IT Solutions industry, quite dangerous.… Read more (in a new tab)

‘Gathering’ is so passive

I have previously stated a view that Requirements gathering does more harm than good

‘Gathering’ generally has the connotation of collecting something that already exists. As if ‘Requirements’ were sitting out there fully formed waiting to be collected. What value does a Business Analyst add who asks a client for their requirements and writes down whatever they are told? I wish this was uncommon practice but I fear it is not. If I were to ask my clients what their requirements are I am mightily impressed when they say ‘we don’t know’. By demonstrating the ambiguity and inconsistency in the answers who claim that they do know, it is relatively simple to discover that they do not. I don’t believe they should know, and I believe that we are doing them a disservice to let them think it is expected of them to be able to articulate an unabiguous and consistent set. But all this begs the question ‘What is a ‘Requirement’ if such a thing exists at all?’. That’s for next time. For now, I will sign off by saying that in my view whatever we do needs to be active and not passive. We need to help clients to identify and remove ambiguity and inconsistency. Without giving the game away we also need to help them seperate ends and means, to distinguish their goals from the features of the solutions which satisfy them.

I have previously stated a view that Requirements gathering does more harm than good

‘Gathering’ generally has the connotation of collecting something that already exists. As if ‘Requirements’ were sitting out there fully formed waiting to be collected. What value does a Business Analyst add who asks a client for their requirements and writes down whatever they are told? I wish this was uncommon practice but I fear it is not. If I were to ask my clients what their requirements are I am mightily impressed when they say ‘we don’t know’. By demonstrating the ambiguity and inconsistency in the answers who claim that they do know, it is relatively simple to discover that they do not. I don’t believe they should know, and I believe that we are doing them a disservice to let them think it is expected of them to be able to articulate an unabiguous and consistent set. But all this begs the question ‘What is a ‘Requirement’ if such a thing exists at all?’. That’s for next time. For now, I will sign off by saying that in my view whatever we do needs to be active and not passive. We need to help clients to identify and remove ambiguity and inconsistency. Without giving the game away we also need to help them seperate ends and means, to distinguish their goals from the features of the solutions which satisfy them.

  • RSS qoto.org/@daviding (Mastodon)

    • daviding: “Might we have an indicator that lives for Canadians are at a…” December 21, 2022
      Might we have an indicator that lives for Canadians are at a stress level lower than other countries? Either that, or spouses are just nicer to each other.> Canadian marriages are oddly stable> In 2020 – the most recent year for which data is available – Canada recorded fewer divorces than at any point since […]
    • daviding: “Any country concerned about population decline could learn f…” December 12, 2022
      Any country concerned about population decline could learn from Finland on policies encouraging infertile mothers, balancing personal and societal concerns. > In Finland – where women first gained suffrage, where a woman is now Prime Minister – it is illegal to pay egg donors more than a basic €250 compensation for temporary discomfort (plus the […]
    • daviding: “While institutions are incorporated to live beyond the lifet…” November 29, 2022
      While institutions are incorporated to live beyond the lifetime of a single human being, perhaps fulfilling its mission can lead to a conclusion that the best course is to wind itself down. Courage at the #IveyFoundation , led by #BruceLourie > One of Canada’s largest and oldest philanthropic organizations has decided to wind down and […]
    • daviding: “Reassured that qoto.org is on the Wayback Machine @interneta…” November 27, 2022
      Reassured that qoto.org is on the Wayback Machine @internetarchive .https://web.archive.org/web/20220000000000*/Qoto.org
    • daviding: “Researching #Contextualism, online archive of "#RootMetaphor…” November 26, 2022
      Researching #Contextualism, online archive of "#RootMetaphor: The Live Thought of #StephenCPepper" from Paunch 1980 magazine is helpful. Philosopher of aesthetics a follower of #JohnDewey, contemporary of #KurtLewin, senior to #ThomasKuhn, #EricTrist https://ingbrief.wordpress.com/2022/11/26/root-metaphor-the-live-thought-of-stephen-c-pepper-1980/ #SystemsThinking
  • RSS on IngBrief

  • Recent Posts

  • Archives

  • RSS on daviding.com

  • RSS on Media Queue

  • Meta

  • Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License
    Theme modified from DevDmBootstrap4 by Danny Machal