SCRUM Software Engineering Technical Review Workshop 
Scrum.org
JULY 14, 2021
This post is a non-technical version of an academic paper about Scrum teams that I wrote with Daniel Russo. Daniel is a Professor at the University of Aalborg and is specialized in empirical software engineering. I am an organizational psychologist and Scrum practitioner with a love for survey development and statistics.
Project Pulse Journal
APRIL 15, 2024
Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Beyond Scrum , several Agile frameworks were developed to address the unique needs and challenges of projects and teams. Agile methodologies offer a path to mastering these challenges.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
MARCH 22, 2023
One of the most exciting outcomes of Scrum being adopted by a team is innovation. The following interview is with Marjolein Pilon , a Scrum Master from the Netherlands. But I know you have some practical ideas for how Scrum and Teams can help. What if all Scrum Teams would do that? Broadly that is described as innovation.
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.
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.
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.
Herding Cats
MAY 11, 2019
Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C.
Expert insights. Personalized for you.
241 
Let's personalize your content