Nexus es un marco de trabajo para el desarrollar y mantener iniciativas de construcción de productos y programas a escala. Nexus utiliza Scrum como bloque de construcción. Nexus aumenta Scrum proponiendo algunos cambios en eventos, roles y artefactos.
Nexus es una unidad representada por un único Product Owner y un único Product Backlog, con la participación de 3 a 9 equipos Scrum (de 10 a 100 personas), que trabajan de forma cíclica para la obtención de incrementos integrados. Cada equipo Nexus está dirigido por un NIT (Nexus Integration Team). Los equipos Scrum de Nexus siguen las mismas normas establecidas en la guía Scrum.
Te animo a revisar el manual de Nexus (en catalán) disponible en esta web. Al final de este artículo también encontrarás un enlace para descargarte el PDF de la guía. También te recomiendo la lectura de la Nexus Guide de Scrum.org
La mecánica del examen es muy sencilla. Consiste en responder 40 preguntas tipo test en 60 minutos. Con un 85% de aciertos quedas automáticamente certificado, y podrás descargarte el certificado y el correspondiente logotipo para incluirlo en tu CV.
Las preguntas pueden ser del tipo true/false, selección única o selección múltiple. La principal dificultad radica en el hecho que el examen es íntegramente en inglés. Aunque las pruebas previas (open assessments) que Scrum.org pone a disposición, puedes copiar y pegar texto en el traductor. No puedes confiar en esta función a la hora de hacer el examen oficial, ya que Scrum.org acostumbra a bloquear algunas funciones del navegador.
El precio de la certificación son 250$ y el examen es online. Una vez compras el derecho a examen, tienes una oportunidad que puedes ejercer cuándo quieras (el token no caduca).
Para prepararse el examen, lo ideal es leer a fondo la Guía Nexus, i complementar esta lectura con un repaso de la Scrum Guide. Además, puedes encontrar fácilmente algunas webs con información sobre el examen, y preguntas reales para poder practicar.
Scrum.org también facilita un pequeño examen gratuito de 10 preguntas para poner a prueba tus conocimientos antes del examen real. Es conveniente haber hecho examenes gratuitos de diversas fuentes y tener un alto porcentaje de aciertos antes de enfrentarse al examen real. También es buena idea practicar los open assessments de Scrum Master y Product Owner, ya que Nexus parte de la base de Scrum, y muchas cuestiones se pueden resolver desde esta perspectiva.
Puedes tener abierto el traductor (por ejemplo google translate). Aunque te recuerdo que no confíes en “copiar y pegar” texto directamente, ya que, probablemente, deberás teclear los enunciados manualmente.
Puedes tener abierta la Guía Nexus y la Guía de Scrum para aclarar alguna pequeña duda. Pero no pierdas mucho tiempo. Si una pregunta te resulta difícil, puedes pasar a la siguiente, y regresar a esta al final. El tiempo de examen, con un conocimiento medio de inglés no debería ser un problema. Si te sobra tiempo, revisa las preguntas que has encontrado más difíciles. Puedes cambiar cualquier respuesta mientras dura el examen.
Mucha suerte!!!
Nexus Guide, (https://www.scrum.org/resources/nexus-guide) Página oficial de descarga multiidioma, marzo 2023
Scrum Guide, (https://scrumguides.org/download.html) Página oficial de descarga multiidioma, marzo 2023
Escalar Scrum con Nexus, (https://youssefoufaska.com/escalar-scrum-con-nexus/) youssefoufaska.com, marz 2021
Las 10 claves del escalado de Scrum con Nexus, (https://www.youtube.com/watch?v=PFXXfBWtbAw) Paradigma digital, julio 2018
Scrum.org. Open assessments, (https://www.scrum.org/open-assessments) Scrum.org, marzo 2023
Scaled Professional Scrum Sample Questions, (https://www.processexam.com/scrum-org/scrum-org-sps-certification-exam-sample-questions) processexam, marzo 2023
SPS Preparation Quiz, (https://mlapshin.com/index.php/scrum-quizzes/scaled-scrum-quiz/) Mikhail Lapshin, 2018
SPS Practice Exam, (https://www.techagilist.com/practice-exams/sps-practice-test/sps-practice-exam-practice-mode-questions/) Tech Agilist, marzo 2023
Estas preguntas de ejemplo se pueden encontrar en diversos repositorios y artículos sobre el tema. Aquí únicamente se hace una traslación de algunas de estas preguntas, sin poder asegurar su validez.
1. When is the Definition of “Done” reviewed? (choose the best option)
2. A six-team Nexus is developing a full-featured e-commerce application. There are different parts of the application that only certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside the Nexus that are required for some of the work. In past Sprints the Nexus encountered challenges dealing with the many dependencies between Scrum Teams. Some individual Scrum Teams in this Nexus have said that they do not see how the work they are doing is contributing to the product’s progress. What is the best remedy for this situation? (Choose the best option)
3. In the first part of Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams identify many dependencies. This makes it hard for them to choose the work they could pull into their individual teams for the next Sprint. No matter how they reorganize the Product Backlog items, they continually find more or new dependencies. There are especially two teams that have a lot of dependent work. What techniques could help this Nexus manage its dependencies effectively? (choose all the options that apply)
4. How will the Nexus evolve its definition of “Done” over time? (choose the best option)
5. Sam is a developer within a scrum team. Sam believes that the top item in the product backlog is not very clear. He asks the other Developers if they understand it. They have expressed to Sam that it does seem unclear and they are not able to help. What should Sam do? (choose the best option)
6. A team is working on cutting-edge technology and does not have a lot of familiarity with the technical environment. As a result, it is struggling to estimate a complex story because the approach itself is not clear. How should the team proceed? (choose the best option)
7. True or False, Resources with specialized knowledge should be distributed across the different Scrum Teams to ensure that all the teams have the knowledge they need to do their work?
8. Representatives of Scrum Team A and Scrum Team B are participating in Sprint Planning. Each Team has 8 Developers. These Teams have quite a few dependencies on each other in Sprint 1. Which techniques will help with reducing these dependencies? (choose all the options that apply)
9. Many dependencies exist when multiple teams collaborate to create a complete and ‘Done” Integrated Increment. These dependencies are related to (choose all the options that apply)
10. How does Nexus relate to Scrum?
1. When is the Definition of “Done” reviewed? (choose the best option)
Explanation: The Nexus Integration Team will discuss the Definition of “Done’ during the Nexus Sprint Retrospective and let the individual Scrum Teams adapt to it. The changed definition of” Done” might not be implemented right away
2. A six-team Nexus is developing a full-featured e-commerce application. There are different parts of the application that only certain Scrum Teams can work on. In fact, there are some highly specialized individuals outside the Nexus that are required for some of the work. In past Sprints the Nexus encountered challenges dealing with the many dependencies between Scrum Teams. Some individual Scrum Teams in this Nexus have said that they do not see how the work they are doing is contributing to the product’s progress. What is the best remedy for this situation? (Choose the best option)
Explanation: The Nexus Sprint planning is used to highlight dependencies and the flow of work during the Sprint. It focuses on the coordination between teams to ensure the Nexus Sprint Goal is achieved.
3. In the first part of Nexus Sprint Planning, representatives from each of the 9-member Scrum Teams identify many dependencies. This makes it hard for them to choose the work they could pull into their individual teams for the next Sprint. No matter how they reorganize the Product Backlog items, they continually find more or new dependencies. There are especially two teams that have a lot of dependent work. What techniques could help this Nexus manage its dependencies effectively? (choose all the options that apply)
Explanation: Refinement of the Product Backlog at scale serves a dual purpose. It helps the Scrum Teams forecast which team will deliver which Product Backlog items, and it identifies dependencies across those teams. This transparency allows the teams to monitor and minimize dependencies. Domain knowledge: The people on the teams have knowledge of various business and computer systems. Their knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work, to minimize interruptions between Scrum Teams during a Sprint.
4. How will the Nexus evolve its definition of “Done” over time? (choose the best option)
Explanation: During the Nexus Sprint Retrospective, the Definition of “Done” can be revised If needed. 2. These changes would be then communicated to the Individual teams to be incorporated. 3. Once Adapted by the Individual Scrum Team, they would implemented/applied to the Product Backlog items in each Sprint.
5. Sam is a developer within a scrum team. Sam believes that the top item in the product backlog is not very clear. He asks the other Developers if they understand it. They have expressed to Sam that it does seem unclear and they are not able to help. What should Sam do? (choose the best option)
Explanation: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is also accountable for effective Product Backlog management, which includes:
Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible, and understood.
So Sam should discuss his concerns with the product owner; if the product owner is unable to clarify then the item should not be chosen for the current sprint until the item can be clarified
6. A team is working on cutting-edge technology and does not have a lot of familiarity with the technical environment. As a result, it is struggling to estimate a complex story because the approach itself is not clear. How should the team proceed? (choose the best option)
Explanation: The best way to remove the uncertainty of a technical nature is to perform experimentation – which is the intent of a SPIKE story. When a story cannot be estimated because the team needs to experiment, the best approach is to write a spike story before working on the main story.
7. True or False, Resources with specialized knowledge should be distributed across the different Scrum Teams to ensure that all the teams have the knowledge they need to do their work?
Explanation: Team members’ knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work This would minimize Interruptions between Scrum Teams during a Sprint.
8. Representatives of Scrum Team A and Scrum Team B are participating in Sprint Planning. Each Team has 8 Developers. These Teams have quite a few dependencies on each other in Sprint 1. Which techniques will help with reducing these dependencies? (choose all the options that apply)
Explanation: Remember the following with respect to dependencies: The scope of the requirements may overlap, and the order in which they are implemented may also affect each other. While ordering the Product Backlog and selecting the Product Backlog items in the Sprint Backlog, one should make sure that such dependencies are accommodated. Team Members’ knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work. This would minimize interruptions between Scrum Teams during a Sprint. Extending the Sprint Length is not an option under any situation. Merging the Team is not possible as well as both the team has 9 members.
9. Many dependencies exist when multiple teams collaborate to create a complete and ‘Done” Integrated Increment. These dependencies are related to (choose all the options that apply)
Explanation: Many dependencies exist when multiple teams collaborate to create a complete and “Done Increment. These dependencies are related to Requirements: The scope of the requirements may overlap, and the order in which they are implemented may also affect each other. While ordering the Product Backlog and selecting the Product Backlog items in the Sprint Backlog, one should make sure that such dependencies are accommodated. Domain Knowledge: Team members’ knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work. This would minimize interruptions between Scrum Teams during a Sprint. Software and Test Artifacts: The requirements are, or will be, instantiated in software.
10. How does Nexus relate to Scrum?
Explanation: Nexus is a framework for developing and sustaining scaled product and software development initiatives. It uses Scrum as its building block.
Descarga el documento per imprimir aquí
