Remove 2011 Remove Case Study Remove Process Remove Software Development
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 215
article thumbnail

Top 10 Lean/ Kanban Books for IT, Software and Knowledge Work!

Digite

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). Personal Kanban: Mapping Work – Navigating Life. By Jim Benson.

Lean 79
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The Complete Guide to Scaling Agile and SAFe for Business Agility

Agilemania

The entire organization had to be in the process, not just a few self-managed teams. . In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. Scaling Agile SAFe success stories.

Agile 98
article thumbnail

Risk Management Resources

Herding Cats

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project Risk Management: A Combined Analytic Hierarchy Process and Decision Tree Approach,” Prasanta Kumar Dey, Cost Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999. 3, March 2002. 255, April 2010.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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. IEEE Transactions on Software Engineering , Vol.

article thumbnail

Without a Root Cause Analysis, No Corrective or Preventive Action is Credible - Part 1

Herding Cats

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. A Case Study in Root Cause Defect Analysis,” Marek Leszak, Dewayne E.

2014 45
article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46