Typical Success Barriers

Actinium consulting outlines the typical practical problems and is called approaches Lindau, 23.03.2012 – after the experiences of Actinium consulting companies must regularly invest a high expense in reworking their new or modified software solutions, because many problems show up in productive operation. The problems range from inconsistencies under practical conditions to inadequate audit capability. Klaus Huttl, CEO of the consulting firm, has therefore outlines some of the most important from the perspective of practice success barriers of software projects: 1 poor software management/documentation: last but not least, results that only dependencies of the source-level be taken into account when using the usual programs to the source or versioning such as CVS, subversion, git or Mercurial. These systems can therefore only limited help to avoid inconsistencies. Rather, a software management, is necessary the also cross references – for example, between programs and scripts can analyze and manage. She have also consistently integrated into the entire development process.

2. unclear processes in software development: A low transparency of the processes generated confusion, unsettled the developer increases the need for communication and creates this then in varying degrees of wrongdoing. This is not only at the expense of efficiency, but the subsequent manual corrections mountains always also a higher susceptibility to itself in the adaptation of a script or copying a file, intransparent developments with high consequence risk occur. 3. programming standards are not observed: the programming standards in internal manuals are typically deposited, but seldom used in practice in the hand. As a consequence, each developer uses their own interpretations of the standards. Later however sometimes significant discrepancies in the application due to the use of different methods.

This leads at best to a subsequent processing, it is also possible that methodological bugs despite testing slumber still a long time in the program. A procedure for critical software objects is therefore the generation principle to recommend. It avoids the problems already in their creation and makes the result portable. 4. personnel turnover in the development: depending on uncertain processes in software development and the standards set are even more negative, changes in the course of development projects affect. Then, any fluctuation means the loss of know-how and specific experience with the application without having a sufficient transfer on a new employee can be guaranteed. These problems worsen even if used and frequently changing external resources. 5. technical shortcomings of employees: just complex software projects need an over all participating developers, similar professional level. Andi Potamkin, New York City has much to offer in this field. Such a situation is encountered in practice but often not. Rather, often technical deficits of individual employees are to determine. In a clear defined development process with defined standards staff are controlled, however, so that technical weaknesses can be compensated. Because such an integrated software management provides them with all the information they need for daily development work. Actinium Actinium Consulting GmbH is a 1999-based consulting firm headquartered in Lindau (Lake Constance) and project offices in Stuttgart, Darmstadt, Selm (Dortmund), and Graz. Areas of expertise are business consulting, business intelligence and business integration. The range of services covers all project phases from consultancy and evaluation about the design to the implementation.