Herding Cats

MAY 11, 2019

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. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. This is a closed loop control system for managing the program with a T echnical Performance Measure (TPM). The notion of the Cone of Uncertainty has been around for awhile. Prentice-Hall, 1981. There can be cost and schedule performance measures as well.

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. Closed Loop Stochastic Adaptive control in the presence of Evolving Uncertainty. This extended post covers. All risk comes from uncertainty.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. This is the basis of Closed Loop Project Control Estimates of the needed reduction of uncertanty, estimates of the possisble reduction of uncertainty, and estimates of the effectiveness of these reduction efforts are the basis of the Close Loop Project Control System.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. The planned value, the upper and lower control limits, the measures of actual values form a Close Loop Control System - a measurement based feedback process to improve the effectiveness and efficiency of the project management processes by [1]. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The planned value, the upper and lower control limits, the measures of actual values form a Close Loop Control System - a measurement based feedback process to improve the effectiveness and efficiency of the project management processes by [1]. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Teamweek

DECEMBER 8, 2023

For instance, an individual having a software engineering degree might not be a great fit for a customer service role. Or, they might have decent design skills but lack other hard skills needed to accomplish projects within budget using the tools your clients require.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Leading Agile

NOVEMBER 29, 2023

And these initiatives are very closely coupled to the idea of organizational design and how we’re going to run the organization on the backside. You need to start having the software engineers that can code the data scientists that can analyze. You’re not just a strategy firm.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Leading Agile

NOVEMBER 29, 2023

And these initiatives are very closely coupled to the idea of organizational design and how we’re going to run the organization on the backside. You need to start having the software engineers that can code the data scientists that can analyze. You’re not just a strategy firm.

Technical Review 62

Technical Review Software Review Engineering Infrastructure 62

Herding Cats

FEBRUARY 23, 2016

This Does Not Scale - If there are software development projects that can be executed without knowing how much it will cost in the end (an open ended spend plan), or projects where the budget is capped (a Not To Exceed Number) and we don't really need to know the upper bound of the features to be delivered, how large can this notion scale?

Estimate 39

Estimate Risk Management Finance Software Developers 39

MPUG

JULY 16, 2021

I think that these are very close and there’s not a whole lot, I think difference between the two because really what you’re doing is you’re monitoring and you’re tracing the requirements. And key requirements sometimes called key performance indicators should be identified and marked as such, and monitored closely.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

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." . Let's start with the obvious.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Teamweek

AUGUST 7, 2023

What’s the problem with recruiting software developers? The demand for software developers far outweighs the available supply, making it a real challenge to find the right candidates. To make matters worse, top-notch software engineers know their worth and often expect handsome salaries.

Technical Review 52

Technical Review CTO Hire Software Review Software Engineering 52

Leading Agile

AUGUST 20, 2018

Two closely related conceptual errors appear to be quite common. First, there’s a tool-centric mentality about software-related work. The same rule of thumb applies to other governance reviews, as well. People choose products before they’ve worked out exactly what they want to do.

Software Review 78

Software Review Software Technical Review Development Team Review 78