Component Enablement | Targetprocess - Enterprise Agility Solution

Component Enablement

Requires the following solution to be installed: Product Enablement (1b2923c7-d707-4bed-b0d1-275b6f70e341) ---------------------------------------------------------------------------------------------------------------------------------- Solution Overview A Component is a discrete and self-contained part or element of a larger system or structure. It is a fundamental unit with well-defined functionalities that

Trusted by Agile teams at show more

Requires the following solution to be installed:

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

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

Solution Overview

A Component is a discrete and self-contained part or element of a larger system or structure. It is a fundamental unit with well-defined functionalities that can be easily replaced or interchanged without affecting the overall system's functionality. Components are often designed to be modular, making them independent and reusable, which promotes code organization, maintenance, and scalability.

In software development, a Component refers to a modular piece of software that encapsulates specific functionality. These Components can be combined or integrated into a larger application or system to build complex software solutions. Using Components allows developers to break down a system into manageable and interchangeable parts, promoting code reusability and easier maintenance.

Components are also used in various other fields, such as electronics, engineering, and mechanical systems, where they represent individual parts that contribute to the overall functionality of a device or structure. In essence, a Component is a building block that, when combined with others, creates a complete and functional entity.

The solution enables a new Component, which is a part of one or many Products, and Component Versions. It also enables a possibility to define the Work Items related to a Component and Component Version development. 

Portfolio Epics, Epics and Features have many to many connections to a Component, which means they can be related to multiple different Components, while User Stories and Bugs can only have one related Component.

 

On a Component view, you will find a tab Products where you can see and connect the Products which include the Component. One Component can be a part of multiple Products.

On a Component view, you will see new tab Work Items with a Component Backlog such as Portfolio Epics, Epics (Capabilities) and Features connected to a Component, as well as User Stories and Bugs which are implemented within a Component. Here you can link existing Work Items to Component or create new ones. From this view you can easily manage and see the items developed for the Component.

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

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

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

 

On User Story and Bug views, you'll see a Component field in the right section.

 

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

Component Versions

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

On a Component Version view you can define what Product Versions it will be a part of.

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

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

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

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

Version 1.0

Integrations

See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.

Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.

For Transparency above the Team Level 
 
EXPAND 2 INTEGRATIONS

Azure DevOps
Azure DevOps
Add Targetprocess on top of the team level tool: get visibility on Product and Portfolio level.
Atlassian Jira Software
Atlassian Jira Software
Ensure free data flow from Jira to Targetprocess for greater visibility for all team members.

For Continuous Integration and Continuous Delivery 
 
EXPAND 6 INTEGRATIONS

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
GitLab
GitLab
Automatically link branches and merge requests to Targetprocess entities.
GitHub
GitHub
Automatically associate branches and pull requests with Targetprocess entities.
Phabricator
Phabricator
Link code revisions with any Targetprocess entity.
Bitbucket
Bitbucket
Automatically associate branches and pull requests with Targetprocess entities.
Jenkins
Jenkins
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.

For Product Management, ITSM, Sales and Marketing to Stay on the Same Page 
 
EXPAND 5 INTEGRATIONS

Miro
Miro
Centralize unstructured communication on Miro’s online whiteboard inside Targetprocess.
Microsoft Project Server
Microsoft Project Server
Provide visibility into high-level goals and details about implementation for all teams.
Salesforce
Salesforce
Synchronize customer service, sales, the PM office, and development teams.
Zendesk
Zendesk
Allow all team members to collaborate on shared artifacts from customer service tickets.
ServiceNow
ServiceNow
Collaborate on shared work items, consolidate reporting across the entire organization.