2006 Innovation Risk SCRUM 
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? In our work with Scrum teams, we’ve been part of teams that had it. So Scrum was doomed from the start. We also explore how these insights create a strong foundation for the Scrum framework.
The IIL Blog
AUGUST 8, 2023
Articles are now appearing addressing burnout specifically in a project management environment [Verma (1996), Haynes and Love (2004), Richmond and Skitmore (2006), Pinto et al., There is risk that burnout can spread to the entire team if not identified and controlled. Journal of Product Innovation Management. Pinto , Jeffrey K.;
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
APRIL 7, 2022
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Kozlowski & Ilgen (2006) describe this reciprocity as “process begets structure, which in turn guides process”. The wish behind fluid teaming risks becoming the father of its thought. This post is my attempt to do this. Bradley et.
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.
Herding Cats
MAY 11, 2019
This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. Risk Management is essential for development and production programs.
Scrum.org
FEBRUARY 22, 2021
Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide.
Herding Cats
DECEMBER 16, 2017
Software Sizing, Estimation, and Risk Management: When Performance is Measured Performance Improves , Daniel Galaorath and Michael Evans , Auerbach, 2006. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006. Agile Project Management: Creating Innovative Products , Jim Highsmith, Addison Wesley, 2004.
Expert insights. Personalized for you.
207 
Let's personalize your content