fbpx

Visualize Team Relationships with the Dependency Wheel

Agile teams are meant to be self managing and independent. But as the size of an organization grows or the scope of the product being developed becomes complex, many teams have to work together. Thus dependencies can start existing between these different agile teams. These dependencies can become a serious problem if they are not recognized, identified and acknowledged. Correctly mapping them and having real transparency becomes all the more important.

Kendis now introduces a more aesthetically pleasing and extremely useful view into tracking your dependencies. We introduce to you, the Dependency Wheel.
In this article, we will talk about the features and the power of the Dependency Wheel. We will give you a walkthrough into how the Dependency wheel can be used.

What is the Dependency Wheel?

Dependency Wheel

Visually pleasing and extremely powerful, the dependency wheel summarizes all the dependencies that you have created among teams on the Kendis board into one dynamic solution.

The names of the teams are listed on the boundary of the wheel diagram. The teams are differentiated with the colors that you have set while creating the teams. All these teams on the wheel are clickable.

There is a mesh of lines that represent the dependencies. These lines are outgoing from a team or incoming to them.

The width of each line is directly proportional to the number of dependency lines which means that the greater the number of dependencies, the thicker the line on the dependency wheel will be.

What Does Hovering On The Line Show?

Whenever you hover on to a line, it will show the source and target of where the dependency line is being made along with the total number of dependencies it has.

Dependency Wheel Hovering On The Line Show

How Do You Know The Total Number Of Dependencies?

Total Number Of Dependencies

Once you hover on any team, a tooltip will appear that will show the total number of dependencies that exist for your selected team with other teams. When viewing the dependencies for your team, only the lines that exist for that team will be highlighted while the rest of the lines would become opaque.

How Do You Know If a Dependency is Outbound or Inbound?

When you hover over a team and you see the same colored lines emanating from your selected team to other teams, those are considered outbound dependencies from your selected team.
Inbound dependencies are any different colored lines from other teams that are joining into your selected team.

Using Filters

The filters for this dependency wheel will allow you to know exactly where a dependency is being created. Choose from 4 types of filters:

  • 1. Select Team: Choose one or more teams from the drop down to view their dependencies.
  • 2. Select Sprint: Choose one or more sprints from the drop down to view their dependencies
  • 3. Feature Relationship: This drop down will allow you to select the dependencies between:
    • a. Feature to Feature: Dependencies between parent to parent items
    • b. Feature to Story: Dependencies between parent to child items
    • c. Story to Feature: Dependencies between child to parent items
    • d. Story to Story: Dependencies between child to child items
  • 4. Status: This drop down will allow you to select Open or Resolved Dependencies.

Export

The dependency wheel can be exported in order to be shared with anyone within or out of the organization. This can be done in one of the four file formats which are jpeg, png, svg or pdf.

Finally…

One of the main purposes for introducing the dependency wheel is to identify teams that have strong correlation between them. Teams may already be structured by components, geography, or even historical reasons. However, if they need to be strongly dependent on other teams in order to bring true value, it may be worth exploring or reexamining the makeup of your current teams. After all, the less handoffs and dependencies between teams, the better!

About Kendis

Kendis is a leading solution for Distributed PI Planning. It is a new way to plan and manage your dependencies, risks, and objectives. Get actionable insights into your program increment’s progress and scope changes.
Try out 10 days free trial or book a demo with our product expert.


Kendis is a digital solution for PI, Tribe, and Big room Planning that works on top of Jira and Azure Boards.

...

Leave a Reply

Your email address will not be published.

Explore Articles about Scaling Agile

Pick your next read from our vast library of specialized content. These Kendis articles help the Agile transformation leaders develop a deeper understanding and provide fact-based insights that contribute to decision making on critical scaling issues.


Got Questions?

Talk to our product expert to understand how Kendis can help your organization in your scaling agile journey.
Contact us now Get a personalized demo for free.



Play

Watch Video
Program reports and analytics

Program reports and analytics

Collaborate for the completion of a Release Train with a wholesome overview of all activities on your Program Board summarized into graphical and tabular formats.

Dependencies Management

Dependencies Management

Summarize all your PI dependencies into one meaningful and simple dynamic solution that automates dependency status updates throughout the PI according to the triggers you select.

Risk Register Tracking

Risk Register Tracking

Address and visualise the present and upcoming risks of your Program Increment, sprint or iteration to swiftly identify and smoothly mitigate them.

Feature Tracking

Feature Tracking

Visualise features progress, development, addition and removal, across sprints and teams in a simple and easy manner.

Scope Change Tracking

Scope Change Tracking

Track your PI’s scope and other changes post-planning, saving yourself hours of manual work and eliminating the possibility of human error.

Collaboration, communication and transparency lie at the heart of Kendis. It brilliantly reduces all the painful efforts and makes the entire process of planning your Program Increment a very easy task.
PI Objectives Tracking
Play

Watch Video

Dependencies are essential in recognizing, identifying and correctly mapping factors that are affecting your progress. In Kendis you can create multiple dependencies across your Program board and track them.
Dependencies Management
Play

Watch Video

With Kendis you can transparently address and visualize the present and upcoming risks of your Program Increment, sprint or iteration in a way that makes it painless to identify and analyze.
Risk Register Tracking
Play

Watch Video

Create objectives for each team or for your Program and link those with any item present your board. This allows you to choose precisely what features and stories are contributing to the objective.
Feature Tracking
Play

Watch Video

An extremely vital and powerful feature that gives an overview of all the recent activities that are being done. Presented in graphical or tabulated formats, you obtain all the necessary information in just a glance.
Scope Change Tracking
Play

Watch Video