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

JUNE 9, 2017

The classic paper “ Software Engineering Economics,” Barry Boehm, IEEE Transactions on Software Engineering , Vol SE-10(1), 1984, pp. One model that is many times misunderstood by the agile community is the Cone of Uncertainty surrounding estimates as well as the technical and operational aspects of the project.

Software 51

Software Software Engineering Estimate Manufacturing 51

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. Risk Analysis and Management,” Lester B.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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. Risk Analysis and Management,” Lester B.

Risk Management 35

Risk Management Risk Technical Review 2002 35

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.

2012 29

2012 2007 2010 2006 29

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

Herding Cats

APRIL 14, 2018

For software development, those scarce resources are people, time, and money. Software engineering economics is a topic that addresses the elements of software project costs estimation and analysis and project benefit-cost ratio analysis. This is the foundation for estimates. Related articles.

Process 45

Process Estimate Software Developers Software Development 45

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

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. Software-intensive systems include: . Our daily lives depend on complex software-intensive systems, from banking to communications to transportation to medicine.

Software Developers 39

Software Developers Software Development Engineering Software 39

Herding Cats

NOVEMBER 18, 2017

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] Why Guessing is not Estimating and Estimating is not Guessing.

2007 31

2007 Software Engineering Engineering Manufacturing 31

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

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

To assess the impact of that risk, devise the protective actions needed to address the resulting risk - ESTIMATING is required. Without estimates the Aleatory and Epistemic uncertanty that exists on All project will go unaddressed and the probablity of project sucess will be significanlty reduced, perhaps to Zero. . Related articles.

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. . Implying there is no need to measure the project performance and by implication no need to estimate. For example in "Software Engineering: An Idea Whose Time Has Come and Gone?" All estimates are evil.

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

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

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

PM Basics

APRIL 24, 2018

In this case, project planning boils down to identifying project scope, estimates of time and costs, and setting milestones. Document Analysis. In the end, you need requirements that software engineers will understand. You may want to incorporate high-level feasibility analysis here. Mind Mapping. Wireframes.

Software Developers 67

Software Developers Software Development Software Review Software 67

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). Economics of Software Development. Estimating Probabilistic Outcomes?

Technical Review 28

Technical Review Software Review Underperforming Technical Team 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 205

2002 SCRUM 2007 2003 205

Scrum.org

AUGUST 18, 2023

Additionally, if you're intrigued by the application of VSM in software engineering, check out the article " The value of value stream mapping in software engineering ". While this first analysis, based on the team's understanding and estimates, gave a broad overview, we needed empirical data for a more accurate picture.

SCRUM 163

SCRUM Software Review Technical Review Software Engineering 163

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

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

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 153

Underperforming Technical Team SCRUM Technical Review Software Review 153

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. 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 Developers 34

Software Developers Software Development Risk Management Risk 34

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

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

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 227

Development Team Review Underperforming Technical Team Software Review Technical Review 227

Herding Cats

APRIL 4, 2019

But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. Probabilistic Risk Analysis: Foundations and Methods , Tim Bedford and Roger Cooke, Cambridge University Press, 2009. Risk Analysis in Theory and Practice , Jean?Paul No References? All these books are in print.

Risk Management 43

Risk Management Risk 2003 2011 43

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. TO DO in Rally, Remaining Estimate in Jira, and other fields in Team Foundation Server and VersionOne.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

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. Benington gave a presentation about the development of software for SAGE at Symposium on advanced programming methods for digital computers.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. When I left for the airport this morning to catch my flight to a customer site I estimated, given the conditions, how much time I need to get to my favorite parking spot at DIA. So when you hear we can't estimate you'll know better.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

JANUARY 23, 2019

In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun. Rarely are software engineers working on science experiments. maybe a read of the resources of Estimating Agile Software Development may help. Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

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