- Do they recognise the need to base requirements on their business/technology plan/architecture - as this provides the only canonical reference point. If they don't then point them at the material that explains why and leave them for a year or two.
- Do they recognise the current requirements in an architectural vacuum, document oriented, often software engineering lead, approaches to requirements have been failing, appallingly for a decade. It fails for everyone but the consultants and SW engineers. If they don't then point them at the material that explains why and leave them for a year or two.
- Do they recognise that engineering requirements, methods and modelling are oriented at wrong things for the wrong people. If they don't then point them at the material that explains why and leave them for a year or two.
- Do they recognise that what is required are solutions where all stakeholders can access information in ways suited to the tasks they perform, that all demands and requirements need to reference a common view of the enterprise? That each project dealing with requirements, should as a by-product, of its elaboration improve that view of requirements? That is do they recognise:
- Requirements should be captured referencing the enterprise's architecture (as a building project references the town plan)
- Requirements captures should help identify and remediate gaps in the enterprise's architecture (as a building project will identify gaps and errors in a town plan).
- Overlaps across projects will only be visible when the reference to a canonical source is in place (as one can see on a town plan if buildings will overlap)
- a common vocabulary of requirements affect on the architecture is needed (to avoid dozens terms which mean the same thing, or may not)
- documents and other specifications should be automatically generated (as reports on data, not narratives purporting to be data)
- common ways of rating things (based on data) should be in place - such as: value, risk, feasibility, cost, clarity, etc.
- we should be able to identify potentials impacts of a change in the business architecture on all projects
- the criticality of all stakeholders have immediate direct access to requirements, in forms and at levels of detailed suited to their roles (diagrams, documents, visualizations; heatmap, roadmap, impact map; etc.)
- the need to link explicitly the requirements to putative solution elements (to support delivery management)
The bottom line is you can't help people who don't want to be helped - and the 1st they need to make (for themselves) is to recognise there is a problem and they need to do something. See the 12-step programme for treating addiction to failed ways of doing things.
Remember Planck's Principle (not his constant) - "A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die and a new generation grows up that is familiar with it."