Skip to main content
Project Management

Return to Answer

added 63 characters in body
Source Link
MCW
MCW
  • 8.7k
  • 2
  • 29
  • 49

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra formatConnextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

added 4 characters in body
Source Link
Todd A. Jacobs ♦
Todd A. Jacobs ♦
  • 50.7k
  • 7
  • 60
  • 181

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scopethe Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.

Source Link
Todd A. Jacobs ♦
Todd A. Jacobs ♦
  • 50.7k
  • 7
  • 60
  • 181

The Agile Approach

Story points are meant to convey level of effort or complexity for a unit of work, and the Connextra format typically used for user stories provides context and scope. However, while prioritization within the Product Backlog is often the main expression of business value, the actual value is more accurately tracked through a separate metric.

Technically, business value is determined by stakeholders, while prioritization is determined by the Product Owner. This is an important distinction, but the distinction is often blurred when people talk about agile approaches because most of the extant literature focuses on the Development Team rather than the Product Owner or stakeholder processes.

The general agile approach is to enable stakeholders to estimate business value based on agreed-upon criteria. This creates a consensus around the relative business value of your high-level product increments, which can then be used to prioritize the work.

Tools and Techniques

There are a wide variety of tools and techniques for implementing the agile approach outlined above. Among them, Mountaingoat Software provides a number of tools for deriving stakeholder-driven metrics of business value. Provided techniques include:

  • Relative Weighting

    Relative weighting is a prioritization approach that considers both the benefits of a feature and the cost of that feature. The technique is best applied for setting approximately quarterly goals rather than each sprint.

  • Theme Screening

    Theme screening is a useful and easy prioritization technique that can be used to prioritize themes and/or epics against one another. It can also be used to prioritize entire projects or products.

  • Theme Scoring

    Theme scoring is a prioritization technique that can be used to prioritize themes (groups of user stories) and epics (large user stories) against one another. It can also be used to prioritize projects or products against one another.

In general, all these approaches provide a numerical result that can be used to measure relative business value. This approach is highly flexible and very effective at building consensus among stakeholders, and only requires that you create buy-in among the stakeholders in the design of the filtering criteria and the choice of methodology. As long as everyone has agreed on how business value will be estimated, there is likely to be wide acceptance of the results.