CLIAMS:1. A project assurance management system (102) comprising:
a processor (104);
a recommendation module (116) coupled to the processor to:
determine, for a project phase in a software project lifecycle of a project, one or more probable problems associated with the project phase, one or more probable problems being determined for at least one of a technological area and business landscape of the project, wherein the software project lifecycle comprises an information technology (IT) application lifecycle and an project management lifecycle, the IT application lifecycle relating to technical aspects of a project and the project management lifecycle relating to business aspects of the project; and
provide one or more recommendations to remedy the one or more probable problems to enhance an assurance indicator of the project phase, the assurance indicator representing state of the project phase and business value realized by the project phase; and
an assurance indicator determination module (120) coupled to the processor to determine the assurance indicator for the project phase, based on the one or more recommendations implemented in the project phase to remedy the probable problems.
2. The project assurance management system (102) as claimed in claim 1, wherein the assurance indicator determination module (120):
determines an assurance index of the project phase with respect to a plurality of assurance features, the plurality assurance features including a development feature, an operations feature, a quality assurance feature and a business feature; and
computes business value realized in the project phase, based on a plurality of goals define for the project phase;
and wherein the assurance indicator is based on the assurance index of the project phase and the business realized in the project phase.
3. The project assurance management system (102) as claimed in claim 2, wherein the assurance indicator determination module (120):
computes a goal assurance index for each of a plurality of goals defined for each of the plurality of assurance features, the goal assurance index being determined based on an index value and weightage associated with the goal; and
determines a feature assurance index for each of the plurality of assurance features, based on corresponding goal assurance indexes, wherein the assurance index for the project phase is determined based on the feature assurance index corresponding to each of the plurality of the assurance features.
4. The project assurance management system (102) as claimed in claim 2, wherein the assurance indicator determination module (120):
determines business value to be realized by each of the plurality of goals define for the project phase, based on a weightage associated with each of the plurality of goals;
computes business value lost, for each of the plurality of the goals, based on a reduction factor, the weightage, and the business value to be realized; and
determines net business value, based on the business value to be achieved and the business value lost, the net business value indicting the business value realized in the project phase.
5. The project assurance management system (102) as claimed in claim 4, wherein the assurance indicator determination module (120) determines business value lost due to non-implementation of recommendations, based on the business value to be realized, the weightage, and an auto assurance index, and wherein the business value lost is based on the business value due to non-implementation of the recommendations.
6. The project assurance management system (102) as claimed in claim 1, wherein the recommendation module (116) identifies a current project phase of the project, based on project progress information, and wherein the one or more probable problems are provided for the current project phase.
7. The project assurance management system (102) as claimed in claim 1, wherein the IT application lifecycle comprises at least one of a requirements phase, a design phase, a development phase, and a test phase, and the project management lifecycle comprises at least one of a business goals phase, an IT goals phase, an investment decisions phase, an operations phase, and a business change rollout phase.
8. The project assurance management system (102) as claimed in claim 1, wherein the quality assurance system further comprises a knowledgebase management module (114) coupled to the processor to:
gather data pertaining to a plurality of projects from at least one of an internal source and an external source, the data including at least one of the activities performed during various project phases of the plurality of projects, common defects in the activities, and available remedies for the defects;
classify the data into one or more groups, based the technology area and the business landscape; and
analyze the data, based on phase-key word data, to determine corresponding a project phase, the phase-key word data including a list of key words occurring frequently in the project phase.
9. A method for project assurance management, the method comprising:
determining, for a project phase in a software project lifecycle of a project, one or more probable problems associated with the project phase, one or more probable problems being determined for at least one of a technological area and business landscape of the project, wherein the software project lifecycle comprises an information technology (IT) application lifecycle and an project management lifecycle, the IT application lifecycle relating to technical aspects of a project and the project management lifecycle relating to business aspects of the project;
providing one or more recommendations to remedy the one or more probable problems to enhance an assurance indicator of the project phase, the assurance indicator representing state of the project phase and business value realized by the project phase; and
determining the assurance indicator for the project phase, based on the one or more recommendations implemented in the project phase to remedy the probable problems.
10. The method as claimed in claim 9, wherein determining the assurance indicator comprises:
determining an assurance index of the project phase with respect to a plurality of assurance features, the plurality assurance features including a development feature, an operations feature, a quality assurance feature, and a business feature; and
computing business value realized in the project phase, based on a plurality of goals define for the project phase;
and wherein the assurance indicator is based on the assurance index of the project phase and the business realized in the project phase.
11. The method as claimed in claim 10, wherein determining the assurance index of the project phase comprises:
computing a goal assurance index for each of a plurality of goals defined for each of the plurality of assurance features, the goal assurance index being determined based on an index value and weightage associated with the goal; and
determining a feature assurance index for each of the plurality of assurance features, based on corresponding goal assurance indexes, wherein the assurance index for the project phase is determined based on the feature assurance index corresponding to each of the plurality of the assurance features.
12. The method as claimed in claim 10, wherein determining the business value realized in the project phase comprises:
determines business value to be achieved by each of the plurality of goals define for the project phase, based on a weightage associated with each of the plurality of goals;
computing business value lost, for each of the plurality of the goals, based on a reduction factor, the weightage, and the business value to be achieved; and
determining net business value, based on the business value to be achieved and the business value lost, the net business value indicting the business value realized in the project phase.
13. The method as claimed in claim 9, wherein the method further comprises identifying a current project phase of the project, based on project progress information, and wherein the one or more probable problems are provided for the current project phase.
14. The method as claimed in claim 9, wherein the method further comprises:
gathering data pertaining to a plurality of projects from at least one of an internal source and an external source, the data including at least one of the activities performed during various project phases of the plurality of projects, common defects in the activities, and available remedies for the defects;
classifying the data into one or more groups, based the technology area and the business landscape; and
analyzing the data, based on phase-key word data, to determine corresponding a project phase, the phase-key word data including a list of key words occurring frequently in the project phase.
15. A non-transitory computer readable medium having a set of computer readable instructions that, when executed, perform a method to manage project assurance, the method comprising:
determining, for a project phase in a software project lifecycle of a project, one or more probable problems associated with the project phase, one or more probable problems being determined based on at least one of a technological area and business landscape of the project, wherein the software project lifecycle comprises an information technology (IT) application lifecycle and an project management lifecycle, the IT application lifecycle relating to technical aspects of a project and the project management lifecycle relating to business aspects of the project;
providing one or more recommendations to remedy the one or more probable problems to enhance an assurance indicator of the project phase, the assurance indicator representing state of the project phase and business value realized by the project phase; and
determining the assurance indicator for the project phase, based on the one or more recommendations implemented in the project phase to remedy the probable problems.
,TagSPECI:As Attached