Monitoring and creating customized dynamic project files based on enterprise resources
One example method of operation may include identifying project files in a database, identifying one or more active project files and one or more inactive project files from the project files, retrieving one or more of the inactive project files, identifying one or more project risk metrics associated with the one or more inactive project files, and determining potential project risk metrics associated with the one or more active project files based on the one or more project risk metrics associated with the one or more inactive project files.
1. A method comprising:
executing a computer-implemented simulation to quantify a likelihood of failure of an active project file within a project management software application, the computer-implemented simulation including stress testing the active project file in accordance with operations that include:
identifying attributes of an active project from within contents of the active project file and identifying attributes of an inactive project from within contents of an inactive project file within the project management software application,
determining that an identified category attribute of the active project identified from the active project file corresponds to an identified category attribute of the inactive project identified from the inactive project file,
dynamically setting thresholds for the identified attributes of the active project based on values of the identified attributes of the inactive project file,
determining that the active project is at risk of failure based on a comparison of the identified attributes from the active project file with the thresholds dynamically set based on the values of the identified attributes from the inactive project file, and
dynamically reallocate a resource from another active project that has less of a risk of failure to the active project within the active project file via the project management software application to reduce a likelihood of the risk of failure of the active project.
2. The method of claim 1 , wherein the determining that the active project is at risk of failure includes:
determining that the identified attributes of the active project are within a predefined range of the thresholds dynamically set based on the values of the identified attributes from the inactive project file.
3. The method of claim 1 , wherein the method further comprises changing a deadline of a deliverable of the active project based on a deadline of a similar deliverable identified from the inactive project file.
4. The method of claim 1 , wherein the inactive project file corresponds to a previously completed project.
5. An apparatus, comprising:
a memory that stores project files of a project management software application in a database; and
a processor configured to execute a computer-implemented simulation to quantify a likelihood of failure of an active project file within the project management software application, the computer-implemented simulation including stress testing the active project file in accordance with operations that include:
identify attributes of an active project from within contents of the active project file and identifying attributes of an inactive project from within contents of an inactive project file within the project management software application,
determine that an identified category attribute of the active project identified from the active project file corresponds to an identified category attribute of the inactive project identified from the inactive project file,
dynamically set thresholds for the identified attributes of the active project based on values of the identified attributes of the inactive project file,
determine that the active project is at risk of failure based on a comparison of the identified attributes from the active project file with the thresholds dynamically set based on the values of the identified attributes from the inactive project file, and
dynamically reallocate a resource from another active project that has less of a risk of failure to the active project within the active project file via the project management software application to reduce a likelihood of the risk of failure of the active project.
6. The apparatus of claim 5 , wherein the processor is further configured to determine that the identified attributes of the active project are within a predefined range of the thresholds dynamically set based on the values of the identified attributes from the inactive project file.
7. The apparatus of claim 5 , wherein the processor is further configured to change a deadline of a deliverable of the active project based on a deadline of a similar deliverable identified from the inactive project file.
8. The apparatus of claim 5 , wherein the inactive project file corresponds to a previously completed project.
9. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform a method comprising:
executing a computer-implemented simulation to quantify a likelihood of failure of an active project file within a project management software application, the computer-implemented simulation including stress testing the active project file in accordance with operations that include:
identifying attributes of an active project from within contents of the active project file and identifying attributes of an inactive project from within contents of an inactive project file within the project management software application,
determining that an identified category attribute of the active project identified from the active project file corresponds to an identified category attribute of the inactive project identified from the inactive project file,
dynamically setting thresholds for the identified attributes of the active project based on values of the identified attributes of the inactive project file,
determining that the active project is at risk of failure based on a comparison of the identified attributes from the active project file with the thresholds dynamically set based on the values of the identified attributes from the inactive project file, and
dynamically reallocating a resource from another active project that has less of a risk of failure to the active project within the active project file via the project management software application to reduce a likelihood of the risk of failure of the active project.
10. The non-transitory computer readable storage medium of claim 9 , wherein the determining that the active project is at risk of failure includes:
determining that the identified attributes of the active project are within a predefined range of the thresholds dynamically set based on the values of the identified attributes from the inactive project file.
11. The non-transitory computer readable storage medium of claim 9 , wherein the method further comprises changing a deadline of a deliverable of the active project based on a deadline of a similar deliverable identified from the inactive project file.