Herding Cats

AUGUST 1, 2018

Specific actions to reduce the Episuncertaintiesnaties and Margin to handle the Aleatory uncertainies are part of any good project management process. . Coping with the Cone of Uncertainty: An Empirical Study of the SAIV Process Model,” Da Yang, Barry Boehm, Ye Yang, Qing Wang, and Mingshu Li, ICSP 2007 , LNCS 4470, pp.

2012 29

2012 2007 2010 2006 29

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

Herding Cats

DECEMBER 16, 2017

Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Estimating Software Costs: Bringing Realism to Estimating , Second Edition, Capers Jones, 2007. Software Estimation: Demystifying the Black Art , Steve McConnell, Microsoft Press, 2015. Prentice Hall, 2000. IT Risk Management.

Software Developers 46

Software Developers Software Development Estimate 2006 46

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

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 18, 2017

The requirements documents (in whatever form) are the basis of the process to verify these needed capabilities with customers and internal or external stakeholders and validates these requirement meet to need strategic intent of the work. [2]. 1] Software Engineering Body of Knowledge, [link] . [2] that will be necessary.

2007 31

2007 Software Engineering Engineering Manufacturing 31

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

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. Gano, Atlas Books, 2007. What Are Problem Causes of Software Projects?

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. . 37–48, 2007. 37–48, 2007.

2010 28

2010 2007 Estimate Aerospace 28

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002).

2002 203

2002 SCRUM 2007 2003 203

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. The processes is an engineering discipline. 1] Systems Engineering Measurement Primer, INCOSE. [2]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measure that is modeled in the Cone the variable is the Quantitative basis of a control process that establishes the goal for the performance measure. The processes is an engineering discipline. 1] Systems Engineering Measurement Primer, INCOSE. [2]

Technical Review 28

Technical Review 2005 Estimate Software Review 28

The IIL Blog

JANUARY 24, 2024

ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. LEAN processes emerged in 1991, with the Agile Manifesto launched by a group of software engineers in 2001. As ITSM evolved, so did the ways of delivering Information Technology services.

2001 78

2001 2007 2024 Information Technology 78

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Measures that are modeled in the Cone of Uncertainty are the Quantitative basis of a control process that establishes the goal for the performance measures. The processes is an engineering discipline. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

JUNE 19, 2017

Misinterpretations of the “Cone of Uncertainty” in Florida during the 2004 Hurricane Season, Kenneth Broad, Anthony Leiserowitz, Jessica Weinkle, and Marissa Steketee, American Meteorological Society , May 2007. 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

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

Leading Agile

JUNE 27, 2018

The impression was reinforced strongly when I attempted to bridge the divide by participating in the academic tracks of agile and technical conferences in the 2007-2008 time frame. They weren’t professional software developers, and they were pretty new at the whole process of doing research, as well. ” Yeah.

Software Review 123

Software Review Technical Review Underperforming Technical Team 2007 123

Herding Cats

APRIL 4, 2019

Software Risk Management , Barry W. Strategic Risk Taking: A Framework for Risk Management , FT Press, August 12, 2007. Applied Software Risk Management: A Guide for Software Project Managers , C. Ravindranath Pandian, Auerbach Publications, 2007. Stewart, ACTEX Publications, 2006.

Risk Management 43

Risk Management Risk 2003 2011 43

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

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