You would often come across some tom, dick or harry posing as an intellectual and giving opinion about something he or she doesn't really understand.
"Things have changed, we shouldn't continue with ISO or CMMI or Malcolm Balridge".
"Now everyone is using Agile, it is so very different".
"Using CMMI means a lot of overhead".
Statements like the one above show just one thing.
The person making such statements is an intellectual pygmy.
As they say half knowledge is risky.
But no knowledge is simply fatal.
Some of these folks may be doing a lot of work that involves creating technical solution, designing system architecture, writing proposal, doing effort estimation, etc. but that by itself doesn't make them expert in anything.
They may not even be experts in the above activities.
Volume of processing a person has done can never be a true indicator of that person's efficiency and effectiveness.
An excellence framework is simply that.
A framework.
An overall approach.
Basics never change, they may get refined and fine-tuned over time.
The basic principles of project management have always been the same since ages:
This was true a decade back, is true today and will be true a decade hence too.
The basic principles of software engineering have also always been the same since ages:
Any excellence framework in the domain of project management and software engineering would contain elements and aspects to take care of above.
CMMI does that.
ISO also does that.
And Malcom Balridge also does that.
As for the intellectual pygmies, there is only one thing left for them to do.
Simply get lost.
"Things have changed, we shouldn't continue with ISO or CMMI or Malcolm Balridge".
"Now everyone is using Agile, it is so very different".
"Using CMMI means a lot of overhead".
Statements like the one above show just one thing.
The person making such statements is an intellectual pygmy.
As they say half knowledge is risky.
But no knowledge is simply fatal.
Some of these folks may be doing a lot of work that involves creating technical solution, designing system architecture, writing proposal, doing effort estimation, etc. but that by itself doesn't make them expert in anything.
They may not even be experts in the above activities.
Volume of processing a person has done can never be a true indicator of that person's efficiency and effectiveness.
An excellence framework is simply that.
A framework.
An overall approach.
Basics never change, they may get refined and fine-tuned over time.
The basic principles of project management have always been the same since ages:
- project germination or acquisition
- project initiation
- project planning
- project tracking
- project closure.
This was true a decade back, is true today and will be true a decade hence too.
The basic principles of software engineering have also always been the same since ages:
- problem definition/articulation (requirements)
- solution approach determination (design)
- solution implementation as per agreed approach (construction)
- checking of solution against approach being followed (verification)
- checking of solution against problem getting solved (validation)
Any excellence framework in the domain of project management and software engineering would contain elements and aspects to take care of above.
CMMI does that.
ISO also does that.
And Malcom Balridge also does that.
As for the intellectual pygmies, there is only one thing left for them to do.
Simply get lost.
