Managing iterative processes

 

Managing iterative processes:

Iterative and Incremental development is a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interaction in between. The iterative and incremental development is an essential part of the Rational Unified Process , the Dynamic Systems Development Method, Extreme Programming and generally the agile software development frameworks.


Approaches like XP correctly emphasize the importance of communication and of removing artificial barriers to development productivity. XP to many might seem to be simply a license to hack. However, a more detailed examination of the techniques of XP shows that many are conscious techniques to counter the excesses of hacking and to ensure good maintainable code is written.

            Booch suggests that there are two level of development- the macro process and the micro process. The macro process closely related to the waterfall process model. At this level, a range of activities carried out by a variety of specialist groups has to be coordinated. We need to have some dates when we know that major activities will finished so that we know when we will need to bring in staff to work subsequent activities. Within this macro process there will be micro process activities which might involve iterative working. Systems testing has always been, how a sequential macro process can be imposed on a number of iterative sub-processes. With iterative micro processes the use of time boxes is needed to control at the macro level.

            There are cases where the macro process itself can be iterative. It might be that a prototype for a complex technical system is produced in tow or three successive versions, each taking several months to create and evaluate. In these circumstances, each iteration should be treated as a project in its own right.


Comments

Post a Comment

Popular posts from this blog

Decision making process

Image
  Decision making process:             These are the following steps involved in decision making process. 1)       Defining the Process: Decision making process really starts with defining the exact problem. The decision maker has to basically identify what exactly is the problem, before making a decision on the situation. A problem exists when there is difference between what is or will be happening and what should happen in given situation. The real and most basic cause of the problem must be identified. While defining the problem, it is essential to find out the critical or strategic factors of problem. These factors pose restriction or present obstacles in finding the solution to the problem. In adequacy of finance, limited managerial talent, low employee morale, adverse change in the government policy etc. are some of the critical factors which need a careful attention while deciding over a prob...
Read more

Steps in Planning Process

Image
  Steps in Planning Process: The steps in planning process are presented here in connection with major programs, such as the acquisition of a plant the development of a product, managers would follow essentially the same steps in any other through planning. Since minor plans are usually simpler, some of the steps would be more easily accomplished, but the practical steps listed below. In practice, however, managers must study the feasibility of possible courses of action at each step. These are the following steps of planning process. 1) Being Aware of Opportunities: This is first steps of planning. Although it precedes actual planning and is therefore not strictly a part of the planning process, an awareness of opportunities in the external environment as well as within the organization is the real starting point for planning. All managers should take a preliminary look at possible future opportunities and see them clearly and completely, know where they stand in light of their...
Read more

Stakeholders of project

  Stakeholders: These are people who have a stake or interest in the project. It is important that they be identified as early as possible, because you need to set up adequate communication channels with them right from the start. The project leader also has to be aware that not everybody who is involved with a project has the same motivation and objectives. The end users might, for instance, be concerned about the ease of use of the system while their managers might be interested in the staff savings the new system will allow. Stakeholders might be internal to the project team, external to the project team but in the same organization, or totally external to the organization. Internal to the project team : This means that they will be under the direct managerial control of the project leader. External to the project team but within the same organization: For example- the project leader might need the assistance of the information management group in order t...
Read more