Ways of categorizing software projects

Scenario : The organization has Project's which they had been undertaking themselves and working for various clients. Now they want to give the project's to other organizations as well. However, customer wants to categorize the Project's so that on the Project Display screen he would be able to see the Project's which was undertaken by his organization as one category and also the project's that has been assigned to other companies as another category.

Resolution : On the Project Display screen it is not possible as there are only two filter's which are " My Project's" and " All Project's" and there are no more drop down options which can be provided. Please follow the steps below to create a User Defined Field and categorize the Project's accordingly. Service level agreements are becoming increasingly important as organizations contract out functions to external service suppliers. Projects may be distinguished by whether their aim is to produce a product or to meet certain objectives.

A project might be to create a product the details of which have been specified by the client. The client has the responsibility for justifying the product. On the other hand, the project might be required to meet certain objectives. There might be several ways of achieving these objectives in contrast to the constraints of the product-driven project.

One example of this is where a new information system is implemented to improve some service to users inside or outside an organization. The subject of an agreement would be the level of service rather than the characteristics of a particular information system.

Many software projects have two stages. The first stage is an objectives-driven project, which results in a recommended course of action and may even specify a new software application to meet identified requirements. A project might be to create a product the details of w hich have been specified by the client. The client has the responsibility for justifying the product. On the other hand, the project might be required to meet certain objectives. There might be several ways of achieving these objectives in contrast to the constraints of the product-driven project.

One example of this is where a new information system is implemented to improve some service to users inside or outside an organization. The subject of an agreement w ould be the level of serv ice rather than the characteristics of a particular information system.

Many software projects have two stages.