2007 2019 SCRUM Technical Review 
Scrum.org
JUNE 1, 2022
Do your Daily Scrums feel like a pointless ritual where everyone just lists what they’ve done yesterday, and what they do will do today? And does your Sprint Review consist of team members listing their individual accomplishments? In our work with Scrum teams, we’ve been part of teams that had it. Forsyth, 2009 or Brown, 2019)?
Project Pulse Journal
APRIL 15, 2024
Beyond Scrum , several Agile frameworks were developed to address the unique needs and challenges of projects and teams. It encourages continuous delivery and improvement without the fixed iterations of Scrum. Agile methodologies offer a path to mastering these challenges. What Makes Kanban Agile?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
FEBRUARY 25, 2020
When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. You love this!”. Step one - The interview. .
The IIL Blog
JULY 19, 2023
The wage and salary activities for the assigned workers were the responsibility of their functional managers and project managers often had very little input if any in the performance review processes. Team members relied upon their functional managers for encouragement, support, and performance reviews. Pendry et al.,
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
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.
Scrum.org
DECEMBER 23, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”. Technical Debt and Code Smells.
Expert insights. Personalized for you.
222 
Let's personalize your content