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

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. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What Resources will be needed to reach Done?

Transportation 39

Transportation Software Engineering Finance 2011 39

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

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. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What Resources will be needed to reach Done?

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

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

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

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

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 Software Review Governance 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

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

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

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

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." . So how do we get ±10% accuracy?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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

MPUG

JULY 16, 2021

The backlog is the list of prioritized and estimated user stories. And then determine if the proposed change can be accommodated within the fiscal and technical resources of the budget? Performing requirements traceability analysis is an important part of software engineering. Can you afford it?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

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. It’s often considered good practice to involve security specialists early in each project, rather than waiting until most of the time and budget have been used up before they have a chance to perform a review.

Software Review 78

Software Review Software Technical Review Development Team Review 78