Product Enablement

Can be extended with the following solutions:

• Product Hierarchy (88222ebf-5593-465b-a673-aff14133c8b2)
• Solution Enablement (ffdee4ab-caab-45ad-b788-1ac5ab428fcf)
• Component Enablement (d5d19bdf-87e4-42a9-afd4-0d387651e9db)

-----------------------------------------------------------------------------------------------------------------------------------

Solution Overview

A Product is a tangible or intangible item created, manufactured, or developed to satisfy a specific need or want of consumers or businesses. It can be a physical object, such as a car, smartphone, or clothing, or it can be an intangible service, such as a software application, consulting service, or insurance policy. In essence, a Product is anything that is offered for sale or exchange in the market.

There are two main types of products:

1. Goods: These are physical, tangible items that can be seen, touched, and owned. Examples of goods include electronic devices, household appliances, furniture, and food products.
2. Services: These are intangible offerings that provide value through a specific task, expertise, or assistance. Services can include things like healthcare services, financial advice, transportation, and entertainment experiences.

Products can vary in complexity and scope, ranging from simple everyday items to highly sophisticated technology or industrial equipment. They are created to fulfill the needs and desires of consumers, solve problems, improve efficiency, or simply provide enjoyment and convenience.

In the business world, products play a central role in generating revenue for companies. The successful development, marketing, and sale of products are essential for a company's growth and profitability. Throughout the product lifecycle, companies may refine, update, or expand their product offerings to stay competitive and meet changing market demands.

The solution enables new Product and Product Versions objects and connections of them to Work Items such as Portfolio Epics, Epics (Capabilities), Features, User Stories, and Bugs. 

After installing the solution, a new folder Products will appear in the left menu. On a Product Backlog view you can see a list of Products and it's backlogs – related Features, User Stories and Bugs. Here you can easily create new Products and start managing Product Backlogs.

On a Product view, you will see new tab Work Items with related to a Product work items such as Portfolio Epics, Epics (Capabilities), Features, User Stories, and Bugs. Here you can link existing Work Items to Products or create new ones. From this view you can easily manage and see the items developed for the Product.

Portfolio Epics and Epics have many to many connections to a Product, which means a they can be related to multiple different Products, so that you can define which Products are affected when implementing Portfolio Epics or Epics (Capabilities). Features, User Stories and Bugs can only have one related Product, as they usually implemented within one Product.

So, on a Portfolio Epic, and Epic (Capability) views there will be a new tab showing a list of related Products. 

On Feature, User Story and Bug views, you'll see a Product and respective Product Versions fields in the right section.

By connecting Work Items to Products, you can now better manage Product Backlogs and build any reports around Products.

Product Versions

Also the solution helps to monitor Product Versions. On a new Product Versions tab you can create and see all the Product Versions, see the details when the work on them started and finished as well as what Planning Interval it's planned to.

When creating a new Product Version, simply enter the Portfolio, which a Product Version belongs to, and a Version ID. It can be MVP and MMP Product Version or a numbered Version ID to it.

On a Product Version view you can define what Features, User Stories and Bugs should be implemented in this Product Version.

When Features, User Stories and Bugs are created from a Product Version view, they will automatically be linked to a respective Product.

Note 1: You can't delete a Product with Product Versions in final state. Just move it to the final (Retired) state to avoid data loss.

Note 2: When you delete a Product with no Product Versions in the final state, then it'll delete all the Product Versions as well.

---------------------------------------

Version 1.5