Remove 2014 Remove Definition Remove Process Remove Software Developers
article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

Some find the process of creating them “childish” or “a waste of time”. This is also why the Scrum framework includes the Definition of Done. Once that definition is clearly engrained in the minds of its members, there is less need to constantly talk about it, decide about it, and coordinate work to assure it. Edmondson, A.

2004 232
article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

Many studies have shown that stressed developers make more mistakes (Furuyama, Arai & Lio, 1996, Sonnentag et. High-stress environments are also more likely to burn developers out (Sonnentag et. The neurological processes for this are also well-understood. In Achieving Quality in Software (pp. Furuyama, T., Kalota, M.

Insiders

Sign Up for our Newsletter

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

article thumbnail

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

Scrum.org

A working definition of Agile and Stakeholders. 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. I prefer a process-based definition of agility.

Agile 206
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”. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work.

Lean 79
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 Correction fixed the immediate non-conformance. All for the want of a nail.

2014 45
article thumbnail

Risk Management Resources

Herding Cats

“A Taxonomy of Threats for Complex Risk Management,” Centre for Risk Studies, Research Programme of the Cambridge Centre for Risk Studies, University of Cambridge, Judge Business School, June 2014. “A IEEE Transactions on Software Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999.

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.