Abstract:
A graphical interface module may provide a set of graphical presentations comprising at least: a Likelihood of Delivery chart showing a probability distribution of predicted delivery dates; a Delivery Date Risk Trend chart showing how the completion time for the project predicted according to the Likelihood of Delivery chart has changed over time; and a Burndown chart that shows at least work-items of planned work for the project. Each of the Likelihood of Delivery chart, the Delivery Date Risk Trend chart, and the Burndown chart has a timeline axis.
Abstract:
Mechanisms are provided for generating a shape tag cloud display. A user input is received that specifies an arbitrarily hand-drawn shape tag. A set of shape tag equivalence classes is updated based on the received user input to assign the arbitrarily hand-drawn shape tag to a shape tag equivalence class having similar previously entered arbitrarily hand-drawn shape tags. Rankings of the shape tags relative to one another are generated. The shape tag cloud display is generated based on the rankings. A representation of each shape tag within the shape tag cloud display has display characteristics based on the rankings. The shape tag cloud display is then output.
Abstract:
Incorporating user insights in predicting, diagnosing and remediating problems that threaten on-time delivery of a project may comprise gathering information. The information may be conveyed to one or more users. A user may be allowed to input a new value associated with the project, the new value assessed based on the information and representing an expert assessment of the information. The user may be allowed to also indicate a period of time the user considers the information to be applicable. The new value and the period of time may be incorporated into data used in a prediction algorithm that predicts probability distribution of completion time of the project as the project is progressing.
Abstract:
A user may be allowed to specify a change in one or more parameter data associated with the project, the one or more parameter data used previously to compute a probability distribution of completion time of the project. The probability distribution of completion time of the project may be recomputed based on the change. The recomputed probability distribution of the completion time of the project may be presented. An option to save the recomputed probability distribution may be provided. An option may be provided to specify another change in one or more parameter data associated with the project and repeat the recomputing and the presenting procedures based on another change in one or more parameter data associated with the project.
Abstract:
A user may be allowed to specify a change in one or more parameter data associated with the project, the one or more parameter data used previously to compute a probability distribution of completion time of the project. The probability distribution of completion time of the project may be recomputed based on the change. The recomputed probability distribution of the completion time of the project may be presented. An option to save the recomputed probability distribution may be provided. An option may be provided to specify another change in one or more parameter data associated with the project and repeat the recomputing and the presenting procedures based on another change in one or more parameter data associated with the project.
Abstract:
Historic and current development data associated with the project may be gathered. A catalog of patterns, each pattern associated with a data measure and an analysis routine capable of detecting the pattern according to the data measure in a given data set may be obtained. A pattern describes a particular indication in the historical and development data, which arises one or more of, at a discrete point in time or over a period of time. The analysis routine may be applied to the historic and current development data. A notification may be issued responsive to identifying the pattern in the historic and current development data. The applying and the issuing may be performed for each pattern in the catalog of patterns.
Abstract:
A graphical interface module may provide a set of graphical presentations comprising at least: a Likelihood of Delivery chart showing a probability distribution of predicted delivery dates; a Delivery Date Risk Trend chart showing how the completion time for the project predicted according to the Likelihood of Delivery chart has changed over time; and a Burndown chart that shows at least work-items of planned work for the project. Each of the Likelihood of Delivery chart, the Delivery Date Risk Trend chart, and the Burndown chart has a timeline axis.
Abstract:
A graphical interface module may provide a set of graphical presentations comprising at least: a Likelihood of Delivery chart showing a probability distribution of predicted delivery dates; a Delivery Date Risk Trend chart showing how the completion time for the project predicted according to the Likelihood of Delivery chart has changed over time; and a Burndown chart that shows at least work-items of planned work for the project. Each of the Likelihood of Delivery chart, the Delivery Date Risk Trend chart, and the Burndown chart has a timeline axis.
Abstract:
Mechanisms are provided for generating a shape tag cloud display. A user input is received that specifies an arbitrarily hand-drawn shape tag. A set of shape tag equivalence classes is updated based on the received user input to assign the arbitrarily hand-drawn shape tag to a shape tag equivalence class having similar previously entered arbitrarily hand-drawn shape tags. Rankings of the shape tags relative to one another are generated. The shape tag cloud display is generated based on the rankings. A representation of each shape tag within the shape tag cloud display has display characteristics based on the rankings. The shape tag cloud display is then output.
Abstract:
Scheduling a given event, in one aspect, may include obtaining a set of one or more business rules, obtaining analytics, and obtaining an event specification. The event specification may include at least one content specification and two or more transmission modes. The event may be scheduled based on the event specification, the analytics and the business rules. The scheduling may be indicated by a tuple comprising event content, one or more communication modes selected from the two or more transmission modes, and timing of the scheduled event.