The Nexus Integration Team (NIT) is a new role that is essential within the Nexus™ framework. It is a role that is performed by a team of people. As described in the Nexus Guide, “the Nexus Integration Team exists to coordinate, coach, and supervise the application of Nexus and the operation of Scrum so the best outcomes are derived.”
I see four common reasons an agile implementation doesn't get the benefits hoped for. These reasons include a failure to limit risk, long end-to-end delivery lead times, consistent cost-overruns, and no one knows why you do what you do.
Why does the software industry act differently from many other industries where a code of ethics isn't required to act "professionally"? Read more to learn how some of our PSTs think this should change.
In the Professional Scrum Product Owner course, we teach that high performing Product Owners are entrepreneurial. They not only act with the business in mind, they have the authority to make important decisions. What should we do now versus later?
Watch our international panel of Professional Scrum Trainers, as they share ethical challenges they have seen software delivery teams face in the real world and learn about an interesting approach your teams might use to tackle these challenges.
A small software shop within a government organization where multiple Scrum Teams are serving the same cause is building one product that has several sub-systems. Sometimes, those sub-systems need to be integrated.
Organizations who don’t understand why they want to become Agile also often take the wrong path to get there. Agility requires empowering teams and helping them make decisions on their own, learning from their experiences as they go.
I’m currently helping a small software shop within a government organization where multiple Scrum Teams are serving the same cause. They are building one product that has several sub-systems, which sometimes need to be integrated.
ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum. Every Scrum role, rule, and timebox is designed to provide the desired benefits and address predictable recurring problems.
According to the Scrum Guide, the Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.
In this session, Karel Deman, global agile lead at Avanade, and Patricia Kong, who leads the Scrum.org scaling initiative, will describe how Avanade improved their organizational agility. They will also share the successes and challenges Avanade faced in scaling ability across the enterprise to best deliver solutions to their clients using Scrum and agile practices.
The Nexus Sprint Backlog is created during Nexus Sprint Planning. It is a visualization of the work across the Nexus that has dependencies. The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams in a Nexus for a single Sprint. Read more to see what Professional Scrum Trainer Rob Maher and Scrum.org Product Owner for Enterprise Solutions Patricia Kong have to say.
This document provides and overview of the different Scrum.org certification assessments that are available. These Professional Scrum assessments come with the industry recognized Professional Scrum certification for those who pass.