Managing Collectors

April 29, 2017

Introduction

Managing collectors helps an organization track, organize and govern the various teams in a manner that is relevant to the organization’s unique context. Because organizational designs evolve over time, you don’t have to have your organizational structure figured out up front – you can make changes to your structure along the way as it makes sense.

The main benefit of managing your collectors is that it helps you perform insightful and unique analyses once the data is collected.

Prerequisites

Before you can perform any of the tasks below, you will need to open up a Comparative Agility account.

 

Step 1 — Create Collectors

When you first start out creating Collectors, you probably have not figured out exactly how you want to setup your structure yet. That's OK; you can change this along the way. Step 1

For now, let's just start by creating some Collectors:
Team 1
Team 2
Team 3

As you can see, these collectors reside on the same level.


Step 2 — Adding Parent and Child collectors

As you add more teams and organize your collectors in a matter that reflects how your company operates, you may want to avoid placing all collectors on the same level, as this can be challenging to manage. Step 2

Let's say your organization has a Program dedicated to delivering a given value stream and a separate DevOps group.
Using the same structure defined in Step 1, we can now:

- Add a Parent collector called Program to Team 3
- Rename Team 2 to DevOps Group
- Add a Child collector to DevOps Group named Team 4

Note: Note: When gathering data, you only send out Collectors at the Team level. Parents therefore do not have individual survey Collector links, but contain the aggregated data from their children.


Step 3 — Using Drag & Drop to manage collectors

Let's say that the organization finds that it makes more sense for each Program to have their own dedicated DevOps unit. In other words, the DevOps Group is no longer at the same level as the Program, it is now a child of the Program.

Step 3 Making this change is easy. Here, we’ll completely rearrange the current structure to reflect this latest organizational change.

- Move the DevOps Group collector under Program collector
- Move Team 3 collector under Program collector
As you can see, the Program is now at the highest level, with two teams (Team 1 and Team 3) under it, as well as the DevOps Group and its associated teams.

Note: There is no limit to the structural changes you can make. You can even add a Parent to the Program collector (Organization, for instance) which then can have multiple children representing the various Programs in the organization.


Where to Go From Here

The next step is performing analysis.