Remove 2010 Remove Presentation Remove Software Remove Software Developers
article thumbnail

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

Scrum.org

2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. Many studies have identified high autonomy as an important prerequisite for Agile teams ( Moe, Dingsøyr & Dybå, 2010 ; Donmez & Gudela, 2013 ; Tripp & Armstrong, 2018 ; Melo et. 2010, April). Cardozo et. LePine, J.

Agile 211
article thumbnail

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

Scrum.org

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). The five areas we presented here are not meant to be exhaustive.

2004 233
Insiders

Sign Up for our Newsletter

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

article thumbnail

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

Digite

262 pages, ET to read: 4 hours, Published April 7th, 2010 by Blue Hole Press). 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. David Anderson, who is widely regarded as the Kanban Method pioneer published this book in 2010.

Lean 79
article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Presentations and Briefings. Managment Processes.

2003 54
article thumbnail

Software Cost Accounting

Herding Cats

But in the software development world, the domains of IT, there are two other colors of money. There are two types of software that are developed for a business: 1) internal-use software, and 2) software developed to be sold, leased or marketed (“software to be sold”). CAPEX and OPEX.

article thumbnail

Agile Movers & Shakers (6): The Liberators Christiaan Verwijs & Barry Overeem

Scrum.org

“ Christiaan : A friend of mine started a software company. He sold solutions, I developed them. Barry : Failed software development projects. Barry : Failed software development projects. In 2010 I worked as a project manager for a web agency. Developers, because of the growing crunch-culture.

Agile 99
article thumbnail

Reading List for the Cone of Uncertainty

Herding Cats

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48