Herding Cats

AUGUST 27, 2017

There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. Let's look at each one in more detail.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Herding Cats

OCTOBER 1, 2016

For software, this can be value produced (assuming we have a unit of measure for that value in the for of effectiveness, performance, key performance parameters, or technical performance measures ). It can be the cost, schedule, and technical performance measures of the software project.

Closing 28

Closing Estimate Controlling Process 28

ProProfs Project Management

JANUARY 21, 2020

Agile projects usually do not have set or fixed scope, making this method extremely adaptive to changes proposed by clients. . It refers to any prediction or estimation made on a project’s status, including how it will unfold in the future. Performance Measurement Baseline. Assumption. Functional Requirements.

Underperforming Technical Team 111

Underperforming Technical Team Estimate Risk Management Defining 111

Herding Cats

OCTOBER 12, 2018

It's been said by an agile voice that. The original agile author's quote shows that systems engineering is missing from his development of software using Agile. In most of the software development, this notion is missing - hence the quote that What is divided from How. Also, trailing indicator.

Engineering 32

Engineering Performance Measurement Underperforming Technical Team Risk Management 32

Herding Cats

MARCH 5, 2017

The common definition of the Definition of Done in agile software development is (mostly from the Scrum Alliance and other official Scrum sites): A simple list of activities (coding, comments, unit testing, integration, release notes, design documents, etc.) These Measures have Little meaning to the Decision Makers.

Software Review 28

Software Review Technical Review Performance Measurement Estimate 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. The Cone of Uncertainty as a Technical Performance Measure. The Cone of Uncertainty as a Technical Performance Measure.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

AUGUST 14, 2016

For some reason the notion if value is a big mystery in the agile community. Many blogs, tweets, books are spent of speaking about Value as the priority in agile software development. We produce Value at the end of every Sprint Value is the most important aspect of Scrum based development.

Performance Measurement 49

Performance Measurement Engineering Lean Software Developers 49

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

JANUARY 22, 2017

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). This is a closed loop control system for managing the program with a T echnical Performance Measure (TPM).

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

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. There can be cost and schedule performance measures as well.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Herding Cats

AUGUST 19, 2016

Here's two recent ones I've encountered with some Agile and #NoEstimates advocates. Rarely the case in software development, where Little's Law is misused often. The OP claimed Goodhart's Law was the source of most of the problems with software development. No measures of effectiveness. Hofstadter's law.

Performance Measurement 28

Performance Measurement Estimate Software Developers Software Development 28

Herding Cats

JANUARY 17, 2017

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). This is a closed loop control system for managing the program with a T echnical Performance Measure (TPM).

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

MARCH 31, 2017

Each of these processes has Practices that have been shown to be widely applicable in many domains, including Agile development. With the Requirements in place - and these can be a list of Features held in the Product Roadmap and Release Plan for agile, we need to lay out how they will be built. Related articles.

Process 53

Process Engineering Software Developers Software Development 53

Herding Cats

NOVEMBER 14, 2018

AHP was developed in the 1970s by Dr. Thomas Saaty. In our agile software development world, AHP is rarely found. This decision model for software development projects addressed: performance, cost, time, and risk. Mathematically, the value equals performance over cost plus time. And of course.

Technical Review 47

Technical Review 2010 2014 Software Developers 47

Herding Cats

AUGUST 1, 2018

We're writing two chapters in an upcoming Project Management Book, with a working title, The Gower Handbook of Project Performance for Agile, Waterfall and Everything in Between , edited by Mark Phillips. 504, Center for Systems and Software Engineering, University of Southern California, 2012. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

APRIL 4, 2016

INCOSE has a Systems Engineering Journal as well with papers speaking to software development complexities . Guide the Systems Engineering Body of Knowledge - speaks to topics like Product road maps are essential for software intensive systems that have many releases of software and capability upgrades.

Engineering 28

Engineering Software Performance Measurement Finance 28

Herding Cats

MARCH 30, 2019

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. Anything less results in systems not worth having or fail to function or perform. [3],

Software Developers 39

Software Developers Software Development Agile Software 39

Herding Cats

APRIL 16, 2019

Project Performance Management (#PPM). Agile Project Management (#APM). Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Product Development (#ProdDev). Agile Software Development (#ASD). Project Performance Management.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MARCH 11, 2018

IEEE Transactions of Software Engineering, 1 (1984): 4-21. By the way, the pure conjecture that agile enables late changing requirements to not have a significant impact on the cost and schedule of the development project is completely lacking any testable evidence outside of personal anecdotes of agile advocates.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

APRIL 5, 2016

There a popular notions in the agile development world that authors like Hayek and Taleb speak to how software development works. You Can’t Understand Agile Without Understanding Hayek. He was not a program manager of engineered to order software intensive system of systems. Let's look at one example.

Software Developers 28

Software Developers Software Development Software Review Software 28

Herding Cats

MAY 12, 2018

This quote is typically the basis of proposing agile software development over traditional software development. Ranging from embedded flight control systems for winged vehicles to orbiting spacecraft, to Software Intensive System of Systems from industrial, business, and financial systems.

Agile 44

Agile Finance Software Developers Software Development 44

Workamajig

JANUARY 11, 2021

Actual dates are different from planned or estimated dates. Actual Effort: The actual effort spent to complete the activity, as opposed to the planned or estimated effort. Actual Expenditure: The actual expenditure spent to complete the activity, as opposed to the planned or estimated expenditure.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Herding Cats

APRIL 4, 2019

All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

Wrike

NOVEMBER 7, 2018

Agile Project Management. Project Management Software & Tools. 19% say Agile techniques. Agile Project Management. 38% of organizations report using agile frequently. [6]. 75% of highly agile organizations met their goals/business intent, 65% finished on time, and 67% finished within budget. Other – 6%.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

JUNE 7, 2018

So when you hear an agile purest talking about the I in Invest, ask is there is any business process loops, interdependencies between systems compoenents, externalities. 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.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 7, 2018

So when you hear an agile purest talking about the I in Invest, ask is there is any business process loops, interdependencies between systems compoenents, externalities. 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.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28

MPUG

JUNE 1, 2022

Melanie: Jeff is currently the Training and Development Manager for Edwards Performance Solutions. As such, he oversees the production and maintenance of courses on project management, systems engineering, software development, business process improvement, and cyber security. The planning performance domain, right?

PMI 59

PMI Software Review Estimate Risk Management 59