Herding Cats

FEBRUARY 23, 2016

IT Governance and Decision Rights - those spending the money rarely of ever have the right to decide how, unless explicitly given that right by those providing the money. Software Engineering is a Verb - I advise my students to listen carefully the moment they decide to take no more mathematics courses.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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 29, 2017

This is called Software Engineering Economics. Related articles. Estimating Processes in Support of Economic Analysis. Architecture -Center ERP Systems in the Manufacturing Domain. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Making Conjectures Without Testable Outcomes.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Herding Cats

AUGUST 27, 2017

After having worked for outsourcing, consultancy and product companies I believe that creating a place where people really trust each other is easier when software engineers and stakeholders are both part of the same organization. This notion shows that governance is not considered a requirement for the business.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

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. I guess when the software is created straight out of the mind of the developer with no thought to the consequences of each decision made during the development.

Software Developers 39

Software Developers Software Development Engineering Software 39

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. Related articles. Estimating Processes in Support of Economic Analysis. So here's the point. No answer, ignore that conjecture.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

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. Related articles. IT Risk Management.

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

MAY 8, 2016

The Fermi estimate, or order estimation is an estimation problem, teaches dimensional analysis, approximation, using a back-of-the-envelope calculation. Governance drives processes in Agile at Scale. Governance can be ignored or even flaunted for small self contained teams. Governance by its definition is about decision rights.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

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

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

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

MPUG

JULY 16, 2021

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. The necessary updates to the impacted business analysis deliverables are made. What decisions could be made?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

Herding Cats

MARCH 9, 2017

My early metrics book, Controlling Software Projects: Management, Measurement, and Estimation (Prentice Hall/Yourdon Press, 1982) , played a role in the way many budding software engineers quantified work and planned their projects. […] The book’s most quoted line is its first sentence: “You can’t control what you can’t measure.”

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

MPUG

OCTOBER 15, 2020

Even the engineers, hardware engineer, software engineer, mechanical engineer. Now you’re thinking, how about mechanical engineer I just said. Agile has been- they are in software industry primarily. Here under Agile analysis and design, I have product roadmap user stories, more of it.

PMI 52

PMI Certification Software Review 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

Herding Cats

JANUARY 13, 2017

Barry Boehm's work in “Software Engineering Economics”. Related articles. Economics of Software Development. Herding Cats: Economics of Software Development. The notion of the Cone of Uncertainty has been around for awhile. Prentice-Hall, 1981. Complex, Complexity, Complicated. Estimating Probabilistic Outcomes?

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 Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1st Flight Article). Software Engineering Economics”.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1st Flight Article). Software Engineering Economics”.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1 st Flight Article). Software Engineering Economics”.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Orange dots are the actual weights from a variety of sources - a Design Model (3D Catia CAD system), a detailed design model, a bench scale model that can be measured, a non-flying prototype, and then the 1st Flight Article). Related articles.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Leading Agile

AUGUST 20, 2018

instrumentation to facilitate analysis and correction of production issues. The build should include style checking, linting, and static code analysis in addition to compiling, linking, and low-level automated checking. The same rule of thumb applies to other governance reviews, as well. automated fraud detection.

Software Review 57

Software Review Software Technical Review Development Team Review 57