{"id":564,"date":"2017-11-22T12:48:03","date_gmt":"2017-11-22T11:48:03","guid":{"rendered":"http:\/\/agilerasmus.com\/wordpress\/?p=564"},"modified":"2017-11-23T05:51:29","modified_gmt":"2017-11-23T04:51:29","slug":"handling-dependencies-with-nexus","status":"publish","type":"post","link":"https:\/\/agilerasmus.com\/wordpress\/handling-dependencies-with-nexus\/","title":{"rendered":"Nexus exoskeleton"},"content":{"rendered":"

One of the trending buzz-words within agile software development is \u201cscaling\u201d. This has been discovered by the gurus within agile processes and we currently see heaps of frameworks popping up. Each of these frameworks pose a solution to scaling work across several teams. But what does scaling actually mean and how can we use a framework like Nexus to handle dependencies?<\/p>\n

A key effect from agile transformations is that organizations start focusing on having stable teams that are high performing and works off an independent backlog. They strive to do Scrum \u201cby the book\u201d to take a step into being more agile.<\/p>\n

This effect is vital, and we should work on persisting it even en scenarios with multiple teams working together to deliver working software. As such it is crucial to find a framework that does not introduce to much overhead and administration. The feasible price for the overhead is very much depending on context. The larger you scale, the more overhead is accepted. However, as you add overhead you also potentially reduce the empowerment of each individual Scrum team and thus break with the original idea of Scrum.<\/p>\n

Nexus exoskeleton<\/strong><\/p>\n

Looking into frameworks for scaling agile \u2013 we stumble upon Nexus as one of the up and coming solutions for handling cross team dependencies. The word \u201cnexus\u201d originates from latin and means \u201cthe action of binding\u201d. The Nexus exoskeleton for scaled Scum consists of a set of roles, events and artefacts that comes in play when 3-9 teams work together on the same backlog to deliver software striving for a joint goal.<\/p>\n

<\/p>\n

Nexus is in many ways similar to Scrum; it\u2019s easy to learn but hard to master.<\/p>\n

Roles<\/strong><\/p>\n

The roles in a Nexus is organized in a so-called Nexus Integration Team. The team is responsible for ensuring that the outcome of the teams is an increment of integrated potential releasable software. Each role has its own responsibility:<\/p>\n