2016 Influencer SCRUM Technical Review 
Scrum.org
NOVEMBER 24, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders. The Scrum Guide seems pretty clear about what Product Owners are accountable for.
Scrum.org
OCTOBER 19, 2022
And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The IIL Blog
NOVEMBER 8, 2023
A recent article in Harvard Business Review described “How AI Will Transform Project Management”. AI and related technologies offer the opportunity to shape-shift the profession. However, the project manager, resource managers, and team members would still be required to review and validate the plan. I say, “Bring it on!”
Scrum.org
MARCH 31, 2020
Many people around the globe are working from home right now, due to the Covid-19 pandemic. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like. Mass actions are influenced by the actions of the masses.
The IIL Blog
AUGUST 2, 2023
Few organizations invest in the change management capabilities required to support new technologies and business processes. We should plan our development to build small, usable components that allow users to regularly review, validate, and provide feedback on the emerging application. However, history demonstrates that change is hard.
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.
International Institute for Learning
FEBRUARY 8, 2023
Documenting and reviewing constraints, assumptions, and risks creates transparency. Tools influence and constrain what we do. A colleague who managed the 10-year effort to update the technology at embassies across the globe had more detailed plans for the upcoming transitions than the later ones.
Expert insights. Personalized for you.
223 
Let's personalize your content