Solution Enablement

Requires the following solution to be installed:

• Product Enablement (1b2923c7-d707-4bed-b0d1-275b6f70e341)

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

Solution Overview

A Solution comprises a collection of Products brought together to deliver value to both internal and external customers. It may encompass a group of related Products forming a product family or a combination of distinct Products aimed at achieving a specific objective. For instance, in the case of Microsoft Office, Excel, PowerPoint, and Microsoft Word would be considered individual Products within the Microsoft Office Solution. Similarly, if we take hardware example, when referring to tractors, wheels, motors, and other separate distinct Products that can be integrated into various types of tractors (Solutions).

The solution enables a Solution and Solution Versions objects that establishes a many-to-many connection with Products and Product Versions respectively. When engaging in discussions about the Solution, we have the ability to specify the Products that will be included in the Solution, along with Portfolio Epics connected to a Solution, and Epics (Capabilities), Features, User Stories, and Bugs, that will be implemented to support the Solution.

On a Solution view, you will find new tab Products where you can see and connect the Products comprising a Solution. One Product can be a part of multiple Solutions.

Also you can define a Solution Backlog by linking/creating Epics (Capabilities), Features, User Stories and Bugs related to a Solution.

You can also see Solution Backlogs in the left menu on a Solution Backlog view.

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

So, on a Portfolio Epic view there will be a new tab showing a list of related Solutions. 

On Epic (Capability), Feature, User Story and Bug views, you'll see a Solution and Solution Version fields in the right section.

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

Solution Versions

Also the solution helps to monitor Solution Versions. On a new Solution Versions tab you can create and see all the Solution 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 Solution Version, simply enter the Portfolio, which a Product Version belongs to, and a Version ID. It can be MVP and MMP Solution Version or just a numbered Version ID.

On a Solution Version view you can define what Product Versions will become a part of a Solution Version.

Also you can add extra Epics (Capabilities), Features, User Stories and Bugs that may not be a part of a Product but need to be implemented for Solution Version to be released.

When Epics (Capabilities), Features, User Stories and Bugs are created from a Solution Version view, they will automatically be linked to a respective Solution.

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

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

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

Version 1.0