Nexus - Scaled Scrum

Based on Nexus Guide and the book The Nexus Framework for Scaling Scrum. Flashcards will be updated gradually.

33 flashcards · Other · by claudehsu

1. What does NIT stand for? Answer: Nexus Integration Team

   NIT is accoutable for ensuring that a done integrated increment is produced at least once a sprint.

2. A Nexus is a group of approximately 3 to 9 Scrum Teams that work together to deliver a single prodct. Fill in the blanks with proper numbers

   Note Nexus has a single Product Owner, who manages a single Product Backlog from which the Scrum Teams work.

3. Nexus seeks to preserve and enhance Scrum's foundation bottom-up intelligence and empiricism while enabling a group of Scrum Teams to deliver more value than can be achieved by a single team.

   Hints: The intelligence is not from managers or by a central authority and then handed down to the teams. Instead it is from individuals or to say giving the teams the power to make decisions. One of the theory supporting Scrum

4. The goal of Nexus is to scale the value that a group of Scrum teams, working on a single product is able to deliver. It does this by reducing the complexity. Common scaling challenges are cross-team dependencies preserving team self-management and transparency ensuring accountability

   Hint: The last blank is one of the pillars of Scrum.

5. Draw the bird's eye view of Nexus

6. The NIT consists of a Product Owner a Scrum Master Nexus Integration Team Members

   Fill in the 3 roles.

7. A Nexus Sprint Goal is the object for the Sprint.

   Hint: the reason why you have the sprint. Usually it's formed after you picking up the stories/tasks.

8. Scrum framework defines three specific sets of accountabilities Developers Product Owner Scrum Master

   Hint: In version 2020, name of one of the three roles gets changed

9. Who is accountable for ensuring that a done Integrated Increment?

   The Nexus Integration Team

10. What is bottom-up intelligence?

    Some key aspects of bottom-up intelligence in Nexus include: Beginning with basic agents that can perceive, learn, and make simple decisions. Then combining agents to create collective behaviors and more advanced capabilities. Leveraging emergent properties Applying evolutionary principles Decentralizing control Integrating bottom-up (emergent) and top-down (designed) approaches. Using top-down design for overall system architecture, while focusing on bottom-up methods for subcomponents.

11. In NIT, what does Product Owner accountable for?

    The Product Owner is accountable for maximizing the value of the product and work performed and integrated by the Scrum Teams in a Nexus.

12. In NIT, what does Scrum Master accountable for?

    The Scrum Master is accoutable for ensuring the Nexus framework is understood and enacted as described in the Nexus Guide.

13. May composition of the NIT change over time? a.) Yes, it can be changed to reflect the current needs of a Nexus. b.) No, it is fixed at the very beginning. Anwer: a

14. What are common activities the NIT might perform? coaching consulting highlighting awareness of dependencies and cross-team issues

15. If someone's 'Scrum' tasks are conflicted with her/his 'NIT' tasks, what should s/he do?

    Membership in the Nexus Integration Team takes precedence over individual Scrum Team membership.

16. Nexus events consist of Sprint Cross-Team Refinement Nexus Sprint Planning Nexus Sprint Review Nexus Sprint Retrospective

    Keep in mind that the 4th event on the list replaces the individual ones(since we have multiple Scrum teams) in Scrum.

17. Attendee of each event

    Nexus events are attended by whichever members of the Nexus are needed to achieve the intended outcome of the event most effectively. Deduction: only for Nexus Sprint Review, all Nexus Team members need to attend(think it as an aggregation of individual Scrum Sprint Reviews)

18. To what level should the decomposition of a Product Backlog item be?

    To actionable work that a single Scrum Team could deliver inside a Sprint.

19. What are the two main purpose of Cross-Team Refinement?

    It helps the Scrum Teams forecast which team will deliver which Product Backlog items. It identifies dependencies across those teams.

20. How to understand the Nexus Sprint Goal?

    It aligns with the Product Goal and describes the purpose that will be achieved by the Nexus during the Sprint Sprint Goal for each Scrum Team aligns with the Nexus Sprint Goal.

21. Purpose of the Nexus Daily Scrum identify the integration issues inspect progress toward the Nexus Sprint Goal

    For the second bullet, use Capital case

22. Is Nexus Daily Scrum the only time Scrum Teams are allowed to adjust their plan?

    No, cross-team communication can occur throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint's work.

23. Which one should be hold first? Nexus Daily Scrum or Daily Scrum of individual teams?

    Nexus Daily Scrum goes first to inspect the current state of the integrated Increment, and identify integration issues. Then each Scrum Team's Daily Scrum complements the Nexus Daily Scrum by creating plans for the day, focused primarily on addressing the integration issues raised during the Nexus Daily Scrum. In Scrum of Scrums, individual Daily Scrums go first.

24. What's the purpose of Nexus Sprint Review?

    To get feedback on the Integrated Increment. The Product Backlog may be adjusted to reflect these discussions.

25. The purpose of the Nexus Sprint Retrospective is to plan ways to increase quality and effectiveness across the whole Nexus.

    The Nexus inspects how the last Sprint went with regards to individuals, teams, interactions, processes, tools, and its Definition of Done. Scrum Teams' Sprint Retrospectives complement the Nexus Sprint Retrospective by using bottom-up intelligence to focus on issues that affect the Nexus as a whole.

26. The Nexus Integration Team works with the Scrum Teams within a Nexus to ensure that transparency is achieved across all artifacts. The three artifacts are Product Backlog Nexus Sprint Backlog Integrated Increment

    All in Capital case.

27. Who is accountable for the Product Backlog?

    The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering.

28. What's the commitment of Product Backlog? Answer: Product Goal

    The answer describes the future state of the product and serves as a long-term goal of the Nexus. Answer in Capital case

29. A Nexus Sprint Backlog is composite of ?

    Nexus Sprint Goal Product Backlog items from the Sprint Backlogs of the individual Scrum Teams. It is used to highlight dependencies and the flow of work during the Sprint, so only items have cross-team dependencies are displayed on Nexus Sprint Backlog.

30. What is the comment of Nexus Sprint Backlog? Answer: Nexus Sprint Goal

    All in Capital case.

31. The Integrated Increment must meet the Definition of Done, and it is inspected at the Nexus Sprint Review

    All in Capital case. Note it may be delivered to stakeholders before the end of the Sprint.

32. What is the commitment for the Integrated Increment?

    Definition of Done, which defines the state of the integrated work when it meets the quality and measures required for the product.

33. Who is responsible for a Definition of Done that can be applied to the Integrated Increment?

    The Nexus Integration Team. Note Individual Scrum Teams self-manage to achieve this state. They may choose to apply a more stringent DoD within their own teams, but cannot apply less rigorous criteria than agreed for the Integrated Increment.