Login

Not Registered?

Scaled Professional Scrum with Nexus Practices

Scrum is a framework from which process evolves. A Scrum Team or organization will build their process by assembling the proper practices that they feel will help them succeed with Scrum at the heart.

Nexus extends Scrum to guide multiple Scrum Teams on how they need to work together to deliver working software in every Sprint. It shows the journey these teams take as they come together, how they share work between teams, and how they manage and minimize dependencies. In the Scaled Professional Scrum with Nexus course, students learn about many of the practices available to help their teams better scale. The intent of the below chart is to help readers understand those practices and find ways to learn more.

A development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build and test process, allowing teams to detect problems early.

To discover coding and code integration problems as early as possible, while the code is still fresh in the developer's mind.

Techniques for synchronizing the work of multiple Development Teams in a Nexus when their Sprint lengths differ.

To handle the situation in which not all teams in the Nexus cannot get PBIs to "done" at the same rate. Especially relevant in mixed hardware/software products, and products that require some work to be done on legacy code.