Final answer:
The claim that project work does not follow any software development workflow is false. Software development requires following a structured workflow, and although the project succeeded in relational-based changes, it failed to make a systematic impact on a larger scale.
Step-by-step explanation:
The statement 'Work carried on throughout the project does not relate to any specific workflow of software development' is false. Software development typically follows specific workflows or methodologies, like Agile, Scrum, or Waterfall, to ensure a systematic approach to project management and execution. This helps in streamlining tasks and making sure that the development progresses in a structured way. However, it is important to note that different methodologies might have varying degrees of impact on the actual work.
Regarding the project mentioned, which did a good job with relational-based changes, this suggests a focus on adapting to the relationships within the data or system being worked on. While there is a clear indication of success on this front, the project lacked in making a systematic impact on local or national levels.
Efforts in software development must also consider the broader impact, which involves systematically affecting communities or users at different scales. Applying changes that work well within a system does not guarantee that those changes will translate to positive outcomes in the wider context without dedicated efforts directed towards community engagement or national-level strategies.