Scrum.org

SEPTEMBER 9, 2019

So where were you between February the 11th and 13th, 2001? The result of this buzz session was, of course, the Agile ‘Software Development’ Manifesto. Could it be that the authors were influenced by a “lean” gestalt which they saw no reason to explicitly acknowledge? Working software is the primary measure of progress”.

Lean 141

Lean Agile Sustainability 2001 141

Agilemania

MARCH 3, 2022

The Development Team includes professionals like software developers, architects, programmers, analysts, system admins, QA experts, testers, UI designers, etc. It is a non-profit organization founded in 2001. Manifesto for Agile Software Development, four values, and 12 principles, agilemanifesto.org .

Certification 52

Certification Lean Development Team Review Engineering 52

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Recent trends of Risk Management in Software Development: An Analysis,” Raghavi Bhujang and V.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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. 5887, 2009. Risk a Feelings,” George F. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Gunther Verheyen

FEBRUARY 27, 2024

As the earlier excerpt shows, it was this book that introduced the idea of applying the practices described by Takeuchi and Nonaka to software development. The authors explain why the waterfall model doesn’t work for software development, and they offer possible alternatives, among them (what they call) Scrum.

SCRUM 71

SCRUM 2004 Software Review 2019 71

Wrike

SEPTEMBER 2, 2009

The idea of constant dialogue in project management surfaced in 2001 as one of the principles of so-called agile software development and is described in the Agile Manifesto. Now agile methods are used to manage various projects outside of the software development. Today, thanks to the influence of Enterprise 2.0

Agile 42

Agile 2006 2003 2001 42

Scrum.org

FEBRUARY 3, 2020

The article discusses possible scientific explanations for the success of a personal productivity approach called “ Getting Things Done ” (GTD; Allen, 2001). Software development is (generally speaking) very complex. Nevertheless, the motto of software development is often ‘first solve the problem, then write the code’.

2002 190

2002 SCRUM 2007 2003 190

Leading Agile

JANUARY 21, 2021

So again, I’m anchoring not on feature level agility that we often talk about when it comes like agile software development but how do I pivot an organization? So you think about like the signing of the manifesto back in 2001, what was going on during that time is Scrum was at the table, XP was at the table, Leanne was at table.

Sustainability 111

Sustainability Agile SCRUM Technical Review 111

Scrum.org

APRIL 7, 2022

This corresponds with research on autonomous teams, as well as principles of Agile software development. The influence of shared mental models on team process and performance. I would like to emphasize that in my treatment of this subject, I assume that team changes are mostly initiated by the teams themselves. Bowers, J.

Underperforming Technical Team 156

Underperforming Technical Team 2007 2006 2009 156

Planio

JULY 22, 2020

Influence: The Psychology of Persuasion. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Influence: The Psychology of Persuasion. Author: Brett Harned. Published date: 2017.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

APRIL 16, 2019

Agile Software Development (#ASD). Those lessons are directly transferable to the management of software development teams. Parametric Project Monitoring and Control - Earned Value is an approach to Performance measurement for monitoring and controlling the progress of software development projects.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MAY 7, 2019

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. Bool, CrossLink: The Aerospace Corporation, Winter, 2000/2001, pp. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). The Use of Precision of Software Development Effort Estimates to Communicate Uncertainty,” Magne Jørgensen, Software Quality Days.

Estimate 64

Estimate 2006 2005 2013 64

Velociteach

MAY 10, 2023

Lean manufacturing influenced the quality movement, Agile , and DevOps. The Agile Manifesto The Agile Manifesto is a set of 4 value statements and 12 principles created for software. Pioneering software development thought leaders collaborated to create the Manifesto (2001).

Lean 88

Lean Cadence PMI 2001 88

Leading Agile

JUNE 20, 2018

The idea of a self-organizing team has been promoted strongly since the Agile movement started to gain popularity following the publication of the Agile Manifesto in 2001. But ultimately we’ll see how the idea ties back to self-organizing teams in the context of Agile software development.

Agile 103

Agile Defining 2001 2009 103