project Evaluation

 

project Evaluation :

The purpose of this project evaluation is to assess the various software methodologies that were used throughout the development of the framework, the accuracy of the estimations, and the usefulness of the reviews. The product will be reviewed and evaluated for whether it accomplishes the ideas presented in the initial overview and for the quality of the product. Overall, the Spiral model development life cycle was used in the development of the framework. This model divides development into five main stages: requirements, design, coding, testing, and maintenance.

The success of a project, both technically and in business terms, is clearly built upon a sound initial evaluation of the technical, organizational and financial feasibility of the project. As will be seen, in some cases managers will be able to justify a commitment to a single project as the financial benefits will clearly exceed the costs of the implementation and operating of the new application. In the other cases, managers fulfillment of strategic objectives when combined with the outcomes of other projects.

Strategic programme management (strategic assessment) :

A different form of programme management is where a portfolio of projects all contribute to common objective. Take, for the example – a business like Amanda’s IOE which carries out maintenance work for clients. A customer’s experience of the organization might be found to be very variable and inconsistent. The employee who records the customer’s requirements is different from the people who actually carry out the work and different again from the clerk who deals with problem that has already been discussed at length with some other IOE employee. A business objective might require changes to a number of different systems which until now have been largely self contained. The work to reorganize each individual area could be treated as a separate project, coordinated at higher level as a programme.

These types of programme are most often needed by large organization which have a large and complicated organizational structure.

Technical assessment :

Technical assessment of a proposed system consists of evaluating the required functionality against the hardware and software available. Organizational policy, aimed at provision of a uniform and consistent hardware/software infrastructure, is likely to place limitations on nature of technical solutions that might be considered. The constraints will, of course, influence the cost of the solution and this must be taken into account in the cost benefit analysis.

Cost-benefit analysis:

The most common way of carrying out an economic assessment of proposed information system or software product, is by comparing the expected cost of development and operation of the system with the benefits of having it in place.

Assessment focuses on whether the estimated income and other benefits exceed the estimated costs. Additionally, it is usually necessary to ask whether the project under consideration is the best of number of options. There might be more candidate projects than can be undertaken at any time and in any case, projects will need to be prioritized so that resources are allocated effectively.

The standard way of evaluating the economic benefits of any project is cost benefit analysis, comprising of two steps.

·         Identifying and estimating all of the costs and benefits of carrying out the project and operating the delivered application: These include the development costs, the operating costs and the benefits that are expected to accrue from the new system. Where the proposed system is replacing any existing one, these estimates should reflect the change in costs and benefits due to the new system. A new sales order processing system, for example, could not claim to benefit an organization by the total value of sales – only by he increase due to the use of the new system.

·

·         Expressing these costs and benefits in common units: We need to evaluate the net benefit, that is, the difference between the total benefit and the total cost of creating and operating the system. To do this, we must express each cost and each benefit in some common unit, that is, as money.

·Most direct costs are relatively easy to identify and quantify in approximate monetary terms. It is helpful to categorize costs according to where they originate in the life of the project.

·         Development costs: Its include the salaries and other employment costs of the staff involved in the development project and all associated costs.

·         Setup costs: Its include costs of putting the system into place. These consist mainly of the costs of any new hardware and ancillary equipment but will also include costs of file conversion, recruitment and staff training.

·         Operational costs: Consist of the costs of operating the system once it has been installed.

·Benefits, on the other hand, are often quite difficult to quantify to quantify in monetary terms even once they have been identified. In cost-benefit analysis the focus has to be on the benefits that can be financially valued in some way-

·         Development costs.

·         Setup costs

·         Operational costs (List some of the benefits under the heading)

·         Quantified and valued benefits.

·         Quantified but not valued.

·         Identified but not easily valued.