Gunther Verheyen

DECEMBER 26, 2023

We have three kids (2001, 2003, 2013) of which the two oldest (sons) have a disability ( Duchenne and Down Syndrome ). Money was not what drove my wife and I when I gave up my position as software engineer and aspiring project manager in favor of running a bookshop (1996). Let there be no misunderstanding: money is important.

2001 80

2001 2013 SCRUM 2016 80

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. But the tide is turning and Agile project management is gaining wide acceptance as a valid process for most projects. History of Agile project management. This works much better for most large projects.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Herding Cats

MARCH 11, 2017

This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.

2003 46

2003 2014 2015 2011 46

Binfire

APRIL 7, 2017

But the tide is turning and Agile is gaining wide acceptance as a valid process for many projects. In the late twenty century many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all. History of Agile project management.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Binfire

AUGUST 28, 2019

The 12 rules of Agile project management principles are based on the Agile manifesto published by the Agile working group in February 2001. Please customers through early and continuous software delivery. 3-Deliver working software frequently. 8-Agile processes promote sustainable development.

Agile 60

Agile Technical Review Sustainability Software Review 60

Agilemania

MARCH 3, 2022

It is an empirical process that builds the products in increments. Scrum is based on 3 pillars of empirical process control that are difficult to master for many teams. All aspects of the process affecting the outcome must be visible to those performing the work as well as those receiving the work. Software Engineers .

Certification 52

Certification Lean Development Team Review 2001 52

Herding Cats

OCTOBER 24, 2018

Root Cause is the fundamental initiating cause on a causal chain leading to a failure of a process which results in a recurrence of the problem. Root Cause Analysis is a systematic documented approach to arrive at the true Root Cause of the process problem. What Are Problem Causes of Software Projects? 1/2, 2001, pp.

2014 45

2014 Aerospace 2011 2013 45

Wrike

NOVEMBER 29, 2017

Check out this video (Length: 2:07): The Agile Manifesto of Software Development , written in 2001, brought an innovative mindset to building software. Canadian software engineer Scott Ambler once said, we don’t need repeatable processes, we need repeatable results.

Agile 36

Agile 2001 2014 Cadence 36

Project Pulse Journal

APRIL 15, 2024

Understanding these top five Agile methodologies that are not Scrum Framework: Kanban, Extreme Programming (XP), Lean Software Development, Feature-Driven Development (FDD), and Dynamic Systems Development Method (DSDM) is crucial for any team or individual looking to implement Agile practices effectively.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.

Estimate 64

Estimate 2005 2006 2013 64

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Norton, The Systems Engineering Process Office, MITRE Corporation, 6 June 1999.

Risk Management 35

Risk Management Risk Technical Review 2002 35