Menu

Items filtered by date: December 2014 - Q:PIT Ltd

We don't need CMMI...

  • Published in Blog

“We don’t need no CMMI” (sung to the tune Pink Floyd’s “Another Brick In The Wall).

  • Another organization has stated that they don’t need CMMI because they already have an ISO certificate in the lobby. CMMI is not seen as a product used for improvement, it is perceived as a certification body, the goal is a maturity level.

  • We don’t want CMMI because we are flexible, our strength is to be able to change directions every day at the whim of the customer’s latest statement. CMMI is seen as a top-heavy bureaucratic process which will slow down as people follow large volumes of procedures and standards.

  • We can’t afford CMMI, we are investing in tooling. CMMI is not seen as a product which assists you in identifying needs and expectations for the selection of tools, it is an expensive and slow methodology which can easily be replaced by a new piece of software or a data storage facility.

  • We don’t use CMMI because we are not primarily a software development company. CMMI is not seen as a support in improving efficiency, customer satisfaction and results, it is seen as something developed 30 years ago for software development.

The very concept of process and process improvement is being more and more difficult to accept by organizations who are still, after all their previous failures, looking for the silver bullet. As consultants and publications remind people that CMMI is not a guarantee of quality, but an improvement of processes and practices, the feeling gets reinforced that this is a methodology which is not even willing to promise results.

Maybe I can try briefly to re-establish some basics about a proper usage of CMMI and other models.

  1. No model can satisfy your business needs if you do not understand and communicate your needs clearly. Process, measurement, tools…? None of these will work on their own as long as management as not clearly established their business goals and expectations.

  2. The CMMI, if properly implemented, should increase the maturity of your organization. Maturity is not a level, certificate or award, it is the capability of your organization to be able to rapidly react to changing circumstances through a clear understanding of why and what needs to be done, where to find the necessary information, and having the skills to implement recognized best practices rapidly and intelligently.

  3. CMMI expectations are not satisfied by someone in “an ivory tower” writing out procedures explaining to people who have experience and qualifications how to do their job; it must be a bottom-up approach in which people identify and help to remove the road-blocks to efficiency and effectiveness in their own work, with the support of their management.

  4. CMMI Maturity Levels do not mean you should not look at the higher maturity practices as long as you have not satisfied the lower ones. To the contrary, you need to start looking at all of them from the start, the maturity levels indicate that you will not get the full benefit of a practice as long as the lower level, elementary practices have not been implemented.

  5. The practices and standards which are recognized as being best for the organization need to evolve and be enforced, but the focus has to be on quality assurance and not, as so many have tried, compliance control: if the process does not satisfy the business need, the process is wrong and the users should not be forced to use it.

  6. Whatever you deploy or implement is wrong to start with. You need a good feedback loop which allows the continuous collection of recommendations, improvements and experiences to help correct the original defects in the process.

  7. Process improvement is not about documentation and control, it is about communication, learning and objectivity. You are not being asked to document everything you do, you are being asked to leave a trace so that later, we can look back, find out why something failed or succeeded, and what lessons can be learned to increase efficiency and effectiveness next time.

No miracles, then – but also no mysteries. If you have implemented CMMI correctly, focusing on the people in your organization and the needs of your people, it is a good demonstration that you have the maturity to understand your capabilities and limitations, and make commitments which you can satisfy.

If you have found a lead appraiser who was happy to give you the result you wanted, or whom you could fool into not seeing the issues within your organization, you have wasted your time and money, you will continue to deliver bad quality products, processes and services, and your customers will not trust you for long.

Of course, if you just want to be another brick in the wall...

Read more...

Minimum effort tools

  • Published in Blog

At a recent conference, I was impressed, once again, at the number of tools and easy solutions for sale. It appears that there is a great market out there for businesses who would like to pay a lot of money for a rapid solution to their problems. There was – among others – a vendor for a storage solution (disk drives) who assured us that this would solve all their DevOps issues.

For those who are not aware, DevOps is the latest buzzword in the software industry which, after recognizing that “Agile” methodologies were not quite sufficiently, are encouraging better communication between departments – in particular between software development, operations and QA. Just buy the tool and suddenly your people and departments all communicate and collaborate.

At the same conference, there was a track on “process” which was focusing on the challenges and opportunities related to changing the culture of an organization, in line with its business strategies, in order to improve (among other things) the sharing of lessons learned and the communication between teams and departments in order to allow better communication and collaboration. There were significantly fewer participants in this track, as it was focusing on helping people communicate rather than simple recipes and tools.

For many years, we have been complaining about the quality of our tools and silver bullets, while avoiding the basic concept that actually, the work is being done by people, not by the tools. Communication is between people and having great tools in place which allow you to share information rapidly and efficiently would be a complete waste of money if your people do not understand the need for communication. Having a tool in place will not help if you do not understand what information people need, when they need it and in what format.

It should be so simple: just do this and everything will work. Yet, every one of the pre-digested solutions falls short of expectations, because it does not fit the corporate, local or national culture.

Even in highly technical environments, you need to remember to work with people, changing the culture of the organization is critical to helping improvements to the business. Buying tools could help things go faster, but rarely will make people communicate more effectively. The result could be a giant repository of useless information, or an empty repository.

The same goes with all the methodologies and standards out there. Do everything recommended in CMMI, ISO, Agile, Prince2, and other methodologies and standards, you can still produce expensive, bad quality (but in a repeatable, measurable and predictable manner). However help your people understand the purpose and objectives, the reason why things needs to be done, may have amazing results, even if the tools and standards are not understood or implemented.

Read more...
Subscribe to this RSS feed