article thumbnail

The Complete History of Agile Software Development

Agilemania

In the early 1990s, PC computing began to rise in organizations, but software development faced a hurdle. At that time, people used to call this crisis the “application delivery lag” or “the application development crisis.” Working software over comprehensive documentation.

article thumbnail

What's Missing from the Agile Software Development Paradigm

Herding Cats

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. Why This Missing Concept is Important to Agile Software Development? . 81-100, 2009. [4]

Insiders

Sign Up for our Newsletter

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

article thumbnail

Real Cross-functional Teams for Creating Real and Better Products

Scrum.org

Besides that, she has published her experience in her books Agile Software Development in the Large, Agile Software Development with Distributed Teams, Retrospectives for Organizational Change, and together with Johanna Rothman Diving for Hidden Treasures: Uncovering the Cost of Delay in your Project Portfolio.

2003 151
article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Ready to transform your approach to project management and software development? Exploring Agile methodologies provides teams with flexible, efficient, and collaborative approaches to software development and project management. Columns include "Reported," "Confirmed," "In Development," "Testing," and "Deployed."

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

Software development is (generally speaking) very complex. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’. A powerful example of the above can be witnessed in termite colonies (Camazine, 2003). This limits our ability to deal with complex problems.

2002 196
article thumbnail

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

Scrum.org

We know from research in teams that even light conflict has a negative effect on team productivity (De Dreu & Weingart, 2003). Analysis of fault generation caused by stress during software development. In Achieving Quality in Software (pp. burnout relationship in software development teams. Furuyama, T.,

2004 227
article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015. Agile Software Development. Earned Value Management.

2003 54