Getting into the details
The Nexus Guide is a quick introduction to the basics of the Nexus Framework. Ken Schwaber and the folks at Scrum.org make the point that, like Scrum, Nexus is simple to understand, yet difficult to master. The remainder of this chapter provides an overview of the implementation details that must be mastered.
Building products, not running projects
As with most Agile-based approaches to development, Scrum and Nexus place the focus on building products, not running projects. There are multiple reasons for this, but the primary issue is one of staying focused on doing the things that add value.
Projects are relatively short-lived development efforts, having a set duration with a defined beginning and an end, and living within the constraints of scope, budgets, schedule, resources, and quality. The outcome of a project is a product, service, or outcome. Once the project ends, all activity stops unless a new project is chartered and initiated.