Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. 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." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Increasing the Probability of Success , Dallas MPUG, May 6th, 2009.

2003 54

2003 2011 2008 Performance Measurement 54

Herding Cats

OCTOBER 5, 2018

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 ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.

2012 48

2012 2007 2011 2010 48

Herding Cats

DECEMBER 28, 2017

Estimation is pretentious rationalism, where rationalism does not serve us well (extremistan)(sic) Take only risks you can survive. These estimates can not the ultimate truth since the underlying processes that create the uncertainties (aleatory and epistemic) are stochastic in nature - stationary or nonstationary. The Fallacy.

2009 40

2009 Estimate Software Developers Software Development 40

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. Some feel that the cone does not provide any value for the work they do and does not match the reducing uncertainty in their estimates. This letter states.

2007 34

2007 2012 2009 2010 34

Herding Cats

MAY 10, 2019

requires making estimates) ? 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. 5887, 2009. reducible and irreducible ? Dorofee, et.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

APRIL 4, 2019

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

Risk Management 43

Risk Management Risk 2003 2011 43

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty.

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 15, 2017

I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. the Secretary of Defense shall develop and implement a new acquisition process for information technology systems.

Process 39

Process Agile 2011 Aerospace 39

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. requires making estimates) ? 5887, 2009.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

SEPTEMBER 25, 2018

Of course, all three of these are operating in the presence of uncertainty and therefore require estimates to be made. Estimates of the aleatory and epistemic uncertainties that create risk to the delivered Value need to be handled. All three pieces of information are needed.

2009 34

2009 Artificial Inteligence 2013 2005 34

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). Dallas MPUG , May 6th, 2009.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

OCTOBER 27, 2016

There are two kinds of uncertainty on all projects, no matter the domain, including software development projects. For customers paying for the development of software, these things include - cost, schedule (time cost of money), market timing, and performance of the product to name a few. Quote of the Day.

2009 28

2009 2015 Influencer Performance Measurement 28

Herding Cats

FEBRUARY 23, 2016

The conjecture that we can make decisions in the presence of uncertainty without estimating the impacts of those decisions is without any principles that can be tested beyond personal anecdotes of I know people who spend other peoples money without providing estimates. This list starts with the earliest posts, beginning in 2009. .

Estimate 39

Estimate Risk Management Finance Software Developers 39

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). The BLUE bars are the probabilistic ranges of the current estimate date.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates are needed but are subject to large level of uncertainty.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

OCTOBER 16, 2018

The previous approaches to project performance management and production of the Estimate to Complete and Estimate at Completion make use of past performance. Estimating Models for Program Management," Norman Womer and Jeff Cman, Final Technical Reports, N00014-00-1-0280, Unversity of Mississippi, 2003. Data Mining | DMIN'17.

Aerospace 41

Aerospace Engineering 2012 2014 41

MPUG

NOVEMBER 14, 2019

And please take note that we have resources in here, we have estimated work, we have duration, we have some completed tasks. But what we have here is the estimated at completion, estimated costs work performed, baseline costs work performed, and some graphs that actually dive deeper in the indicators that we have as Earned Value managers.

2013 40

2013 Finance 2007 Software Review 40