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 ? The program management processes should seek to reduce uncertainty in the variable of the project. Steve McConnell.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? What would be the evidence that we could make decisions in the presence of uncertanty without estimating the impacts and outcomes of those decisions? . Start here.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . 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.

2003 46

2003 2014 2015 2011 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. This letter states.

2007 34

2007 2012 2009 2010 34

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

2012 29

2012 2007 2010 2006 29

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. Because of that, we don't separate the thinking processes into a dual-system. This means putting a formal process in place for making that decision. System One - automatic.

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

JULY 28, 2017

A Story About Data, Models of Data, and Decision Making. In this course, we learned about statistics beyond the physics and engineering (systems engineering) needs and how to sort out bad data from good data. This was my starting point for becoming a software engineer rather than a physicist, by the way. .

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

Herding Cats

MAY 19, 2017

It is popular to claim we've never done this before, so how can we possibly estimate the cost and schedule. If it truly hasn't been done before, then the software project is likely to be an inventing new physics project. In that world, we still made estimates of the cost to design, build, and operate the experiment.

Estimate 36

Estimate Governance Government Software Engineering 36

Herding Cats

MAY 11, 2017

I started my career as a Software Engineer , writing Fortran 77 signal processing algorithms to find and track missile launchers in the middle eastern desert. This skill was an extension of the signal processing work I did as a grad student looking for information in the data stream of a particle accelerator.

Software Developers 39

Software Developers Software Development Engineering Software 39

Herding Cats

DECEMBER 8, 2017

I work in a domain where the CoU is baked into the Integrated Program Performance Management (IPPM) processes flowed down from the buyer, in this case, the Federal Government. This can be the confidence in the estimate for any variable. There is NO data needed to use the CoU. Past data is NOT needed to show the CoU is Value.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

Herding Cats

FEBRUARY 9, 2018

Drawing Unsupported Conclusions from Incomplete and Inconclusive Data, it is not only natural but also laudable, to seek evidence that confirms something that we hold to be true. I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." Let's look at what an estimate is.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

Epicflow Blog

MAY 14, 2019

Actually caring about the needs of your sponsor,” says Alberto Pérez Veiga , an IT Engineer at NATO Communications and Information Agency. Learning from historical data is a good way to improve performance. Most organizations build structures and processes designed to prevent project failure. Learn Your Lessons.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. Because of that, we don't separate the thinking processes into a dual-system. This means putting a formal process in place for making that decision. System One - automatic.

Transportation 28

Transportation Software Engineering Finance 2011 28

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. Making these decisions in the presence Uncertainty ?

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

JANUARY 13, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute. Estimates of cost, schedule, technical performance on the left have a lower probability of being precise and accurate than estimates on the right.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 28

Herding Cats

MAY 11, 2019

requires making estimates) ? 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. Making these decisions in the presence Uncertainty

Risk Management 35

Risk Management Risk Technical Review 2002 35

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. In many cases, once the estimates have been made (at proposal or authorization to proceed), recalibrate and reduction the uncertainty of the initial estimates is not always performed.

2010 28

2010 2007 Estimate Aerospace 28

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). Prentice-Hall, 1981. This is due to many reasons.

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). Prentice-Hall, 1981. This is due to many reasons.

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

JUNE 19, 2017

Of late, Cone of Uncertainty has become the mantra of No Estimates advocates claiming that data is needed BEFORE the Cone is of any use. This fallacy comes from a collection of data that did not follow the needed and planned reduction of uncertainty for the cost estimates of a set of software development projects. .

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). The processes is an engineering discipline. Prentice-Hall, 1981.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

PM Basics

APRIL 24, 2018

Software Development Life Cycle is on every job description for a Project Manager. Everyone wants you to know how to develop software applications. Understanding of SDLC can make the whole process more efficient. When I googled “software development life cycle definition” I found different variants. That is true.

Software Developers 67

Software Developers Software Development Software Review Software 67

Scrum.org

AUGUST 18, 2023

VSM acts as a catalyst for continuous refinement, offering insights into existing processes. In the realm of software development, principles of DevOps and a commitment to technical excellence can further enhance the process. It enables teams to grasp the entire process, spotlighting bottlenecks and inefficiencies.

SCRUM 156

SCRUM Software Review Technical Review Software Engineering 156

Scrum.org

FEBRUARY 4, 2022

Perhaps you’ve read many blog posts about how horrible SAFe is, or how useless estimation is, or what the optimal size of a team is. What if you recommend teams to stop estimation altogether and cause financial damage compared to when you wouldn’t have recommended this? You may have the practical experience to support your beliefs.

Agile 182

Agile Software Review Underperforming Technical Team Technical Review 182

Scrum.org

FEBRUARY 3, 2020

Why our brain is not built for software engineering. Knowledge work’ refers to tasks that take place mostly in our minds, like predicting scope, setting up plannings, considering consequences of changes to complex systems, working out test cases and estimating complexity. This will affect all estimates and predictions.

2002 192

2002 SCRUM 2007 2003 192

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

Teamweek

DECEMBER 8, 2023

You can avoid a lot of these issues by including skills assessments in the hiring process. The global economic consequences of this mismatch were estimated to be ~$8 trillion in unrealized GDP for the world economy in 2018. It enhances job satisfaction and retention while also contributing to the overall health of the global economy.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

PM Basics

FEBRUARY 19, 2020

I need accurate estimates. You can guess and make the high-level estimation that has a bullet-proof buffer. But here’s the truth: If you want accurate numbers, you need to do the bottom-up estimate. You estimate activities and tasks. Do you need a senior Android software engineer? Click To Tweet.

Budget 82

Budget Software Review Estimate Risk Management 82

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? Then conjecture that NOT estimating will fix that symptom. Can't go wrong here, except for one critical issue. Not likely.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Wrike

NOVEMBER 21, 2022

We might rely on AI to help us manage customer relationships through chatbots, scan for fraudulent activity in financial systems, or turn documents into data via optical character recognition (OCR). Gartner estimates that a third of organizations are currently applying AI across several business units, a figure that is only set to grow.

Artificial Inteligence 36

Artificial Inteligence Software Review Technical Review 2030 36

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

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. We need to learn how to predict with credible methods.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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

Wrike

APRIL 5, 2021

Software development has changed radically in recent years, so why are our processes still the same? Release management is a modern solution to the unique challenges software engineers and project managers face today. This software project management method covers everything from ideation to release. Stay flexible.

Software Review 41

Software Review Engineering Software Developers Software Development 41

Herding Cats

JANUARY 23, 2019

The infrastructure removal program meant installing a complete wireless umbrella across several 100 square miles of property with full encrypted security while maintaining voice, data, first responder, physical, and cyber control. This also meant developing software systems to support this effort.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

SEPTEMBER 22, 2017

The #NoEstimates Manifesto - Actually restates Best Practice for estimating and making decisions with those estimates. . Deterministic estimates are point estimates and Point estimates without a Variance are of little value in the presence of uncertainty. Data over Intuition. All project work is uncertain.

Estimate 50

Estimate 2017 Governance Government 50