Nexus és un marc per desenvolupar i mantenir iniciatives de construcció de productes i programes a escala. Nexus utilitza Scrum com a bloc de construcció. Nexus augmenta Scrum proposant alguns canvis en esdeveniments, rols i artefactes.
Nexus és una unitat representada per un únic Product Owner i un únic Product Backlog, amb la participació de 3 a 9 equips Scrum (de 10 a 100 persones), que treballen de forma cíclica per l’obtenció d’increments integrats. Cada equip Nexus està dirigit per un NIT (Nexus Integration Team). Els equips Scrum de Nexus segueixen les mateixes normes establertes a la guia Scrum.
T’animo a revisar el manual de Nexus en català disponible en aquesta web. Al final d’aquest article també trrobaràs un enllaç per descarregar-te el PDF de la guia. També et recomano la lectura de la Nexus Guide de Scrum.org
La mecànica de l’examen és molt senzilla. Consisteix a respondre 40 preguntes tipus test en 60 minuts. Amb un 85% d’encerts com a mínim quedes automàticament aprovat, i podràs descarregar-te el certificat i el corresponent logotip per incloure’l al teu CV.
Les preguntes poden ser del tipus true/false, selecció única o selecció múltiple. La principal dificultat radica en el fet que l’examen és íntegrament en anglès. Tot i que les proves prèvies (open assessments) que Scrum.org posa a disposició pots copiar i enganxar text al traductor. No pots confiar en aquesta funció a l’hora de fer l’examen oficial, ja que Scrum.org acostuma a bloquejar algunes funcions del navegador.
El preu de la certificació són 250$ i l’examen és online. Un cop compres el dret a examen, tens una oportunitat que pots exercir quan vulguis (el token no caduca).
Per preparar-se l’examen, l’ideal és llegir-se a fons la Guia Nexus, i complementar aquesta lectura amb un repàs de la Scrum Guide. A més, pots trobar facilment algunes wwebs amb informació sobre l’exàmen, i preguntes reals per poder practicar.
Scrum.org també facilita un petit examen gratuït de 10 preguntes per posar a prova els teus coneixements abans de l’examen real. És convenient haver fet examens gratuïts de diverses fonts i tenir un alt percentatge d’encerts abans d’enfrontar-se a l’examen real. També és bona idea practicar els open assessments de Scrum Master i Product Owner, ja que Nexus parteix de la base de Scrum, i moltes qüestions es poden resoldre des d’aquesta perspectiva.
Pots tenir obert el traductor (per exemple google translate). Tot i que et recordo que no confiïs en “copiar i enganxar” text directament, ja que probablement hauràs de teclejar els enunciats manualment.
Pots tenir oberta la Guia Nexus i la Scrum Guide per aclarir algun petit dubte. Però no perdis molt de temps. Si una pregunta et resulta difícil, pots passar a la següent, i retornar a aquesta al final. El temps de l’examen, amb un coneixement mitjà d’anglès no hauria de ser un problema. Si et sobra temps, revisa les preguntes que has trobat més difícils. Pots canviar qualsevol resposta mentre dura l’examen.
Molta sort!!!
Nexus Guide, (https://www.scrum.org/resources/nexus-guide) Pàgina oficial de descàrrega multiidioma, març 2023
Scrum Guide, (https://scrumguides.org/download.html) Pàgina oficial de descàrrega multiidioma, març 2023
Escalar Scrum con Nexus, (https://youssefoufaska.com/escalar-scrum-con-nexus/) youssefoufaska.com, març de 2021
Las 10 claves del escalado de Scrum con Nexus, (https://www.youtube.com/watch?v=PFXXfBWtbAw) Paradigma digital, juliol 2018
Scrum.org. Open assessments, (https://www.scrum.org/open-assessments) Scrum.org, març 2023
Scaled Professional Scrum Sample Questions, (https://www.processexam.com/scrum-org/scrum-org-sps-certification-exam-sample-questions) processexam, març 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, març 2023
Aquestes preguntes d’exemple es poden trobar a diversos repositoris i articles sobre el tema. Aquí només es fa una translació d’algunes d’aquestes preguntes, sense poder assegurar la seva validesa.
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.
Descarrega el document per imprimir aquí
