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 143

Lean Agile Sustainability 2001 143

Proofhub

JANUARY 19, 2021

Agile project management Agile methodology started around 2001 and gained popularity fast. Use a project planning software To keep yourself motivated or your team members on the same page, a project planning software is necessary. Why is project management crucial for eCommerce businesses? user/month.

Lean 78

Lean Retail 2001 Budget 78

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 . Software Engineers .

Certification 52

Certification Lean Development Team Review Engineering 52

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. México, 1 al 3 de Febrero de 2006.

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. IEEE Transactions on Software Engineering , Vol. 5887, 2009.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

DECEMBER 4, 2017

These are the starting point for defining project success in our Software Intensive System of Systems (SISoS) domain and are the same measures they can be used in any project domain. Project Succes: A Multidimensional Strategic Concept," Aaron Shenhar, Dov Dvir, Ofer Levy, and Alan Maltz, Long Range Planning , 34, 2001, pp.

2005 37

2005 Performance Measurement Closing Controlling 37

Leading Agile

JANUARY 21, 2021

So it’s like the ability to form teams, the ability to create clear backlogs the ability to get to a working tested increment of software at the end of every sprint. 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?

Sustainability 111

Sustainability Agile SCRUM Technical Review 111

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

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. 14, 2001: pp.

SCRUM 71

SCRUM 2004 Software Review 2019 71

Leading Agile

SEPTEMBER 27, 2023

It’s like how do we run the software factory or the product factory, for lack of a better word, but we distinguish the idea of system of transformation, system of continuous improvement, system of engagement, and it gives us an internal pattern language for really distinguishing things that often get blended. Mike Cottmeyer Okay.

Underperforming Technical Team 69

Underperforming Technical Team Sustainability Governance Government 69

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. Why our brain is not built for software engineering. 2001): Cybernetics and Second Order Cybernetics, in: R.A.

2002 202

2002 SCRUM 2007 2003 202

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. 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.

Underperforming Technical Team 168

Underperforming Technical Team 2007 2006 2009 168

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

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

PM That Works

APRIL 23, 2018

As of 2001 you were writing about it. I was blown away as he was starting to say just before you guys dropped off the call about the way back in 2001 you're writing about the free agent army the global economy and the four waves of product management. I think that was influenced by you as well. 00:24:42;04 - 00:24:49;21 Rick A.

2018 40

2018 Agile Consulting 2002 40

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Velociteach

MAY 10, 2023

Everything from putting people back on the moon, developing new therapeutics and software, or planning a wedding. 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.

Lean 89

Lean Cadence PMI 2001 89

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. Neither are they free from influence.”

Agile 102

Agile Defining 2001 2009 102