senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org YD Scrum.org” The Hone ef Scrum ” Scaled Professional Scrum with Nexus Practices Scrum is a framework from which process evolves. A Scrum Team or organization will build their process by assembling the proper practices that they feel will help them succeed with Scrum at the heart. Nexus (/resources/blog/scaling-scrum) extends Scrum to guide multiple Scrum Teams on how they need to work together to deliver working product in every Sprint. It shows the journey these teams take as they come together, how they share work between teams, and how they manage and minimize dependencies. In the Scaled Professional Scrum with Nexus (/courses/scaled-professional-scrum- nexus-training) course, students learn about many of the practices available to help their teams better scale. The intent of the below chart is to help readers understand those practices and find ways to learn more. * Forming a Nexus - Organizing Teams * Forming a Nexus - Organizing Work * Running a Nexus * Managing a Nexus Forming a Nexus - Organizing Teams Practice Summary Why Use? By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:iwwn scrum arg/scaled-professional-scrum-nexus-practices a7senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Internship Model original team Add new people to a high performance team, then new people move to start their own teams. To help one Ateam team to scaling become high technique that | performing Start with a small team,then grow starts witha | first, then help small team. As | another, then (https:// wwww.scrumorg/resources/how- this team help another nexus-framework-aided-capital-one-scale- grows, the | Avoids the scrum-deliver-complex-product-multiple) team splits | problem of and members | scaling move to start | mediocre newteams, | team performance Ateam scaling technique that Seeonee tha. | Toshare eserves the preserv knowledge across teams and to instill a shared culture across teams when scaling the number of teams. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/websi -terms-service). x hitps:wwn scrum arg/scaled-professional-scrum-nexus-practces 2n7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Ateam formation approach that consists of a To give teams deeper insight into customer needs and to Feature Teams cross- reduce waste (https://www.scrum.org/forum/scrum- functional and wait-time forum/5563/feature-teams-vs-component-_ | team that is by reducing teams) able to pull, hand-offs of deliver, and work to support an people end-to-end outside the feature. team. To improve the An modularity of architectural the code, style that which organizes the | improves its architecture of | maintainability. Microservices (https://stackify.com/what- applications | making it are-microservices/) around a set easier to of narrowly- | change focused, different parts independently | of the code deployable independently services. from other parts. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hips hw serum orgiscaleé-professional-scrum-nexus-practces 3n7senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Ul Drives Feature Areas Ateam formation technique that uses the User Interface to identify areas of high cohesion and low coupling, then form teams around these areas. To reduce cross-team dependencies, based on an assumption that different parts of the UI serve different needs and can be decoupled from other parts. Persona Teams (https://wwwinteraction- design org/literature/article/personas-why- and-how-you-should-use-them) Ateam formation approach where teams form around personas, which are fictionalized abstract descriptions of types of users of the application. To give teams deeper insight into the users ofan application, which can help them feel more connected to the user, which can help them build better solutions. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hips hw serum orgiscaleé-professional-scrum-nexus-practces an7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Feature Set Teams (https://www.scrumorg/resources/common- mistakes-when-scaling-scrum) Ateam formation approach To scale where teams feature teams form around by focusing on customer- a consistent facing customer product areas, | experience in which are also | a domain area. known as value areas. Team Self-Selection (/resources/how-net- health-used-team-self-selection-reorganize- their-scaling-initiative) To increase Ateam the sense of formation team technique . : identification where team and reduce members team conflicts choose which b team they join | °% empowerin: based on their | “MPowerng people to interests, their constraints, and the needs of the team. choose what. they work on and who they work with Forming a Nexus - Organizing Work Practice Summary Why Use By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/websi -terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces x sn7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Aplanning technique that uses a visual map tohelp | To underst communicate | the and connect connectior Impact Mapping thttps:/wwwscrumorg/resources/blog/extending- | PuSIness between P impact-mapping-gain-better-product-insights) goals, and the personas, product ar outcomes, business g impacts, and _| they satisfy Product, Backlog Items (PB) Aplanning technique that helps teams to | To provide decompose _| structured user stories way to refit into PBIs to fles User Story Mapping (/resources/blog/3-key- manageable | out an initic tactics-scrum-teams-connect-customers) chunks of usable ver: work by of a produc visualizing and then user stories additional along two functionali independent dimensions. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces x an7senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org To ensure Aplanning fseeren technique that | 27S 9 of work the helps teams needs to b track business . « done to Track Business-centric items in the Product Backlog | centric items deli eliver when business v. decomposing | the Product | 9 evelopm« Backlog, P marketing, support, et A Refinement technique db at x To improve te ple king | Ne Row of leams worKnS | ork wher together on ‘ multiple Cross-team Refinement (/resources/cross-team- one Product teams are refinement-nexus) Backlog to working reduce or ‘innate together te el . build a sing cross-team Product. Product Backlog Item dependencies. planning technique to | To reduce decompose | problem Create PBls as ‘Thin’ as Possible me where i roduc! are ‘undon (/resources/blog/product-backlog-refinement- u u Backlog Items | at the end explained-23) along with Sprint and their minimize By using this site you are agreeing to the Privacy Policy (/privacy-pat ofan nis of. eslapenden (/website-terms-service). criteria. hitps:wwn scrum org/scaled-professional-scrum-nexus-practces 77senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org ing a Nexus PracticS? Summary Why Use? Astrategy for making the status of, and To communicate Visualize your Work progress on, and reduce (/resources/visualizing-nexus-sprint- Product misunderstanding: backlog) Backlog Items | about the status ot visible and PBIs, therefore transparent. An approach for organizing | To help improve the teams in collaboration Nexus Sprint Planning Room Layout Nexus Sprint | during the Nexus Planning, Spring Planning including event, remote teams. To eliminate the A technique for need to use other using the artifacts to make Nexus Sprint the work Backlog to Use the Nexus Sprint Backlog to Manage transparent by visualize the “ the Flow of Work (/resources/visualizing- visualizing the status of, and nexus-sprint-backlog) sequence and progress on, depend f A lependencies of PBls, during the | °°P , the PBls forecast Sprint for the for the Sprint for Nexus, the Nexus. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces an7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Aset of related techniques that can help to improve the Pr To make running Sprint Review large Sprint at scale by Reviews more Science Fair/Expo letting i effective and (/resources/blog/sprint-review-much- stakeholders engaging betweer more-just-demo) see what they the Development Teams and stakeholders. want/need to see, on demand, during the Nexus Sprint Review. Aset of related techniques that enables teams to better engage with To improve the stakeholders effectiveness of Offline Sprint Review when those Sprint Reviews stakeholders when stakeholder: cannotattend | can't be present. the Sprint Review. either in-person or remotely. Aset of To make sure that techniques for | Sprint making Sprint Retrospectives Retrospective | items don't get items ignored or transparent forgotten Retrospective Board By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces on7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org A validation To obtain product approach for | feedback from evaluating users; to better (/resources/scrum-design-thinking) alternatives understand using a whether the released Product is meeting Product. user needs. Validation To obtain product techniques for feedback from ; gathering users; to better Build Manual Feedback into the Product (/resources/scrum-design-thinking) interest and understand feedback from | whether the a released Product is meeting Product, user needs, A validation approach for To obtain product using feedback from Build Automated Feedback into the Product | instrumentation users; to better (/resources/blog/what-devops-taught- inthe understand me-about-agile) application to | whether the gather Product is meeting information user needs. about usage An approach to scaling Product Ownership by delegating To scale Product Scaled Product Ownership (/forum/scrum- | Some of the Ownership when forum/7820/product-owner-role- work of there's too much delegated-team) Product work for them to Ownership do, and they need while still help. maintaining By using this sit ing tothe Privacy Policy /priseypoteysnd Terms of Service : By using thissite yous aroagrooing Privacy Policy |/privacy-polcy and Terms of Service hitps:wwn scrum org/scaled-professional-scrum-nexus-practces 107senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Adevelopment practice that requires developers to integrate code oI To discover codinc into a shared to and code reposi posttory integration several times a Continuous Integration problems as early day. Each (/resources/blog/devops-cake) as possible, while the code is still fresh in the developer's mind check-in is then verified by an automated build and test process, allowing teams to detect problems early, ‘An approach for using test automation to verify that ty To reduce the leve requirements of manual effort Automated Acceptance Testing are metTo that is required to (/forum/scrum-forum/5391/test-cases- reduce the erify that veri part-staged-deployment-process) level of manual y requirements are effort that is being met. required to verify that requirements are being met By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:iwwn scrum org/scaled-professional-scrum-nexus-practces nTsenor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org GC To enable code to XY Scrum.org” be integrated Tetons oe “” Atechnique | without that enables all | introducing Feature Toggles work to be partially (https://martinfowlercom/articles/feature- | integrated completed work toggles. htmb regardless of by keeping the feature code “turned off* readiness until everything is ready for the feature to be used To improve the release readiness Techniques 9 of a product by that improve , rot Develop for Operations the vine a 3 (/resources/blog/what-devops-taught- deployability 3 e wor necessary to me-about-agile) and deploy and supportability | SCPIOY support a PBI is completed in the same Sprint. of applications To improve the release readiness Tech senniques of a product by . that improve Track Operations / Infrastructure Work in the making sure that the Product Backlog all the work deployability (/resources/blog/what-devops-taught- and necessary to me-about-agile) supportabilty | 42P!ey code related to a PBI is of applications completed in the same Sprint. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces wan7senor 19:33 ‘Scaled Professional Scrum with Nexus Practices | Sorum.org To handle the situation in which not all teams in the Techniques for | Nexus cannot get synchronizing PBIs to “done” at Teams on Differing Cadences the work of the same rate (/forum/scrum-forum/15954/are-sprint- | multiple teams | Especially relevan' length-all-scrum-teams-nexus-same- in a Nexus in mixed duration) when their hardware/softwani Sprint lengths products, and differ. products that require some work to be done on legacy code, Atechnique for forming and supporting ‘oups of or ue th To share Communities of Practice People wi information across . common (/resources/overview-communities- teams; to improve interests, for practice) professionalism the purpose of across teams. sharing learnings and improving skills. A technique that improves | To improve the Track Architecture Work in the Product the resiliency | resiliency and and reduce the | reduce the total Backlog total lifecycle lifecycle cost of cost of applications. applications. By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces 1an7senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org G . A technique for Scrum.org refactoring and | To improve the Facittate Shared’ Architectlre sharing resiliency and (/resources/importance-vertically-slicing- | components reduce the total architecture) across lifecycle cost of applications applications. and teams. A technique to enable multiple Internal Open Source (aka “Inner Source’) | teams to make To move away from teams ownin: components to (https://enwikipediaorg/wiki/Inner_source) | changes to the shared componen same code at ownershi the same time. p Managing a Nexus Practice Summary v Top way Atechnique | visui Product Backlog Treemap for visualizing | size, (https://www.mountaingoatsoftware.com/blog/visualizing- | the sizeand _ of Pl a-large-product-backlog-with-a-treemap) completeness | usec of PBIs. thes the tran: Atechnique | Top for visualizing | way Feature Burndown (/forum/scrum-forum/5616/release- the Don burndown-chart) completeness | Und of work atthe | fora feature level. fora {oo By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service (/website-terms-service). hitps:wwn scrum org/scaled-professional-scrum-nexus-practces “ansenor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Top G ) Scrum.org” light The Hone oF rum YY for tr Atechnique _ self- Health Check for helping chal (https://labs.spotify.com/2014/09/16/squad-health- teams assess _ that check-model/) their own, focu performance. | impr thing help mos A facilitation technique for knowledge sharing in large groups__| Top by breaking way World Café (http://www.theworldcafe.com/key-concepts-_ | them into and resources/design-principles/) smaller sub- | idea groups, based | grou ‘on sub-topics, | envi and rotating people through the groups A facilitation Top technique for way breaking into ller into smal to fe groups to idea Open Spaces (/resources/blog/open-space-and-scrum) discuss and prot fe focus on the« topics of may interest elf inter By using this site you are agreeing to the Privacy Policy (/privacy-policy) and WPHODSEHice | Yer (/website-terms-service). organization hips zw. scrum orgiscales-professional-scrum-nexus-pactices 1617senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Sorum.org Top to si Atechnique | prot for restoring | arisit order toa havi Nexus that is | pool strugglin unn De-scaling (/resources/blog/nail-it-you-scale-it) ‘sgiing with scaling espe problems by _ situz reducing the | whic number of nur teams. peo] have dest Tod itue Atechnique whic equivalent of Next “pulling the bec andon cord’ Scrumble inca stopping work (https//kenschwaberwordpress.com/2016/09/28/scaling- | 4 acca doin and descalin the-nexus-and-scrumbling/) 3 worl until stability worl can be to} si restored to ° ani the Nexus. can (if pc By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service X (/website-terms-service). https: Jimwwscrum.orgiscaled-professional-scrum-nexus-practices ag 87senor 19:33, ‘Scaled Professional Scrum with Nexus Practices | Scrum, og To ir GC ) Scrum.org" An approach | incre Th owe FS W ‘ for improving | tean cohesiveness | colle and building byb Distributed Teams Travel (/resources/blog/emerging- stronger pers practices-cheerlead-your-distributed-teams-good-great) | working relat relationships | and with shar distributed | acro teams, distr tean Ton A technique ., distr for using colle technology to mon Distributed Tooling (/resources/distributed-agile-teams-8- | improve the | 1 rol hacks-make-them-work) ability for app! distributed a of di teams to work | colle together. tech © 2022 Scrumorg, All Rights Reserved. Contact (/about/contact-us) Privacy (/privacy-policy) Terms of Service (/website-terms-service) TM and © Guidelines (/scrumorg-trademarks-and-copyrights) W (https:/twittercom/Scrumdotorg) —f thttp:/facebookcom/scrumorg) in (https:/wrwlinkedin.com/company/scrum-org) _ d& (https://wwnwyoutube.com/user/Scrumorg) By using this site you are agreeing to the Privacy Policy (/privacy-policy) and Terms of Service x (/website-terms-service). hs: scum orale proessiona-scrun-neus an