Herding Cats

OCTOBER 5, 2018

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48

2012 2007 2011 2010 48

Herding Cats

JUNE 9, 2017

The classic paper “ Software Engineering Economics,” Barry Boehm, IEEE Transactions on Software Engineering , Vol SE-10(1), 1984, pp. For software development, there are many decisions to be made. What Feature to develop next ? Architecture -Center ERP Systems in the Manufacturing Domain.

Software 51

Software Software Engineering Estimate Manufacturing 51

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

2003 38

2003 Software Engineering Manufacturing Engineering 38

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. The Future of Systems-and Software Development. Springer International Publishing, 2016.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 7, 2019

Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points,” Putu Linda Primandari and Sholiq, The Third Information Systems International Conference, Procedia Computer Science, 72, pp. Monte Carlo Schedule Risk Analysis,” Intaver Institute, Inc. 61, September 2004. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

SEPTEMBER 22, 2017

A working paper of the same title " Incremental Commitment Spiral Model (ICSM), " Barry Boehm, Jo Ann Lane, Supannika Koolmanojwong, Richard Turner, CSCI577, Software Engineering, Fall 2017, University of Southern California (my alma mater in Systems Engineering) . Architecture -Center ERP Systems in the Manufacturing Domain.

Estimate 50

Estimate 2017 Governance Government 50

Herding Cats

APRIL 14, 2018

Software development is a Value Creaton activity, but Value cannot be determined unless we know the cost to produce that value and when that value will be available for use by those who of paid for that Value. For software development, those scarce resources are people, time, and money. Microeconomics .

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

APRIL 13, 2018

This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. If you google "Real Options software development" or "real options ICT" you'll find these and many dozens more. Architecture -Center ERP Systems in the Manufacturing Domain.

2008 32

2008 2002 Estimate Software Engineering 32

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Herding Cats

DECEMBER 3, 2017

The planned uncertainty not only needs to decrease over time passing, but this reduction diminishes any impacts of risk on the decision-making processes. Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. 37-48, 2007.

2007 34

2007 2012 2009 2010 34

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Herding Cats

AUGUST 27, 2017

Although I understand measuring productivity could work well for repeatable activities, it's hard to believe it works well for abstract and, ultimately, non-repeatable tasks like software development. We engineers should always keep in mind that software development is usually one part of many others inside the company.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Herding Cats

FEBRUARY 9, 2018

Kahneman is speaking about risk-taking when we put it in the project context. This is the domain of Microeconomics and when applied to software development it is the microeconomics of software development. 2] IEEE Transactions on Software Engineering , SXE-10, Janurary, 1981, pp. Why not you?

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

MPUG

MAY 6, 2021

I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. Are we doing good change and risk management? All projects have risks.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Leading Agile

AUGUST 20, 2018

But there’s a risk that people will get excited about automation and get ahead of themselves. They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Including appropriate tooling in the automated CI process covers most of the remaining risks in this area.

Software Review 78

Software Review Software Technical Review Development Team Review 78