Tackle instances have key parameters that are configured in the Controls window prior to migration by the project architect and can be added and edited as needed.
These parameters define applications and individuals, teams, verticals or areas within an organization affected or participating in the migration.
The steps to creating and configuring a Tackle instance can be performed in any order, but the suggested order below is the most efficient for creating stakeholders and tags.
Stakeholders
Tags
Tackle stakeholders and defined by:
Follow the steps below to create a new stakeholder group. There are no default stakeholder groups defined.
Procedure
Tackle uses the job function attribute to classify stakeholders and provides a list of default values that can be expanded. Follow the steps below to create a new job function not included in the default list.
Procedure
Follow the steps below to create a new migration project stakeholder.
Procedure
Tackle uses the business services attribute to define the departments within the organization that use the application and will be affected by the migration.
Important: Business services must be created prior to creating or importing applications.
Follow the steps below to create a new business service. There are no default business services defined and must be created prior to creating applications.
Procedure
Tackle uses tags to classify applications in multiple categories. Follow the steps below to create a new tag type not included in the default list.
Procedure
Follow the steps below to create a new tag not included in the default list.
Procedure