The difficulty with credentials in software development is that you need some sort of objective standard for the knowledge and/or skills required to merit a certain credential.
No-one really knows yet how to consistently build good software with a normal workforce within commercially realistic timescales and budgets. For that matter, even what constitutes "good software" probably depends on the context; in the real world, it is usually a question of "good enough" rather than any absolute standard that applies to all projects. Therefore, I'm not sure there is anyone in the world who could write those objective standards yet.
Even if there were, there is a significant risk that they would be shouted down by the kind of consultants who don't actually make a lot of software and don't actually have a good track record of success in their own projects, yet have no problem writing books, blogging, speaking at conferences, or otherwise telling the rest of the industry how it should be doing its job.
That could lead to the worst possible outcome: an industry with de facto or even de jure regulation of who may practise, similar to other engineering disciplines for example, but where the regulation actively favours people who are buzzword compliant and up on the latest fads, rather than people who are actually good at building useful software.
No-one really knows yet how to consistently build good software with a normal workforce within commercially realistic timescales and budgets. For that matter, even what constitutes "good software" probably depends on the context; in the real world, it is usually a question of "good enough" rather than any absolute standard that applies to all projects. Therefore, I'm not sure there is anyone in the world who could write those objective standards yet.
Even if there were, there is a significant risk that they would be shouted down by the kind of consultants who don't actually make a lot of software and don't actually have a good track record of success in their own projects, yet have no problem writing books, blogging, speaking at conferences, or otherwise telling the rest of the industry how it should be doing its job.
That could lead to the worst possible outcome: an industry with de facto or even de jure regulation of who may practise, similar to other engineering disciplines for example, but where the regulation actively favours people who are buzzword compliant and up on the latest fads, rather than people who are actually good at building useful software.