MPUG

MAY 6, 2021

Please find below a transcription of the audio portion of Fletcher Hearn’s session, Project Performance Measurement – Part 1: Overview Of Project Performance Measurements, being provided by MPUG for the convenience of our members. Kyle: Hello, and welcome to part one of MPUGs Project Performance Measurement course.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

MPUG

MAY 14, 2021

Please find below a transcription of the audio portion of Fletcher Hearn’s session, Project Performance Measurement – Part 2: What to Measure and How to Report, being provided by MPUG for the convenience of our members. Kyle: And welcome to Part 2 of MPUG’s Project Performance Measurement course. Is it Eric?

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

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

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

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . 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. This information comes from the Paul G.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

JUNE 7, 2018

This always takes us back the coupling and cohesion discussion all of us who were Software Engineers in the 1980's . 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. This information comes from the Paul G.

Underperforming Technical Team 28

Underperforming Technical Team SCRUM Software Engineering Risk Management 28