2006 Agile Innovation Risk 
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.;
Scrum.org
JUNE 1, 2022
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. The social nature of agile teams. In Agile 2007 (AGILE 2007) (pp.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Digite
AUGUST 14, 2017
Competitiveness in the age of digital disruption requires businesses to achieve agility at scale – not in select projects and portfolios alone, but across functions, across the business. The approaches to achieving enterprise-wide agility are keenly debated. The method wars. So what works best?
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. México, 1 al 3 de Febrero de 2006. De Meyer, C.
Scrum.org
FEBRUARY 22, 2021
You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers. In the attempt to fill Scrum’s product discovery void, product delivery organizations regularly turn to other agile frameworks like lean UX, jobs-to-be-done, lean startup, design thinking, design sprint—just to name a few.
Herding Cats
DECEMBER 16, 2017
Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. While some have publication dates that may seem old, the principles in these books are immutable, even for agile projects. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.
Expert insights. Personalized for you.
78 
Let's personalize your content