Browse Prior Art Database

System and Criteria Based Dash Board View for Project Control & Management

IP.com Disclosure Number: IPCOM000129158D
Original Publication Date: 2005-Sep-29
Included in the Prior Art Database: 2005-Sep-29
Document File: 2 page(s) / 60K

Publishing Venue

IBM

Abstract

1 Background Project Management and Control are going through complex changes in the new world of outsourcing and multiple location development. The project management is growing complex due to multi site development and integration. For example, if we take the development example of Tivoli Identity Manager, we have development groups located in four continents and about nine different time zones. This leads to very complex network of management requirements and delivery schedules adherence. For example, if suddenly due to the change of requirements to deliver to a particular customer like UPS due to higher demand stakes, then it is very hard for the management to understand the co-requisites, pre-requisites, the testing requirements, the IDD-requirements, the globalization-requirements, the current state of the project and the delivery change. 2 Existing Solutions and Limitations Rational has Requirements Pro software which provides a method to record business requirements. However this software is used to define and control the business requirements and store them in a database. There is not method to define the criteria of the project based upon business requirements and then break them down into a schedule and subsequent line items. There is also no method to define the co-requisites and pre-requisites that are associated with a particular line item based on the criteria that was previously defined. Microsoft?s top seller Project ® software helps to define a project schedule and criteria. It also helps to generate reports based upon the static definitions that are already defined in the view. They are not based on the current state of the project and the unknown test requirements or the status of the project changes. However, they do not have an easy method to report the various stages of the project and subsequently see the current state of the project on criteria. If the view have to be changed based on a new criteria or requirement like delivery based on a customer that cannot be accomplished. The major limitation of the existing solutions is that the criteria of importance like customers focus, importance of line item or any other particular goal for an internal delivery are maintained statically in various project information capture systems. However, the effect of change or focus of the newer delivery to change needs of the market economics leaves companies into assemblage of teams for systematic requirements gathering and change prediction. This is a heavy financial burden and often results in resource waste and eventually scrapping of projects. 3 Problem Here is a list of problems that are currently associated with project management: · Multiple Sites of Development and Test environment · Merging of status from different systems is done manually instead of a live view of the project · Priorities of the customers and the effect of the change in delivery schedule based on priority is not easily predicted and requires manual intervention across the team members to determine the ripple effect · Middle management is burdened with the change in priorities, customer focus, and to understand the effect of a requirements change to the existing project environment.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

System and Criteria Based Dash Board View for Project Control & Management The invention is divided into two parts:
* System to collect live information about the status of various sub components that are associated with a state of a project
* Tree-View to see the various sub-stages that are associated with the project based on the criteria to modify the perspective

Here is a high level overview of the system that will be used to collect the information from various sources:

In the above pictures the status collection aspect can be distributed across multiple locations physically. For example, the development status is collected from different sites that are located around the world. This will allow independent and distributed development and status collection.

Criteria: The criterion is set of very high level business driving forces which are priority based. The criteria by themselves form the requirements which lead the project. For example, if one of the type of criterion is 'customer-type' and the list of driving requirements are: 'e-bay', 'Amazon' etc. If 'e-bay' is a higher priority customer and we want to re-arrange the deadline of the entire project for 'e-bay', then the driving force can be changed with priority being 'e-bay'. This will lead the dash board to update the status of the individual 'pre-requisite' management systems that are distributed across.

The various management systems will automatically update any decision made at the dash-board to allow various pre-requisites and co-requisites be managed and updated according to the new priority.

Dashboard Tree View: The dashboard is a view that will help to the management see...