Herding Cats

AUGUST 27, 2017

There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. Let's look at each one in more detail.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Herding Cats

MARCH 23, 2017

In the estimating business, like many things in project management, there is confusion about principles, practices, and processes. A good estimation approach should provide estimates that are within 25% of the actual results, 75% of the time. Software Engineering Metrics and Models. Dunsmore and V.Y.

Estimate 32

Estimate Software Engineering Engineering Information Technology 32

Herding Cats

OCTOBER 11, 2018

We can make decisions in the presence of uncertainty without estimating the outcome of that decision on our probability of success. Any criticism of the NO Estimates statement is met with being blocked from the discussion. Any criticism of the NO Estimates statement is met with being blocked from the discussion.

Estimate 38

Estimate Software Engineering Engineering Software Developers 38

Herding Cats

JANUARY 9, 2017

Aleatory uncertainty, which is the naturally occurring yields variances in the underlying processes. Epistemic uncertainty comes from probabilistic processes that can be addressed with handling responses. The idea of risk and its management and handling is a critical success factor for all software development.

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

APRIL 14, 2018

Software development is a Value Creaton activity, but Value cannot be determined unless we know the cost to produce that value and when that value will be available for use by those who of paid for that Value. For software development, those scarce resources are people, time, and money. Microeconomics .

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

NOVEMBER 3, 2016

Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do. There is no discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately. illities are a waste.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

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 ? As more details get developed, the Cone converges to the actual value. Steve McConnell.

2012 48

2012 2007 2011 2010 48

Planio

JUNE 8, 2022

However, their position as a technical leader means they also need to understand common coding languages, app architecture, and QA processes. Technical project managers straddle the line between business and engineering and need to bring the two together in several ways. Estimate the time, effort, and resources for an entire project.

Technical Review 78

Technical Review Software Review Development Team Review Underperforming Technical Team 78

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? An estimate is. It's a fallacy.

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

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. Project Estimation. How do you come up with project estimation in Agile world?

Agile 97

Agile Technical Review Software Review Development Team Review 97

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

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

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

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. But the tide is turning and Agile is gaining wide acceptance as a valid process for many projects.

Agile 100

Agile Technical Review Software Review Development Team Review 100

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) ? De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

SEPTEMBER 27, 2017

"Managing the Development of Large-Scale Software: Concepts and Techniques," Winston Royce, Proceedings, Wescon, August 1970. Iterative Enhancement: A Practical Technique for Software Development," Victor Basil and Albert Turner, IEEE Transactions on Software Engineering , Vol. 4, December 1975.

2003 38

2003 Software Engineering Manufacturing Engineering 38

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 28

Transportation Software Engineering Finance 2011 28

Herding Cats

FEBRUARY 9, 2018

I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." The "bad management" is itself a symptom of untrained, inexperienced, unskilled decision making processes in the presence of uncertainty. . Let's look at what an estimate is.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

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

Epicflow Blog

MAY 14, 2019

Most organizations build structures and processes designed to prevent project failure. However, Muratgali Karimsakov , a Project Engineer at Karachaganak Petroleum, warns that lessons learned must be applied in the right way: “Unfortunately, the lessons learned process in many companies doesn’t work properly.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

DECEMBER 18, 2016

Software developers and the IT managers they work for operating in the future. Many of this practitioners view the future as an esoteric, abstract, impractical realm, But the future is where the value of the software is earned. I didn't know I should be estimating. Economics of Software Development.

Estimate 28

Estimate Software Engineering Software Developers Software Development 28

Workzone

JANUARY 18, 2023

Favro Gamers or rather game developers, you may want to check out Favro. It’s specifically built for technicl creatives—such as game developers, UX designers and software engineers. Their Kanban board stretches horizontally across to help you visualize what’s next in the product development cycle.

2023 52

2023 Software Review Lean Estimate 52

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

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 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

Herding Cats

JUNE 19, 2017

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. 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.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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 160

SCRUM Software Review Technical Review Software Engineering 160

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 194

Agile Software Review Underperforming Technical Team Technical Review 194

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

LiquidPlanner

JANUARY 18, 2023

It turns out that “agile” isn’t really a process. Agile came about in the world of software development precisely because people started to realize that the pace of change had become so fast that it was smarter to embrace that change and find ways to work within it than try to resist. No change in engineering practices.

Fractional VPE 148

Fractional VPE Agile Software Review 2001 148

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Why our brain is not built for software engineering. This will affect all estimates and predictions. Attention is the process of selectively concentrating on one aspect while ignoring other aspects. This will affect all estimates and predictions.

2002 203

2002 SCRUM 2007 2003 203

nTask

SEPTEMBER 9, 2021

When we talk about software project management in a conversation related to the organizational paradigm, it usually comprises of all of the things from software development, documenting the whole process, testing every single element, and delivering the finished product on time. Agile Software Project Management.

2021 157

2021 Software Review Software Software Developers 157

nTask

AUGUST 8, 2019

We have gone an extra mile to illustrate various real life use cases and examples where waterfall is implemented, and how one can use nTask to further simplify that process – so on and so forth. It follows a sequential, linear process which is why it is often described as a “linear-sequential life cycle model”.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97