Herding Cats

NOVEMBER 3, 2016

I work in a domain where engineered systems are developed for complex software-intensive system of systems. These systems are engineered with a variety of development methods. Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

Scrum.org

FEBRUARY 3, 2020

Software development is (generally speaking) very complex. Using the aforementioned cognitive limitations, I will argue that approaches based on a fully rational analysis (e.g. Why our brain is not built for software engineering. This will affect all estimates and predictions. waterfalls) are very likely to fail.

2002 197

2002 SCRUM 2007 2003 197

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 11, 2018

Economics is a social science concerned chiefly with description and analysis of the production, distribution, and consumption of goods and services. Microeconomics is applicable to the development is software systems. 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

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

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. Signal processing is a domain of software development well suited to the paradigm of engineered systems. Software-intensive systems include: .

Software Developers 39

Software Developers Software Development Engineering Software 39

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. Not a group that likes to get questions, by the way.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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. When I googled “software development life cycle definition” I found different variants. Phases in Software Development. Examples of Software Development Life Cycles.

Software Developers 67

Software Developers Software Development Software Review Software 67

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 4, 2016

Smith Infinitesimal Analysis. When we hear, we can't estimate this because we've never done this before. Or estimating is hard - meaning it's hard for me , and I can't possibly estimate when I don't know how. Decision Analysis and Software Project Management. Software Engineering is a Verb.

Estimate 69

Estimate Software Engineering Engineering Software 69

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

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

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) ? reducible and irreducible ?

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Building software.

Software Review 69

Software Review Software Technical Review Development Team Review 69

Herding Cats

JUNE 12, 2018

Have you done a Root Cause Analysis? Then conjecture that NOT estimating will fix that symptom. Then conjecturing (here) that Not Estimating will somehow fix the problem of when you are DSTOP. The supposed evidence in the presentation, that estimating "does not work" starts with the Chaos Report.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. Aligning Software Investment Decisions with the Markets ," Hakan Erdogmus. "

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

AUGUST 1, 2018

Since there has been some confusion around the CoU in the past, about whether it can be reduced, whether there is credible data showing it is valid or not, whether those claiming it can't be reduced have any Root Cause Analysis as to why it wasn;t reduced, I thought I'd included the references we're using. 37–48, 2007. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

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. Software development is Micro, not Macro.

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

JULY 29, 2017

This is called Software Engineering Economics. Why Guessing is not Estimating and Estimating is not Guessing. Estimating Processes in Support of Economic Analysis. Estimating and Making Decisions in Presence of Uncertainty. Related articles. IT Risk Management.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Scrum.org

MARCH 11, 2020

Finally, the term Development Team seems to limit the role to technical people, for example, software engineers. Too much estimating: The Development Team estimates sub-tasks. Source : Scrum Guide 2017. . One-quarter of the tasks are more than sufficient to not just start with the Sprint, but also start learning.

Development Team Review 219

Development Team Review Underperforming Technical Team Software Review Technical Review 219

Herding Cats

JUNE 12, 2018

Have you done a Root Cause Analysis? If you haven't encountered the notion of Root Cause Analysis, start with the Apollo Root Cause Analysis method. Then conjecture that NOT estimating will fix that symptom. This is simply good process development and business management. Not likely.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Scrum.org

JUNE 13, 2022

The term “Developer” seems to limit the role to technical people, for example, software engineers. There is a moment when the marginal return of an additional refinement effort is zero or probably even negative—think analysis-paralysis. Too much estimating: The Developers even estimate sub-tasks.

Underperforming Technical Team 145

Underperforming Technical Team SCRUM Technical Review Software Review 145

nTask

AUGUST 8, 2019

We did an extensive analysis of various factors that influence waterfall project management. This helped us to simplify how nTask project management software can be used for solving such issues. What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

JULY 28, 2017

This was my starting point for becoming a software engineer rather than a physicist, by the way. . Root Cause Analysis is a powerful tool for finding the cause of an observed symptom. You're bad at estimating - WHY? Estimating Processes in Support of Economic Analysis. So here's the point.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

Herding Cats

DECEMBER 8, 2017

This can be the confidence in the estimate for any variable. But is can be ANY variance for the program, including confidence in the estimates of future performance - cost, schedule, or technical performance. This usually results in a project's actual costs far outrunning the optimistic estimates and creating a large overrun.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. Rarely are software engineers working on science experiments. For software development starts with.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

NOVEMBER 18, 2017

In software this is a HUGE mistake! The requirements process begins with the analysis and elicitation of the objectives and constraints of the organization needed to meet the strategic goals in the form of Capabilities. [1] 1] Software Engineering Body of Knowledge, [link] . [2] This conjecture is a fallacy.

2007 31

2007 Software Engineering Engineering Manufacturing 31

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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. Its purpose?

Software Review 41

Software Review Engineering Software Developers Software Development 41

Teamweek

DECEMBER 8, 2023

The global economic consequences of this mismatch were estimated to be ~$8 trillion in unrealized GDP for the world economy in 2018. For instance, an individual having a software engineering degree might not be a great fit for a customer service role. Here’s an example of talent or skills gap analysis. More than 1.3

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Wrike

NOVEMBER 21, 2022

Gartner estimates that a third of organizations are currently applying AI across several business units, a figure that is only set to grow. customers is because it delivers the best artificial intelligence tools for project and task management, for a fraction of the cost of bespoke software engineering solutions.

Artificial Inteligence 36

Artificial Inteligence Software Review Technical Review 2030 36

Teamweek

OCTOBER 20, 2022

You probably already know—Agile isn’t just for software developers anymore. After all, Agile projects deliver proven value in software projects: Higher profit More meaningful projects and client relationships Greater productivity Clearer communication. They also assign estimates to each task. Buzzword alert. Enhances creativity.

Agile 52

Agile Technical Review SCRUM Executing 52

Herding Cats

MARCH 4, 2017

Let's start with a clear and concise description of the problem of successfully managing projects in the presence of uncertainty: Accurate software cost and schedule estimations are essential for non-trivial software projects. As a software project progresses, more information about the project is known.

2010 28

2010 2007 Estimate Aerospace 28

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. The future is where to cost to develop that software is paid back. Economics of Software Development.

Estimate 28

Estimate Software Engineering Software Developers Software Development 28

Herding Cats

MARCH 9, 2017

DeMacro made this post, which has been picked up by the agile community to mean estimating is a waste. . Implicit in the quote (and indeed in the book’s title) is that control is an important aspect, maybe the most important, of any software project. For example in "Software Engineering: An Idea Whose Time Has Come and Gone?"

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

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

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