Start with the end in mind...
The big picture below illustrates how real-time synchronization with ALM tools works in piplanning.io. The supported ALM tools are: Jira Software, Rally Software and Microsoft Azure DevOps.
Our BIG picture showcasing the Work Item Sticky Note synchronization on ART Backlog Board and the Team Boards where these work items originate.
ART (Features) or Team (User Stories) Backlog Work Items from these ALM tools can be synchronized (originate) on these two (2x) types of Boards in piplanning.io, respectively:
ART Backlog Board (Program) level
Team Board level
In addition, this is very important, each organizational layer, for example, Team/s > ART/s > Solution Train) are represent as nodes in the piplanning.io Organization hierarchy. It is a prerequisite to configure the Organization hierarchy before preparing any PI Session. Navigate to; RTE Cockpit > Organization menu.
Important: Configuring the Organization nodes (Teams > ARTs > Solution Train) is always the first step to complete before attempting both the ALM Connection and PI Session setup.
piplanning.io Boards as they map to the Organizational hierarchy
Organization | Boards |
Solution Train / Portfolio | Solution Backlog Solution Planning Board |
ART (Agile Release Train) | ART Backlog Board* ART Planning Board ART PI Objectives |
Team | Team Board* |
Table: Organization nodes and corresponding Boards: * indicates which Boards have Work Item type Sticky Notes that synchronize via the ALM Connection
Origin Boards; what you need to know
FYI
Each node in the Organization - Solution Train > Agile Release Train (ART) > Team - has, what we call an origin Board. The origin Board is where the respective ALM Work Items are managed. Even though that synchronized Sticky Note / ALM Work Item originates on a specific board, it can them be mirrored to other boards for transparency and rapid decision making.
The origin Boards hold the Backlog Work Items for the respective organizational node. In practice the origin Boards in a PI event are as follows:
Solution Backlog Board for Solution Trains (ST) - is a container for the ST backlog items such as Capabilities etc.
ART Backlog Board for ARTs - is a container for the ART Backlog of Features, Enablers that you will synchronize to/from the ALM tool etc.
Team Board for Teams - each Team has their own unique Team Board. Team Boards are for User Stories, Enablers, Defects that synchronize to/from the ALM tool etc.
Firewalls/Whitelisting; the IP Range to allow connections with piplanning.io
If your ALM tool is behind a firewall then you need to allow for network traffic from our IPs, which are:
3.66.113.44 (Effective starting early December 2025, subscribe to notifications)
IMPORTANT
Starting early December 2025, the IP Range to allow connections with piplanning.io will be only be 3.66.113.44.
All other previous IP ranges will be phased out at this time.
Please subscribe to the IP Range notifications updates by clicking the button below, or check back here in December, 2025
Make sure that you allow outgoing traffic to our WebHook Endpoint for real-time updates, reachable under:
194.182.188.230
To be notified of any changes regarding this list, please subscribe to our IP Range mailing list by clicking the button below.