Herding Cats

JANUARY 7, 2017

This is the foundation for estimates. Estimates with accuracy and precision values needed to make credible decisions. These estimates are critical to both developers and customers. These estimates are used for generating requests for proposals, contract negotiations, scheduling, monitoring, and control. No Estimates?

Software Developers 40

Software Developers Software Development Software Software Engineering 40

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." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

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. IEEE Transactions on Engineering Management , 57 (4), pp. IN this case Mean Time To Failure.

Performance Measurement 35

Performance Measurement 2017 Technical Review 2008 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. IT Risk Management.

2003 38

2003 Software Engineering Manufacturing Engineering 38

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

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

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 Development Software Developers 45

Herding Cats

FEBRUARY 9, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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. Software engineering economics is about making decisions related to software engineering in a business context. A final Thought . Palacios, Cristina Casado?Lumbreras,

Transportation 39

Transportation Software Engineering Finance 2011 39

MPUG

MAY 14, 2021

Having spent half my life in the commercial space and half in the government space, the questions are always there. And then I came back and started using it in larger government programs. I got junior software engineers, software engineers, senior software engineers. Is it Fletcher?

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Herding Cats

JANUARY 23, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Almost impossible?

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

JULY 28, 2017

This was my starting point for becoming a software engineer rather than a physicist, by the way. . You're bad at estimating - WHY? Estimating Processes in Support of Economic Analysis. Estimating and Making Decisions in Presence of Uncertainty. Why Guessing is not Estimating and Estimating is not Guessing.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

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

Estimate 31

Estimate Software Engineering 2015 Engineering 31

Herding Cats

JUNE 4, 2016

This is used in support of the fallacy that estimates aren't needed to make decisions in the presence of uncertanty. Why Guessing is not Estimating and Estimating is not Guessing. Software Engineering is a Verb. The #NoEstimates advocates love to use a Deming quote. Who's Budget is it Anyway? IT Risk Management.

Software Engineering 28

Software Engineering Performance Measurement Finance Manufacturing 28

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. Architecture -Center ERP Systems in the Manufacturing Domain.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

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 Estimate Software Review Software Engineering 28

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. Software engineering economics is about making decisions related to software engineering in a business context. A final Thought . Palacios, Cristina Casado?Lumbreras,

Transportation 28

Transportation Software Engineering Finance 2011 28

Teamweek

NOVEMBER 9, 2022

Project tracking software helps you: Understand if you’re on track to meet task, milestone, and project deadlines Time tracking Compare estimated vs. actual efforts and costs Adjust plans quickly if you’re not on schedule or within the budget. And almost all such tools are built for software project teams.

Software Review 52

Software Review Software Technical Review Construction 52

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

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . In the presence of uncertainty, estimates is needed to make decisions. There is no way out of this for any non-trivial software development project. This information comes from the Paul G.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

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

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

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . In the presence of uncertainty, estimates is needed to make decisions. There is no way out of this for any non-trivial software development project. This information comes from the Paul G.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

MPUG

MAY 6, 2021

We are a consulting company in the DC Baltimore area that specializes in project and portfolio management for about 80% of our customers in the government space, the other 20 in the commercial space. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Governance Government 52

Teamweek

JULY 12, 2024

ML plays a critical cybersecurity role by identifying potential threats and exploits (weak spots in company software). Engineers can plug those gaps to keep data safe. Both are machine learning models: classification assigns categories, while regression estimates values within a range. Anomaly detection.

Artificial Inteligence 52

Artificial Inteligence 2024 Technical Review Underperforming Technical Team 52

MPUG

OCTOBER 15, 2020

For example, prioritizing the product backlog or refining the product backlog, doing an own value management with respect to the product backlog or estimating, or having the various project accounting principles with respect to product management. Even the engineers, hardware engineer, software engineer, mechanical engineer.

PMI 52

PMI Certification Software Review Technical Review 52

MPUG

JULY 16, 2021

The backlog is the list of prioritized and estimated user stories. Performing requirements traceability analysis is an important part of software engineering. They are generally going to be reviewed as requested by a governing body, for impact on the in process work. And there aren’t any scope holes developed.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

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. Skills mismatches cost organizations billions of dollars worldwide.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

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

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

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. Software Engineering Institute, January 1996.

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. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. The same rule of thumb applies to other governance reviews, as well. The company wanted to automate their dispatching process. Seddon’s company, Vanguard, advised them to wait.

Software Review 78

Software Review Software Technical Review Development Team Review 78