Complexity managed
The selection of the process models has a massive influence on the reliability of the estimation results. Process models in the area of IT/software projects differ from business process models and proceeding models. While the differentiation of business process and process model is already clear, the difference between process model and proceeding model is almost not present. In contrast of proceeding models, process models are characterized by the fact that all activities, their dependencies and the distribution of all roles involved in the project at all development levels are linked together.
Process models are used to control the complexity of projects. In general, they are separated in sequential, iterative, agile and meta models. The selection of the process model has a significant relevance, because effort and cost rather rise disproportional and do not act linear at bug fixing. Process models control the project run and have critical impact on risks and on the success of a project. Not every model is suitable for any project situation and environment, that means that for every project situation a matching process model exists.
For a prototype e.g. the „Rapid Application Development” (RAD) suits most, whereas for complex applications the „Rational Unified Process” (RUP) matches more. There is a big difference between a waterfall model with eight activities or a Rational Unified Process (RUP) classic in a SOA environment with 727 activities. Process models are a basic part of projects or product lifecycles. This is why advancement and permanent adjustment to changing parameters is useful.
For a prototype e.g. the „Rapid Application Development” (RAD) suits most, whereas for complex applications the „Rational Unified Process” (RUP) matches more. There is a big difference between a waterfall model with eight activities or a Rational Unified Process (RUP) classic in a SOA environment with 727 activities. Process models are a basic part of projects or product lifecycles. This is why advancement and permanent adjustment to changing parameters is useful.
Process models generally have the following advantages:
-
Abstraction from the existing project and thus the determination of the general development methodology („project culture“)
-
Enforcement of the correct sequence of all necessary development steps
-
Protection of the consistency of methods and tools in the project
-
Increased transparency and improved predictive planning
-
Development depends on the individual development engineer
-
Facilitation of the teaching and learn ability of the development process
-
Improvement of the process through theoretical consideration, analysis and experience
-
Assessment and certification (ISO 9000, SEI CMM/CMMI, ISO 15504 (SPICE))
The selection of the process model and tailoring is a management task.
That applies to:
-
Ideal process models for any project situation and/or environment don't exist
-
Process models must be adapted to the organization and project situation
-
The used process model must be adapted and developed continuously to the changing conditions
Cost Xpert supports all scientifically published process models and de-facto industry standards.
