Referring to the last entry I’ve put on productivity improvement, one person made a comment group Linkdin of quality in the software and information systems. Javier Garzas commented: it would also be comentable and piece key to improve the process of building software (which as a result can have the effects you mention). If we achieve a better process method of allowing in addition to reducing future maintenance costs and problems do double the work with the same effort, productivity is clear. I wanted to mention the comment of Javier Garzas, since it places emphasis on a fundamental point, and is that in the improvement of the software development process is the origin of the problems and the biggest headaches. Productivity improvement activities, as I mentioned in my entry, will be meaningless if they are guided by a strategy of improving the process of development.
I will explain. In my professional work work squarely in the world of Outsourcing of software development (we call Application Management), and these last years we have had the great fortune of working with large customers in strengthening processes of development of Outsourcing contracts. This coupled with the strategy that we have in CMMi, which for us is a fundamental tool, and serves as a roadmap for the improvement of the development process. This experience has led us, that when an organization asks us for help to start a process of transformation, for example, how to change Time & Material Outsourcing model to a managed model, how to make effective use of a factory of software etc always start with a diagnosis of the development process and evaluate the State of maturity of their processes in the organization. This allows us to know the customer’s organization and gives us visibility on what needs to be done to achieve the transformation that the customer asks us.