Network layer
The Network layer lets several organisations improve a shared platform together. It plans shared capabilities on a 12-week Pulse Cycle while each organisation keeps its own backlog and sprints.
Used in NetworkPortfolio of Networks
When you need it
Switch it on when two or more organisations share a platform, a supplier or a roadmap, such as a network of organisations.
What this layer decides
- Which shared capabilities are built this cycle, and for which organisations
- Cycle objectives for each organisation
- Which delivered solutions are offered for reuse
- Standards: configuration, integration, Jira and reporting
- Which supplier releases the network depends on
Network Kanban
Capabilities shared across organisations. A capability connects work of any type, from any organisation or product, so a solution is built once and used by all of them. Epics never sit here: they belong to each organisation’s Portfolio Kanban.
FunnelReviewAnalysingReadyImplementingValidatingDone
Levers used here
The rest of this page is for subscribers
Subscribe to read the other 7 sections of this page:
- Roles
- Events
- Artifacts
- Inputs and outputs
- How it connects
- If you use Jira or Azure DevOps
- Getting started