Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Scaling Scrum Across Modern Enterprises

You're reading from   Scaling Scrum Across Modern Enterprises Implement Scrum and Lean-Agile techniques across complex products, portfolios, and programs in large organizations

Arrow left icon
Product type Paperback
Published in Aug 2020
Publisher Packt
ISBN-13 9781839216473
Length 618 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Cecil 'Gary' Rupp Cecil 'Gary' Rupp
Author Profile Icon Cecil 'Gary' Rupp
Cecil 'Gary' Rupp
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Section 1: Scaling Lightweight Scrum into a Heavyweight Contender
2. Chapter 1: TheOrigins of Agile and Lightweight Methodologies FREE CHAPTER 3. Chapter 2: Scrum Beyond Basics 4. Chapter 3: The Scrum Approach 5. Chapter 4: Systems Thinking 6. Chapter 5: Lean Thinking 7. Chapter 6: Lean Practices in Software Development 8. Section 2: Comparative Review of Industry Scaled Agile Approaches
9. Chapter 7: Scrum of Scrums 10. Chapter 8: Scrum@Scale 11. Chapter 9: The Nexus Framework 12. Chapter 10: Large-Scale Scrum (LeSS) 13. Chapter 11: Disciplined Agile 14. Chapter 12: Essential Scaled Agile Framework® (SAFe®) 15. Chapter 13: Full Scaled Agile Framework® (SAFe®) 16. Section 3: Implementation Strategies
17. Chapter 14: Contrasting Scrum/Lean-Agile Scaling Approaches 18. Assessments 19. Other Books You May Enjoy

Learning the basics of Nexus

In this section, you will learn how the Nexus Framework extends the original Scrum Framework to support multiple Scrum Teams that are working in collaboration to build large, complex, and integrated products. Will start with an introduction to the NIT.

Defining a Nexus

A Nexus consists of a Nexus Integration Team (NIT) and approximately three to nine Scrum Teams. If Nexus is needed, then there is one product and one product Increment. Each individual team within a Nexus does not produce their own product Increment. Since the Nexus is a collaborative development effort, the individual increments must be integrated and tested as a whole to ensure accomplishment of the Nexus goal.

The NIT is responsible for completing an Integrated Increment that meets the definition of "Done" within each Sprint. In that role, the NIT must help the team assess and eliminate impediments and cross-team dependencies that would complicate their work and reduce...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image