The circle map is for organizations who wish to have more than one scrum team, where each team has their separate Product Backlog.
You can have one or more Primary Circles, each with their own Product Backlog. Other types of circles (Customer Circles, Supplier Circles etc.) also have their separate Product Backlog.
Delegation of User Stories between Circles
If you add a relation from e.g. a Customer Circle to a Primary Circle (called “Development” in the illustration), it means that the team in the Customer Circle can delegate user stories from their Product Backlog to the Primary Circle for implementation.
Please see Delegate to another circle for more details about delegation.
Circle Manifest and Traffic Light
Each circle should have a Manifest describing the purpose and scope or the circle. If you place the cursor over a circle, a popover will show the manifest.
If there are some problems in the circle, you want to draw attention to, you can change the traffic light of the circle to yellow or red. Write a traffic light comment to describe the problems. The traffic lights are shown at the right side of the circle cards.
Teams in Circles (Read More)
A circle has one Product Backlog and usually one team to handle the backlog contents. However, you also have the option of dividing users in to multiple teams within the circle.
How to create a Circle and Relation in the Circle Map?
To add a new circle, right click on the circle map and select the circle type in the context menu. The new circle added will also be available in the circle selection in the Main Menu (Read More).
To create a relation between two circles, hold down the “Alt” key while you drag the relation from one circle to another.