Workspaces
Workspaces in ADOIT serve as collaboration hubs for enterprise architecture. They bundle together multiple functionalities to provide a guided approach to solving specific business needs and to empower the user to perform all relevant tasks and make decisions with a clear focus.
Templates
A workspace is created based on a template. In ADOIT 17.3, the following templates are available:
The Workspaces Page
The Workspaces page shows all workspaces that have been created. If no workspaces are available yet, the templates for creating new workspaces are displayed instead.
Open Workspaces Page
To open the Workspaces page:
- Select Workspaces from the dropdown menu at the top left corner of the program window.
Create New Workspace
See Create Workspace.
Open a Workspace
All workspaces are shown as tiles, sorted alphabetically.
- To open a workspace, click it.
Create Workspace
You can create new workspaces on the Workspaces page:
Click New workspace and choose a template:
To learn more about a template, select Preview.
Once you've made your decision, select Use or click anywhere on the tile to proceed.
noteIf no workspaces have been created yet, you can pick a template directly on the Workspaces page.
On the Set up your workspace page, enter the required information and set permissions:
Workspace name: Enter the name of the new workspace.
Description: Optionally, enter a description of the new workspace.
Add users: Select the users you want to collaborate with. Start typing the username or email address of a user, and then select the one you want when you see it. If you enter an email address that is not associated with any user, you need to enter the full email address. Add additional users as needed.
Choose which permissions users should have for the new workspace. Users can either be members or admins (see below).
Private workspace: Choose whether the workspace should be private (= only visible for members and admins).
Optional: If you are creating a roadmap, the workspace setup has three pages rather than one:
Click Next to advance to the next page of the setup.
Select the element types to consider in your workspace. The available options depend on the chosen template. For example, for Application-based Roadmaps, you can consider application elements such as
Application Components or 
Application Services.Click Next to advance to the final page of the setup.
Choose a prioritisation method for assessing your requirements. You can either select the Value vs. Effort Method or the Eisenhower Matrix.
Click Create workspace.
The first page of the workspace appears, and you can start working on the content right away.
User Types Explained
Any person invited to join a workspace starts out as a member. Members have access to all content within a workspace. They can capture and assess architecture artefacts if they have sufficient user rights.
The person who created the workspace starts out as an admin. Admins can do everything a member can do. Additionally, they can add or remove users from a workspace, make workspaces private or public, and rename or delete workspaces.
Who Can View and Edit Workspaces?
If a workspace is set to private, only users explicitly designated as members or admins can view and edit it.
If a workspace is not set to private, all users with write access to the "Objects" group—the main object group in the Object Catalogue—are treated as members, meaning they can capture and assess architecture artefacts within the workspace. Users with read access to the "Objects" group, however, can only view and edit workspaces where they are explicitly designated as members or admins.
Invitation Emails and Access to the Workspace
After the workspace is created, ADOIT sends invitation emails to all users you have invited to collaborate (provided they have an associated email address) as well as to any other email addresses you have specified that are not linked to a user account.
These invitation emails contain a link to the workspace. A login to ADOIT is required to access the link. If the recipient of the invitation does not yet have a ADOIT user account, one must be created.
Before ADOIT can send emails, the mail settings must be set correctly in the ADOIT Administration (see Email in the Administration Help).
Application Investment Planning
The Application Investment Planning template is a collaborative tool for assessing the fitness of your application portfolio and defining an investment strategy accordingly.
Which Elements Are Used?
Application Investment Planning is enabled for
Application Components (=
applications).
How Does Application Investment Planning Work in ADOIT?
To begin, set up an Application Investment Planning workspace (see Create Workspace).
Once you have created the workspace, follow these four steps:
These steps are discussed in more detail in the following sections.
Application Assessment
The first page of the Application Investment Planning template lets you add applications and assess them.
Define the Set of Applications You Want to Evaluate
First, you need to define the applications you want to assess.
Choose one of the following options:
Add: Search for existing applications, or create new ones. Start typing the name of an application, and then select the one you want when you see it. If the application does not yet exist, finish typing the name of the new application, and then press <Enter> to create a new application.
Import: Import applications from the repository. Select the applications you want to assess, and then click OK.
When you create new applications, they will be saved in the object group "Personal Objects\<username>\Application Component". In the other ADOIT scenarios such as "Design & Document", you can access this group via the Explorer.
Assess the Fitness Level
Once the applications have been defined, they must be assessed by answering a set of questions about their business and IT fitness.
Both Business fit and IT fit must be assessed for each application. There are two ways to do so:
Fill Out a Survey on Your Own: In the Business fit or IT fit column, click an Open survey
, and then click Assess.
Answer the survey questions, and then click Submit.Send Out a Survey to the Application Expert: In the Business fit or IT fit column, click an Open survey
, and then click Delegate.
Start typing the username of a user, and then select the one you want when you see it. Click
Send survey to send out the survey.
When the assessment is finished, the survey will be marked as Done. The button will turn green,
displaying the overall score 
.
See Workspaces: How the Score of a Survey Is Calculated for an explanation of how the overall score for an element is calculated.
Before you can send out a survey to another user, the mail settings must be set correctly in the ADOIT Administration (see Email in the Administration Help).
Survey recipients are automatically added to the workspace as members - they do not have to be explicitly added on the Set up your workspace page.
Other Survey Status
If an application has already been assessed in a different workspace, it will be marked as Open, but will display the overall score
.If an application has already been assessed, but the assessment is more than 365 days old, it will be marked as Outdated, and the button will turn orange
.If the assessment of an application has already started but not yet been completed, it will be marked as Pending, and the button will turn dark yellow
.
Additional Options
The following additional options are available on the first page of the Application Investment Planning template:
To filter applications, in the Filter... box, type the text you want to search for.
To remove an application, hover over the application, and then click the Remove application button
.To open the Insights dashboard of an application, hover over the application, and then click the Insights button
.To rename an application, hover over the application, and then click the Edit button
.
After adding your applications and finishing the assessment, select page 2 from the navigation menu at the top to advance to the next page of the template.
TIME Definition
The second page of the Application Investment Planning template lets you see the TIME categorisation of your applications. Gartner’s TIME model proposes four investment strategies (Tolerate, Invest, Migrate and Eliminate).
For additional information about the four investment strategies, take a look at Application Portfolio Strategy: Five Steps To Assessing Your Investment Decisions.
ADOIT will calculate the fitness score of your applications based on the survey results (see Assess the Fitness Level) and place them in the appropriate investment strategy quadrant. The quadrants measure the technical quality of an application against the business value it brings to the organisation.
Change Thresholds
The x and y axes represent the thresholds between the TIME categories in the chart. To change a threshold:
- Drag the axis to a new position.
The new threshold will be saved to the workspace. Applications will be re-rendered in a different colour if they fall into a different category after a threshold change. Additionally, the Kanban board on the Investment Strategy page will be updated to reflect the changes.
Use the Categories List
The TIME categories and the applications that belong to these categories are listed next to the chart. The following options are available:
To filter applications, in the Filter... box, type the text you want to search for.
To collapse or expand one of the assessment categories, click on it.
To highlight an application in the chart, select it in the list.
To open the Insights dashboard of an application, hover over the application, and then click the Insights button
.
Once you gained an overview of the suggested investment strategies, select page 3 from the navigation menu at the top to advance to the next page of the template.
Investment Strategy
The third page of the Application Investment Planning template allows you to view and modify the investment strategies for your applications.
This page contains a Kanban board where each column represents a specific investment strategy. Each application is represented by a card and is automatically placed in the appropriate column based on the previously assessed fitness score. Applications that have not yet been assessed (see Assess the Fitness Level) are listed on the left. You can confirm the proposed strategy, or drag the card to another column if you disagree with the suggestion.
Get More Information
Before you finally decide on an investment strategy, make sure to check all the information ADOIT provides. The cards on the Kanban board will show you the current assessment state of an application:
[no icon]: The application has not been assessed yet.
Warning Icon: The application has been assessed, but no investment strategy has been confirmed yet.
Alternatively, the application has an investment strategy, but it was set outside the workspace
and differs from the proposed strategy.
Outside the workspace means that the investment strategy was set in another workspace or in another ADOIT scenario such as "Design & Document" (by changing the value of the Investment strategy property in the chapter "Lifecycle").
Info Icon: The application has a confirmed investment strategy.
You can open a card to show more information:
- Click the warning icon or the
info icon. The detail view of
the card opens.
If an application has not been assessed yet, you cannot show more information.
The following information appears in the detail view of the card:
Name of the application as well as Business fit score and IT fit score from the assessment on the Application Assessment page.
Based on calculation: The investment strategy that ADOIT calculates based on the survey data.
Company benchmark: The predicted investment strategy according to a machine learning analysis of previous decisions made for similarly assessed applications in your organisation. The probability according to the prediction model that this prediction is a hit is shown in parentheses. If the probability is less than 35% or the application has not been assessed, no predicted investment strategy will be displayed.
- Current investment strategy:
If the application has an investment strategy, but it was set outside the workspace and differs
from the proposed strategy, it will be displayed here.
- Accept position: If the
application has been assessed, you can accept the investment strategy.
- Confirmed by and Confirmed
on: If the application already has a confirmed investment strategy, you can see who confirmed
it and when.
Choose the Investment Strategy
Once you have gathered all of the necessary information, you can make a final decision on the investment strategy for each application. Choose one of the following options:
Based on Calculation: Confirm the investment strategy that ADOIT calculates based on the survey data. Click the
warning icon to open the card,
and then click Accept position.Company Benchmark: Choose the investment strategy recommended by a machine learning algorithm based on prior selections made for similarly assessed applications. Drag the card to the proposed column on the Kanban board.
Make Your Own Choice: Choose the investment strategy yourself. Drag the card to another column on the Kanban board. In this way, you may even define an investment strategy for applications that have not yet been assessed and are listed on the left.
On accepting the investment strategy on the Kanban board, the following properties of the application are updated:
Business fit
IT fit
Investment strategy
These properties can be found in the chapters "Classification" and "Lifecycle".
During the update, the Business fit and IT fit assessment scores are converted to the predefined values in the "Classification" chapter as follows:
- 0-25: Bad | 26-50: Medium | 51-75: Good | 76-100: Excellent
Additional Options
The following additional options are available on the third page of the Application Investment Planning template:
To filter applications, in the Filter... box, type the text you want to search for.
To open the Insights dashboard of an application, click the Insights button
.To change the different investment strategy of an application, drag the card to another column on the Kanban board.
Once you have confirmed the investment strategy, select page 4 from the navigation menu at the top to advance to the final page.
Summary
The last page of the Application Investment Planning template offers a summary of all the applications in the workspace. This page has the following areas:
Applications in Total: The total number of applications in the workspace as well as the number of applications per assessment status (see below). Hover over a segment of the pie to see a tooltip with the names of the applications with that assessment status.
Applications With Accepted Investment Strategy: The total number of applications with a confirmed investment strategy as well as the number of applications in each TIME category. Hover over a segment of the pie to see a tooltip with the names of the applications in that category.
What's Next?: Check out possible next steps here. Define your requirements based on your defined investment strategy and plan your strategic roadmap. Or, how about a free online training about application portfolio management with ADOIT and ArchiMate?
Assessment Status Explained
Applications can have the following assessment status:
Open: Assessment still pending
In progress: Application is currently being assessed
Assessed: Assessment has been completed
Outdated: Assessment has been completed but it is outdated
Best Practices
Here are some tips to help you use Application Investment Planning in ADOIT more effectively.
One or Many Workspaces?
Rather than using a single large workspace, organise your applications into different workspaces for different areas of the organisation. This helps in maintaining confidentiality and makes it easier to keep an overview.
Assess Regularly, Reuse Workspaces
Assess your applications regularly (at least once a year) to make sure the evaluation is still valid. Reuse existing workspaces for this so that the survey data remains, since it would otherwise be lost because it is saved in the context of the workspace.
Applications in Multiple Workspaces
An application can be in more than one workspace. Be aware that the last accepted investment strategy applies to all workspaces.
Application-Based Roadmap
The Application-based Roadmap template is a collaborative tool for planning the requirements associated with your application elements.
Which Elements Are Used?
Application-based Roadmaps start from a set of application elements such as
Application Components or
Application Services and then
focus on their 
Requirements.
How Do Application-Based Roadmaps Work in ADOIT?
You can start from scratch or build on applications you've already evaluated in an Application Investment Planning workspace.
To begin, set up an Application-based Roadmap workspace (see Create Workspace).
Once the workspace is set up, follow these six steps:
These steps are discussed in more detail in the following sections.
Select Application Elements
The first page of the Application-Based Roadmap template lets you add application elements to the roadmap.
Select Application Elements for Requirements Assignment
To define what application elements you want to work with:
From the Element types list at the top left, choose the type of application element you want to add to the roadmap. Depending on your workspace settings, you may choose
Application Components,
Application Interfaces,
Application Services and
Application Functions. If
only one option is available, it will be automatically selected. After choosing, all elements of
that type will be displayed.To add an element, click the
Add button. To remove an element, click the
Remove button. For bulk
actions, you can use the Add all link provided at the top of the page.
Filter by Investment Strategy, Lifecycle State, Workspace or Group
When you choose Application
Components from the Element types list, you can apply the following filters to hone in on the
specific elements you need:
Investment strategy: Use this filter to select applications with confirmed investment strategies according to Gartner's TIME model (Tolerate, Invest, Migrate, and Eliminate), as well as those with no confirmed investment strategy (indicated by "No entry").
Lifecycle state: Use this filter to select applications based on their lifecycle state (Draft, In development, In production, and Retired). You can also include applications without a confirmed lifecycle state (indicated by "No entry").
All Application Components will
display their investment strategy and lifecycle state.
- Workspace: Use this filter to select applications that you have already evaluated in an Application Investment Planning workspace.
Additionally, the following filter is available for all types of application elements:
- Groups: Use this filter to select application elements from specific object groups.
You can apply multiple conditions to each filter and combine different filters if required.
Additional Options
The following additional options are available on the first page of the Application-Based Roadmap template:
To find elements, in the Filter... box, type the text you want to search for.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename an application element that has been added to the workspace, hover over the element, and then click the Edit button
.
After adding your application elements, select page 2 from the navigation menu at the top to advance to the next page of the template.
Define Requirements
On the second page of the Application-Based Roadmap template, you can define requirements for all application elements that have been added to the workspace.
The application elements are listed along with their associated requirements. Furthermore, for
Application Components, the
current investment strategy and lifecycle state is also visible.
Add Requirements to Application Elements
There are two ways to add requirements to an application element. Choose one of the following options:
Add Requirement: Click Add Requirement below the element to search for an existing requirement or create a new one.
Start typing the name of a requirement, and then select the one you want when you see it. If the requirement does not yet exist, finish typing the name and press <Enter> to create it.
To see more options, click Show more. This opens a support dialogue with the following tabs:
Assigned requirements: Displays all requirements already assigned to the element.
All existing requirements: Lists all requirements in the repository. You can filter requirements, select the ones you want to assign, and click Add.
AI: Click AI to browse AI-generated requirement suggestions. A list of relevant requirements will be created based on an AI model.
You can filter the results, select the requirements you want to assign, and click Add.
AI-generated suggestions must be enabled by your ADOIT administrator for each repository.
Additional Options
The following additional options are available on the second page of the Application-Based Roadmap template:
To filter requirements, in the Filter Requirements... box, type the text you want to search for.
To filter application elements, click the Application Elements button, and then select the application elements you want.
To remove a requirement, hover over the requirement, and then click the Remove element button
. Choose whether to:Remove the requirement only from the application element it has been added to.
Remove it from all application elements in the workspace.
Delete it entirely from all workspaces and the repository.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename a requirement, hover over the requirement, and then click the Edit button
.To view or change the description of a requirement, expand it.
After adding requirements to your application elements, select page 3 from the navigation menu at the top to advance to the next page of the template.
Prioritise Requirements
The third page of the Application-Based Roadmap template lets you prioritise the requirements that you defined in the previous step.
Value vs. Effort Method and Eisenhower Matrix
The appearance of the page depends on the prioritisation method chosen during the setup of the workspace:
The Value vs. Effort Method allows your team to prioritise requirements based on their value and the effort required to implement them.
The Eisenhower Matrix allows your team to organise requirements based on their urgency and importance.
The common visual element in both of these prioritisation methods is a 2×2 grid, which divides requirements into four quadrants. The quadrants are labelled to indicate the level of value and effort or importance and urgency required.
Put Requirements into Quadrants
All requirements are listed in the Drag and drop requirements in the matrix column on the left. Requirements that have already been prioritised are greyed-out.
There are two ways to prioritise a requirement:
Drag it to the quadrant you want.
Click the More button
, and
then click Add to <quadrant-name>.
If you need to change the prioritisation, you can also move requirements from one quadrant to another.
Consider performing pairwise comparisons within each quadrant: Adapt the position of different requirements relative to each other to further refine their priority. This helps in determining which requirements within a specific category should be implemented first.
Change Thresholds
The x and y axes represent the thresholds between the quadrants in the chart. To change a threshold:
- Drag the axis to a new position.
The new threshold will be saved to the workspace.
Once you have prioritised the requirements, select page 4 from the navigation menu at the top to advance to the next page of the template.
Plan Requirements
The fourth page of the Application-based Roadmap template allows you to plan requirements for implementation using a Kanban board.
The Kanban board has columns representing quarters in a year, and each requirement is represented by a card. All requirements start in the Drag & drop Requirements to a quarter area on the left and can be dragged to a column to put them on the roadmap.
Get Information
Before deciding when a requirement should be implemented, it's essential to check all the information provided by ADOIT. The Kanban board cards show the prioritisation category (quadrant) and the scores assigned for the two evaluation criteria during prioritisation on the Prioritise Requirements page.
Place Requirements on the Roadmap
Once you have all the necessary information, you can define when a requirement should be implemented. There are two ways to place a requirement on the roadmap:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a quarter under Move to ....
If you need to reassign a requirement, you can simply move it to a different column.
Add or Remove Quarters
You have the flexibility to manage the quarters represented on your roadmap:
To add a quarter, click the Add quarter button
.To remove a quarter, hover over the quarter, and then click the Remove quarter button
.
Be aware that you can only add or remove quarters at the beginning and the end of the roadmap.
Once you have planned your requirements, select page 5 from the navigation menu at the top to advance to the next page of the template.
Track Requirements
On the fifth page of the Application-based Roadmap template, you can track the implementation status of requirements over time using a Kanban board.
The Kanban board consists of columns that represent different statuses, with each requirement displayed as a card. Initially, all requirements appear in the Drag & Drop Requirements to a status area on the left. You can assign a status by dragging a requirement card into the corresponding column. As progress is made, you can update the status by moving the cards between columns.
Get Information
Each card on the Kanban board displays the assigned prioritisation category (quadrant) from the Prioritise Requirements page, as well as the planned implementation quarter from the Plan Requirements page. Check this information before you assign a status to a requirement.
Set the Status of the Requirements
There are two ways to set the status of a requirement:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a status under Move to...
If you need to update the status, you can simply move it to a different column.
The available statuses are: Not started, On-track, Caution, Off-track, and Completed.
Once all statuses are set, select page 6 from the navigation menu to proceed to the final page.
Summary
The last page of the Application-based Roadmap template offers a summary of all the requirements in the workspace. This page has the following areas:
Application elements in total: Displays the total number of application elements in the workspace.
Requirements in total: Shows the total number of requirements in the workspace.
Status per prioritisation: Click Show chart to open a sunburst chart that visually represents how requirements are categorised and their current progress. The inner rings indicate the assigned prioritisation category (quadrant) from the Prioritise Requirements page, while the outer rings show the status from the Track Requirements page. Below the chart, the number of requirements per status is listed. Hover over a slice in the outer ring to see the names of requirements in that specific category and status.
Status per quarter: Click Show Chart to open a bar chart displaying the number of requirements per quarter and status. Hover over a bar to view the names of the requirements that fall within that specific quarter and status.
Table/Kanban Summary: Provides a detailed overview of all application elements and their assigned requirements, including prioritisation category, planned quarter, and current status. You can switch between a table view and a Kanban board using the
Show table and
Show Kanban board icons.What's Next?: Check out possible next steps here. How about creating another workspace, or taking part in a free online training for ADOIT?
Capability-Based Roadmap
The Capability-based Roadmap template is a collaborative tool for planning the requirements associated with your strategy elements.
Which Elements Are Used?
Capability-based Roadmaps start from a set of strategy elements such as
Capabilities and
Courses of Action and then focus
on their Requirements.
How Do Capability-Based Roadmaps Work in ADOIT?
To begin, set up a Capability-based Roadmap workspace (see Create Workspace).
Once the workspace is set up, follow these six steps:
These steps are discussed in more detail in the following sections.
Select Strategy Elements
The first page of the Capability-based Roadmap template lets you add strategy elements to the roadmap.
Select Strategy Elements for Requirements Assignment
To define what strategy elements you want to work with:
From the Element types list at the top left, choose the type of strategy element you want to add to the roadmap. Depending on your workspace settings, you may choose
Capabilities,
Courses of Action,
Business Actors and
Business Functions. If only
one option is available, it will be automatically selected. After choosing, all elements of that
type will be displayed.To add an element, click the
Add button. To remove an element, click the
Remove button. For bulk
actions, you can use the Add all link provided at the top of the page.
Filter by Level or Group
When you choose Capabilities from
the Element types list, you can apply a filter to hone in on the specific elements you need:
- Level: Use this filter to select capabilities from a specific hierarchical level.
All Capabilities will display
their level. It can be set in another ADOIT scenario such as "Design & Document"
by changing the value of the Level property in the chapter "General".
Additionally, the following filter is available for all types of strategy elements:
- Groups: Use this filter to select strategy elements from specific object groups.
You can apply multiple conditions to each filter and combine both filters if required.
Additional Options
The following additional options are available on the first page of the Capability-based Roadmap template:
To find elements, in the Filter... box, type the text you want to search for.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename a strategy element that has been added to the workspace, hover over the element, and then click the Edit button
.
After adding your strategy elements, select page 2 from the navigation menu at the top to advance to the next page of the template.
Define Requirements
On the second page of the Capability-based Roadmap template, you can define requirements for all strategy elements that have been added to the workspace.
The strategy elements are listed along with their associated requirements. Furthermore, for
Capabilities, their hierarchical
level is also visible.
Add Requirements to Strategy Elements
There are two ways to add requirements to a strategy element. Choose one of the following options:
Add Requirement: Click Add Requirement below the element to search for an existing requirement or create a new one.
Start typing the name of a requirement, and then select the one you want when you see it. If the requirement does not yet exist, finish typing the name and press <Enter> to create it.
To see more options, click Show more. This opens a support dialogue with the following tabs:
Assigned requirements: Displays all requirements already assigned to the element.
All existing requirements: Lists all requirements in the repository. You can filter requirements, select the ones you want to assign, and click Add.
AI: Click AI to browse AI-generated requirement suggestions. A list of relevant requirements will be created based on an AI model.
You can filter the results, select the requirements you want to assign, and click Add.
AI-generated suggestions must be enabled by your ADOIT administrator for each repository.
Additional Options
The following additional options are available on the second page of the Capability-based Roadmap template:
To filter requirements, in the Filter Requirements... box, type the text you want to search for.
To filter strategy elements, click the Strategy Elements button, and then select the strategy elements you want.
To remove a requirement, hover over the requirement, and then click the Remove element button
. Choose whether to:Remove the requirement only from the application element it has been added to.
Remove it from all application elements in the workspace.
Delete it entirely from all workspaces and the repository.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename a requirement, hover over the requirement, and then click the Edit button
.To view or change the description of a requirement, expand it.
After adding requirements to your strategy elements, select page 3 from the navigation menu at the top to advance to the next page of the template.
Prioritise Requirements
The third page of the Capability-based Roadmap template lets you prioritise the requirements that you defined in the previous step.
Value vs. Effort Method and Eisenhower Matrix
The appearance of the page depends on the prioritisation method chosen during the setup of the workspace:
The Value vs. Effort Method allows your team to prioritise requirements based on their value and the effort required to implement them.
The Eisenhower Matrix allows your team to organise requirements based on their urgency and importance.
The common visual element in both of these prioritisation methods is a 2×2 grid, which divides requirements into four quadrants. The quadrants are labelled to indicate the level of value and effort or importance and urgency required.
Put Requirements into Quadrants
All requirements are listed in the Drag and drop requirements in the matrix column on the left. Requirements that have already been prioritised are greyed-out.
There are two ways to prioritise a requirement:
Drag it to the quadrant you want.
Click the More button
, and
then click Add to <quadrant-name>.
If you need to change the prioritisation, you can also move requirements from one quadrant to another.
Consider performing pairwise comparisons within each quadrant: Adapt the position of different requirements relative to each other to further refine their priority. This helps in determining which requirements within a specific category should be implemented first.
Change Thresholds
The x and y axes represent the thresholds between the quadrants in the chart. To change a threshold:
- Drag the axis to a new position.
The new threshold will be saved to the workspace.
Once you have prioritised the requirements, select page 4 from the navigation menu at the top to advance to the next page of the template.
Plan Requirements
The fourth page of the Capability-based Roadmap template allows you to plan requirements for implementation using a Kanban board.
The Kanban board has columns representing quarters in a year, and each requirement is represented by a card. All requirements start in the Drag & drop Requirements to a quarter area on the left and can be dragged to a column to put them on the roadmap.
Get Information
Before deciding when a requirement should be implemented, it's essential to check all the information provided by ADOIT. The Kanban board cards show the prioritisation category (quadrant) and the scores assigned for the two evaluation criteria during prioritisation on the Prioritise Requirements page.
Place Requirements on the Roadmap
Once you have all the necessary information, you can define when a requirement should be implemented. There are two ways to place a requirement on the roadmap:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a quarter under Move to ....
If you need to reassign a requirement, you can simply move it to a different column.
Add or Remove Quarters
You have the flexibility to manage the quarters represented on your roadmap:
To add a quarter, click the Add quarter button
.To remove a quarter, hover over the quarter, and then click the Remove quarter button
.
Be aware that you can only add or remove quarters at the beginning and the end of the roadmap.
Once you have planned the requirements, select page 5 from the navigation menu at the top to advance to the next page of the template.
Track Requirements
On the fifth page of the Capability-based Roadmap template, you can track the implementation status of requirements over time using a Kanban board.
The Kanban board consists of columns that represent different statuses, with each requirement displayed as a card. Initially, all requirements appear in the Drag & Drop Requirements to a status area on the left. You can assign a status by dragging a requirement card into the corresponding column. As progress is made, you can update the status by moving the cards between columns.
Get Information
Each card on the Kanban board displays the assigned prioritisation category (quadrant) from the Prioritise Requirements page, as well as the planned implementation quarter from the Plan Requirements page. Check this information before you assign a status to a requirement.
Set the Status of the Requirements
There are two ways to set the status of a requirement:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a status under Move to...
If you need to update the status, you can simply move it to a different column.
The available statuses are: Not started, On-track, Caution, Off-track, and Completed.
Once all statuses are set, select page 6 from the navigation menu to proceed to the final page.
Summary
The last page of the Capability-based Roadmap template offers a summary of all the requirements in the workspace. This page has the following areas:
Strategy elements in total: Displays the total number of strategy elements in the workspace.
Requirements in total: Shows the total number of requirements in the workspace.
Status per prioritisation: Click Show chart to open a sunburst chart that visually represents how requirements are categorised and their current progress. The inner rings indicate the assigned prioritisation category (quadrant) from the Prioritise Requirements page, while the outer rings show the status from the Track Requirements page. Below the chart, the number of requirements per status is listed. Hover over a slice in the outer ring to see the names of requirements in that specific category and status.
Status per quarter: Click Show Chart to open a bar chart displaying the number of requirements per quarter and status. Hover over a bar to view the names of the requirements that fall within that specific quarter and status.
Table/Kanban Summary: Provides a detailed overview of all strategy elements and their assigned requirements, including prioritisation category, planned quarter, and current status. You can switch between a table view and a Kanban board using the
Show table and
Show Kanban board icons.What's Next?: Check out possible next steps here. How about creating another workspace, or taking part in a free online training for ADOIT?
Goal-Based Roadmap
The Goal-based Roadmap template is a collaborative tool for planning the requirements associated with your motivation elements.
Which Elements Are Used?
Goal-based Roadmaps start from a set of
Goals,
Outcomes and
Drivers, and then focus on their
Requirements.
How Do Goal-based Roadmaps Work in ADOIT?
To begin, set up a Goal-based Roadmap workspace (see Create Workspace).
Once the workspace is set up, follow these six steps:
These steps are discussed in more detail in the following sections.
Select Motivation Elements
The first page of the Goal-based Roadmap template lets you add motivation elements to the roadmap.
Select Motivation Elements for Requirements Assignment
To define what motivation elements you want to work with:
From the Element types list at the top left, choose the type of motivation element you want to add to the roadmap. Depending on your workspace settings, you may choose
Goals,
Outcomes and
Drivers. If only one option
is available, it will be automatically selected. After choosing, all elements of that type will
be displayed.To add an element, click the
Add button. To remove an element, click the
Remove button. For bulk
actions, you can use the Add all link provided at the top of the page.
Filter by Group
When you choose motivation elements from the Element types list, you can apply a filter to hone in on the specific elements you need:
- Groups: Use this filter to select strategy elements from specific object groups.
Additional Options
The following additional options are available on the first page of the Goal-based Roadmap template:
To find elements, in the Filter... box, type the text you want to search for.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename a motivation element that has been added to the workspace, hover over the element, and then click the Edit button
.
After adding your motivation elements, select page 2 from the navigation menu at the top to advance to the next page of the template.
Define Requirements
On the second page of the Goal-based Roadmap template, you can define requirements for all motivation elements that have been added to the workspace.
The motivation elements are listed along with their associated requirements.
Add Requirements to Motivation Elements
There are two ways to add requirements to a motivation element. Choose one of the following options:
Add Requirement: Click Add Requirement below the element to search for an existing requirement or create a new one.
Start typing the name of a requirement, and then select the one you want when you see it. If the requirement does not yet exist, finish typing the name and press <Enter> to create it.
To see more options, click Show more. This opens a support dialogue with the following tabs:
Assigned requirements: Displays all requirements already assigned to the element.
All existing requirements: Lists all requirements in the repository. You can filter requirements, select the ones you want to assign, and click Add.
AI: Click AI to browse AI-generated requirement suggestions. A list of relevant requirements will be created based on an AI model.
You can filter the results, select the requirements you want to assign, and click Add.
AI-generated suggestions must be enabled by your ADOIT administrator for each repository.
Additional Options
The following additional options are available on the second page of the Goal-based Roadmap template:
To filter requirements, in the Filter Requirements... box, type the text you want to search for.
To filter motivation elements, click the Motivation Elements button, and then select the motivation elements you want.
To remove a requirement, hover over the requirement, and then click the Remove element button
. Choose whether to:Remove the requirement only from the application element it has been added to.
Remove it from all application elements in the workspace.
Delete it entirely from all workspaces and the repository.
To open the Insights dashboard of an element, hover over the element, and then click the Insights button
.To rename a requirement, hover over the requirement, and then click the Edit button
.To view or change the description of a requirement, expand it.
After adding requirements to your motivation elements, select page 3 from the navigation menu at the top to advance to the next page of the template.
Prioritise Requirements
The third page of the Goal-based Roadmap template lets you prioritise the requirements that you defined in the previous step.
Value vs. Effort Method and Eisenhower Matrix
The appearance of the page depends on the prioritisation method chosen during the setup of the workspace:
The Value vs. Effort Method allows your team to prioritise requirements based on their value and the effort required to implement them.
The Eisenhower Matrix allows your team to organise requirements based on their urgency and importance.
The common visual element in both of these prioritisation methods is a 2×2 grid, which divides requirements into four quadrants. The quadrants are labelled to indicate the level of value and effort or importance and urgency required.
Put Requirements into Quadrants
All requirements are listed in the Drag and drop requirements in the matrix column on the left. Requirements that have already been prioritised are greyed-out.
There are two ways to prioritise a requirement:
Drag it to the quadrant you want.
Click the More button
, and
then click Add to <quadrant-name>.
If you need to change the prioritisation, you can also move requirements from one quadrant to another.
Consider performing pairwise comparisons within each quadrant: Adapt the position of different requirements relative to each other to further refine their priority. This helps in determining which requirements within a specific category should be implemented first.
Change Thresholds
The x and y axes represent the thresholds between the quadrants in the chart. To change a threshold:
- Drag the axis to a new position.
The new threshold will be saved to the workspace.
Once you have prioritised the requirements, select page 4 from the navigation menu at the top to advance to the next page of the template.
Plan Requirements
The fourth page of the Goal-based Roadmap template allows you to plan requirements for implementation using a Kanban board.
The Kanban board has columns representing quarters in a year, and each requirement is represented by a card. All requirements start in the Drag & drop Requirements to a quarter area on the left and can be dragged to a column to put them on the roadmap.
Get Information
Before deciding when a requirement should be implemented, it's essential to check all the information provided by ADOIT. The Kanban board cards show the prioritisation category (quadrant) and the scores assigned for the two evaluation criteria during prioritisation on the Prioritise Requirements page.
Place Requirements on the Roadmap
Once you have all the necessary information, you can define when a requirement should be implemented. There are two ways to place a requirement on the roadmap:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a quarter under Move to ....
If you need to reassign a requirement, you can simply move it to a different column.
Add or Remove Quarters
You have the flexibility to manage the quarters represented on your roadmap:
To add a quarter, click the Add quarter button
.To remove a quarter, hover over the quarter, and then click the Remove quarter button
.
Be aware that you can only add or remove quarters at the beginning and the end of the roadmap.
Once you have planned the requirements, select page 5 from the navigation menu at the top to advance to the next page of the template.
Track Requirements
On the fifth page of the Goal-based Roadmap template, you can track the implementation status of requirements over time using a Kanban board.
The Kanban board consists of columns that represent different statuses, with each requirement displayed as a card. Initially, all requirements appear in the Drag & Drop Requirements to a status area on the left. You can assign a status by dragging a requirement card into the corresponding column. As progress is made, you can update the status by moving the cards between columns.
Get Information
Each card on the Kanban board displays the assigned prioritisation category (quadrant) from the Prioritise Requirements page, as well as the planned implementation quarter from the Plan Requirements page. Check this information before you assign a status to a requirement.
Set the Status of the Requirements
There are two ways to set the status of a requirement:
Drag its card to the desired column on the Kanban board.
Click the More button
, and
then select a status under Move to...
If you need to update the status, you can simply move it to a different column.
The available statuses are: Not started, On-track, Caution, Off-track, and Completed.
Once all statuses are set, select page 6 from the navigation menu to proceed to the final page.
Summary
The last page of the Goal-based Roadmap template offers a summary of all the requirements in the workspace. This page has the following areas:
Motivation elements in total: Displays the total number of motivation elements in the workspace.
Requirements in total: Shows the total number of requirements in the workspace.
Status per prioritisation: Click Show chart to open a sunburst chart that visually represents how requirements are categorised and their current progress. The inner rings indicate the assigned prioritisation category (quadrant) from the Prioritise Requirements page, while the outer rings show the status from the Track Requirements page. Below the chart, the number of requirements per status is listed. Hover over a slice in the outer ring to see the names of requirements in that specific category and status.
Status per quarter: Click Show Chart to open a bar chart displaying the number of requirements per quarter and status. Hover over a bar to view the names of the requirements that fall within that specific quarter and status.
Table/Kanban Summary: Provides a detailed overview of all motivation elements and their assigned requirements, including prioritisation category, planned quarter, and current status. You can switch between a table view and a Kanban board using the
Show table and
Show Kanban board icons.What's Next?: Check out possible next steps here. How about creating another workspace, or taking part in a free online training for ADOIT?
Adjust Workspaces
Workspaces can be renamed, deleted, and more.
Change Workspace Settings
You can change general workspace settings such as the name, assigned users and permissions. Choose one of the following options:
On the Workspaces Page: Click the More button
on the
tile of the workspace, and then click Settings. Select the settings you want, and then click
Save.From the Workspace: Click the Settings button. Select the settings you want, and then click Save.
For more information on the available settings, see Create Workspace.
Delete Workspace
Administrators can delete a workspace. Choose one of the following options:
On the Workspaces Page: Click the More button
on the
tile of the workspace, and then click Delete.From the Workspace: Click the Settings button, and then click Delete workspace.
Search and Filter Workspaces
To help you quickly find a workspace on the Workspaces page, the following options are available:
Filter by Permissions
To filter workspaces by permissions:
- Click All workspaces, and then select the option you want.
You can view all workspaces, filter by creator, or view my workspaces (= all workspaces where you have been added as a member or admin).
Filter by Type
To filter workspaces by type:
- Click All types, and then select the option you want.
You can view all workspaces or just workspaces of a specific type.
Search
To find a workspace:
- In the Filter... box, type the text you want to search for.
All workspaces that contain the search string in their name are shown.