Controlled development processes
DI Manuel KathoferAll development processes work on the same problems:
Achieving quality, meeting deadlines and costs.
If industry standards (norms, specifications) or e.g. documentation duties are also required in addition to the regular development requirements, development teams often again split their focus. This is not necessary!
Quality management and project process models generally have the same intentions. But only if the right project process model is applied correctly does it actually create a benefit in its implementation.
The increased expenditure for specification and documentation is more than just refinanced by reduced QS cycles and efficient approval processes. Be it the V model XT or the use of different standards and ISO norms: The right application is what matters for success.
In addition, each time new technologies are used, this changes processes and procedures, which have already reached a certain level of maturity The loss of process maturity normally ends in the need to re-establish existing findings and proven experiences. As a result, when new technologies are introduced or implemented, it is particularly important to maintain the organisational level and process maturity.
Example: Current trends in SW project management relate to "Agile methods" and SCRUM. This idea is not new, though the name is. The main risk of introducing SCRUM is above all that of the iterative process drifting in the shape of "Sprints" and ending where it started: in an improvised and fragmented condition. CMMI calls this "downgrading" of e.g. CMMI level 2 "The repeatable process" to level 1 "The initial process".
Ten years ago, there was already a solution to all the problems
in the organisation of IT projects known today!
Make use of our experience in your change process -
With our help, you can avoid the next repetition!
DI Manuel Kathofer teaches the basics of this at higher education colleges and applies his many years of experience with his teams in numerous projects.
