article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The book “The Enterprise and Scrum” by Ken Schwaber (2007).

2010 231
article thumbnail

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

Scrum.org

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. Hoda & Noble (2017) identified learning processes as essential for teams to become Agile. Journal of systems and software , 81 (6), 961–971.

Agile 208
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 Science On Sustainable Pace, Stress, And Motivation

Scrum.org

This increases blood pressure, heart rate, and tenses muscles (McEwen, 2017). al, 2013), healthcare professionals (Papathanasiou et. 2013), and in the workplace (Manganelli, Thibault-Landry & Forest, 2018). Analysis of fault generation caused by stress during software development. Source: Wikipedia. . Furuyama, T.,

article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141
article thumbnail

Agile. Creativity. Innovation.

International Institute for Learning

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). July 2013). ” Software Development 9(8): 28-32. By Luigi Morsa.

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. A recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project. Now To Risk Management.

article thumbnail

Software Estimating Resources

Herding Cats

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. COSMIC Software Estimation Approach,” Alain Abran, ICEAA Workshop, Portland Oregon, June 6?9,