Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

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? Lehtinen and Mika V.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 4, 2017

The uncertainty is always there, it doesn't go away with specific actions in specific domains, or with the use of any tools, processes, or practices. If they are not reducing, then the project is headed for trouble, the and management processes of the project has failed to performance its job. . The COCOMO 2.0 37–48, 2007.

2010 28

2010 2007 Estimate Aerospace 28

Scrum.org

FEBRUARY 3, 2020

Why our brain is not built for software engineering. Attention is the process of selectively concentrating on one aspect while ignoring other aspects. It is a mental process and a limited mental resource (Ashcraft, 2002). Together, these three considerations accommodate a process called self-organization.

2002 192

2002 SCRUM 2007 2003 192

Herding Cats

JUNE 19, 2017

“Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development,” Pongtip Aroonvatanaporn,” Ph.D. Thesis, University of Southern California, August 2012. This Closed Loop Program Control Process provides the decision makers with actionable information. Prentice-Hall, 1981. .

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

APRIL 4, 2019

Foundations of Risk Management, 2nd Edition, Terje Aven, John Wiley & Sons, 2012. Project Risk Management: Process, Techniques, and Insights , 2nd Edition, Chris Chapman and Stephen Ward, John Wiley & Sons, 2003. Software Engineering Risk Management , Dale Karolak, IEEE Computer Society Press, 1996.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JUNE 12, 2018

Principle #1 - Trust Your Process, or Change Your Process. This is simply good process development and management. What is the Root Cause of the process not being trusted? Or are you taking observations and deciding that the process is broken without finding the actual cause of the undesirable outcomes?

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Leading Agile

JUNE 27, 2018

In 2012, I wrote a blog post entitled “Delivering provably-correct code.” They weren’t professional software developers, and they were pretty new at the whole process of doing research, as well. This is not an isolated case, and most of what passes for research in software engineering is horrible.

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

Herding Cats

JUNE 12, 2018

Principle #1 - Trust Your Process, or Change Your Process. This is simply good process development and business management. What is the Root Cause of the process not being trusted? This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

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

MPUG

MAY 18, 2022

So I just want to let you know that the only drawback, real life drawback, is that they really haven’t updated this since about 2012. Make sure the process works for your team and your team determines what your process is going to be. It is a point system in the process and I think that that’s okay.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

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 2006 2005 2013 64

Teamweek

JANUARY 23, 2020

In their words: This is an event for IT and business leaders and architects, cyber security experts, data scientists, software engineers from businesses of all sizes – including those involved in Cloud, network infrastructure, AI, DevOps, cyber security, data analytics, unified communications and IoT. Manchester, UK.

Technical Review 52

Technical Review 2020 Artificial Inteligence Software Review 52