Prioritization for product management

1 . A method implemented in program code stored on computer-readable storage code, the method prioritizing requirements for product release, comprising:

receiving customer satisfaction requirements for a pending product release;

receiving product manager input for the pending product release to meet a release schedule on time and on budget;

receiving developer business requirements for the product release to balance the business desires of the developer; and

processing the received customer satisfaction requirements, product manager input, and developer business requirements for the pending product release to output prioritized requirements.

2 . The method of claim 1 , wherein the product release is a multi-version release of a software product, each version being released at different times and each later-released version including updates and new components from a prior-released version.

3 . The method of claim 1 , wherein the one or more processing technique is selected to increase value-add requirements for each product release based on the perceived value to the customer.

4 . The method of claim 1 , wherein the one or more processing technique is selected to increase value-add requirements to the developer.

5 . The method of claim 1 , wherein the one or more processing technique is selected based on associated anticipated cost, technical risk, relative impact, and other market-related aspects to the developer.

6 . The method of claim 1 , wherein the one or more processing technique is selected to support flat structures.

7 . The method of claim 1 , further comprising implementing a VOHCV analysis by:

assigning global weights to core business values;

receiving input from each stakeholder for each business value feature reflecting how a feature affects the requirement from a respective stakeholder perspective;

assigning requirement distribution points assigned to each requirement based on the feature weights and values;

determining the final priorities for the requirements at a level of interest, the determination performed across blocks within a same level to indicate that all requirements located at a specific level are prioritized relative to each other;

determining the final priorities based on the consolidated stakeholders weighted priorities; and

determining the final ranks on the final priority value assigned to each requirement.

8 . The method of claim 1 , further comprising implementing a HBMIA analysis by:

determining a DoM and DoC for existing and new components, and determining total impact associated with each goal;

prioritizing the DoM/DoC factors to determine to which extent each factor impacts the DoM/DoC relative to the other factors;

normalizing a prioritization vector (β);

prioritizing components with respect to each DoM/DoC factor to determine how the DoM/DoC for each component is affected by each DoM/DoC factor;

normalizing the values of a prioritization vector (Φ);

determining the relative priorities of components based on “experts” in the field and historical metrics data for each component;

prioritizing components with respect to each expert based on familiarity and experience with each component;

normalizing the values of a prioritization vector (δ);

prioritizing the experts in the field with respect to each other by assigned a relative weight to reflect the importance and maturity of each with respect to the developer;

prioritizing the values of the prioritization vector (δ);

determining the DoM/DoC values for each component by aggregating the different contributions from the experts in the field, and historical data based on the assigned weights;

determining the extent of modification (XoM) for each component;

compiling a list of components impacted by implementing each new goal; and

determining total impact of implementing goal (g) in the existing product.

9 . The method of claim 1 , further comprising implementing a VP analysis by:

determining a value point counting type;

identifying requirement categories;

determining a Stakeholder Adjustment Factor (SAF), wherein each stakeholder is assigned a weight reflecting how important the stakeholder is to the developer and/or the product;

evaluating a Value Adjustment Factors (VAF), wherein a value for an adjustment factor to be applied to the (UVP) is determined.

determining the value of the adjustment factor;

determining a Value Adjustment Factor (VAF);

determining a Weighted Adjusted Value Point (WAVP) for non-functional requirements over all the stakeholders;

determining an Adjusted Value Point (AVP) for functional requirements; and

determining product Total Value Point (TVP) value for product requirements.

10 . A computer program product including program executable to prioritize requirements for product release, the program code executing to:

receive satisfaction requirements input by a customer for a pending product release;

receive product release information input by a program manager to meet a release schedule on time and on budget;

receive business requirements input by a developer for the product release;

process the satisfaction requirements, input by the product manager, and business requirements; and

output prioritized requirements to increase or maximize value for the customer and the developer and increase overall satisfaction with the product when the product is released.

11 . The computer program product of claim 10 , further comprising implementing a VOHCV in program code by:

assigning global weights to core business values;

receiving input from each stakeholder for each business value feature reflecting how a feature affects the requirement from a respective stakeholder perspective;

assigning requirement distribution points assigned to each requirement based on the feature weights and values;

determining the final priorities for the requirements at a level of interest, the determination performed across blocks within a same level to indicate that all requirements located at a specific level are prioritized relative to each other;

determining the final priorities based on the consolidated stakeholders weighted priorities; and

determining the final ranks on the final priority value assigned to each requirement.

12 . The computer program product of claim 10 , further comprising implementing a HBMIA in program code by:

determining a DoM and DoC for existing and new components, and determining total impact associated with each goal;

prioritizing the DoM/DoC factors to determine to which extent each factor impacts the DoM/DoC relative to the other factors;

normalizing a prioritization vector (β);

prioritizing components with respect to each DoM/DoC factor to determine how the DoM/DoC for each component is affected by each DoM/DoC factor;

normalizing the values of a prioritization vector (Φ);

determining the relative priorities of components based on “experts” in the field and historical metrics data for each component;

prioritizing components with respect to each expert based on familiarity and experience with each component;

normalizing the values of a prioritization vector (δ);

prioritizing the experts in the field with respect to each other by assigned a relative weight to reflect the importance and maturity of each with respect to the developer;

prioritizing the values of the prioritization vector (δ);

determining the DoM/DoC values for each component by aggregating the different contributions from the experts in the field, and historical data based on the assigned weights;

determining the extent of modification (XoM) for each component;

compiling a list of components impacted by implementing each new goal; and

determining total impact of implementing goal (g) in the existing product.

13 . The computer program product of claim 10 , further comprising implementing a VP analysis in program code by:

determining a value point counting type;

identifying requirement categories;

determining a Stakeholder Adjustment Factor (SAF), wherein each stakeholder is assigned a weight reflecting how important the stakeholder is to the developer and/or the product;

evaluating a Value Adjustment Factors (VAF), wherein a value for an adjustment factor to be applied to the (UVP) is determined;

determining the value of the adjustment factor;

determining a Value Adjustment Factor (VAF);

determining a Weighted Adjusted Value Point, (WAVP) for non-functional requirements over all the stakeholders;

determining an Adjusted Value Point (AVP) for functional requirements; and

determining product Total Value Point (TVP) value for product requirements.

14 . The computer program product of claim 10 , further comprising implementing a VORM analysis in program code by:

defining a number of product releases (n) based on stakeholders.

determine a number (m) of requirements to be implemented and distributed over the product releases (R1 to Rm);

characterizing a release plan is characterized by a vector (x) of decision variables;

modeling requirements dependency and taking into consideration while planning the release contents;

evaluating a number of parameters affecting a release planning problem for each product release by editing the parameters based on product conditions

using the prioritization analysis for planning the release contents taking into consideration any conflicting perspectives of different stakeholders with respect to different criteria affecting each requirement; and

outputting different release plans with different objectives.

15 . A system for prioritizing requirements for product release, comprising:

a computer architecture configured to:

receive customer satisfaction requirements for a pending product release;

receiving product manager input for the pending product release to meet a release schedule on time and on budget; and

receiving developer business requirements for the product release to balance the business desires of the developer;

computer readable storage configured to store program code to process the received customer satisfaction requirements, product manager input, and developer business requirements for the pending product release; and

an output device configured to output prioritized requirements and increased or maximized value for the customer and the developer to increase overall satisfaction with the product when the product is released based on the at least one analysis.