Herding Cats

MARCH 17, 2019

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Business, Technical, Systems, Risk, and Project Management.

2003 54

2003 2011 2008 Performance Measurement 54

Resource Guru

JUNE 14, 2022

If your organization is struggling to keep projects on track with spreadsheets, emails, and files that seem to vanish right when you need them – you’ll be pleased to know that there’s a huge variety of project scheduling software out there that can put an end to your woes. As with all software, there’s no one-size-fits-all solution.

Software Review 52

Software Review 2022 Software Technical Review 52

The IIL Blog

OCTOBER 17, 2023

engineering, IT, human resources, etc.), Earned Value Management (EVM) A systematic approach to project performance measurement assessing schedule and cost performance. RAID (Risks, Assumptions, Issues, Dependencies) Log A document that tracks and manages project risks, assumptions, issues, and dependencies.

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

Project Pulse Journal

APRIL 25, 2024

Here are three common types of PMOs from across various sectors: Supportive PMO Industry Application - A supportive PMO is common in industries where projects require flexibility and autonomy, such as IT and software development enterprises. Risk Management Another critical role of the PMO is identifying and mitigating risks across projects.

PMO 52

PMO Governance Government 2014 52

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. The customer is accountable for knowing what Done Looks Like (in Unity of measure meaningful to their domain).

Software Developers 39

Software Developers Software Development Agile Software 39

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

JULY 9, 2018

The domain I work in is categorized as Software Intensive System of Systems (SISoS). The development of the software and sometimes the development of the hardware is done in an agile manner, using one of several Agile development methods - SAFe, Scrum for example. Cost, Schedule, and these measures are tightly interconnected.

2001 31

2001 Software Estimate Performance Measurement 31

Herding Cats

JULY 9, 2018

The domain I work in is categorized as Software Intensive System of Systems (SISoS). The development of the software and sometimes the development of the hardware is done in an agile manner, using one of several Agile development methods - SAFe, Scrum for example. Cost, Schedule, and these measures are tightly interconnected.

2001 28

2001 Software Estimate Performance Measurement 28

Herding Cats

APRIL 30, 2019

This approach is guided by the processes for Root Cause Analysis on Software Intensive System of Systems project I've worked. Root Cause Analysis is Risk Management, that asks the question what is the condition or activity that will create a risk to the success of our project? Were there: Measures of Effectiveness.

Software Review 41

Software Review Technical Review Engineering 2018 41

Herding Cats

DECEMBER 8, 2017

It can be the needed performance of a measure - Effectiveness, Performance, Key Performance Parameter, or a Technical Performance Measures. The specifics of the Technical Performance Measures applied to inform Physical Percent Complete and the Cone of Uncertainty around the TPM are shown here.

Performance Measurement 35

Performance Measurement 2017 Technical Review 2008 35

Herding Cats

NOVEMBER 19, 2018

For software projects, Scrum can be used. The only answer to that is a measure of Physical Percent Complete (P%C). P%C starts with defining the Measures of Performance and Technical Performance Measures for each deliverable as a function of time. Risk-Informed Decision Making , NASA/SP-2010-576.

2010 39

2010 Governance Government Performance Measurement 39

Wrike

JUNE 11, 2023

For instance, a software development company that aims to be effective would focus on delivering bug-free software that provides a seamless user experience. Using the previous example, efficiency would require finding ways to speed up the software development process without compromising quality.

Software Review 36

Software Review Technical Review Innovation Performance Measurement 36

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. Uncertainty creates Risk. Risk management requires active reduction of risk.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. 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). The Cone is NOT the result of the project's past performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

OCTOBER 16, 2018

This ignores the principles of predictive analytics, and the direct management actions taken to produce outcomes from those analytical models found everywhere from project management to grocery store management and the model-based systems engineering. In ISO 15288 this is the role of the Risk Management Processes. Which comes first?

Aerospace 41

Aerospace Engineering 2012 2014 41

Herding Cats

AUGUST 14, 2016

Many blogs, tweets, books are spent of speaking about Value as the priority in agile software development. Without units of measure of Value beyond time and money, there can be not basis of comparison between one value based choice and another. They define compliance to performance requirements. They identify technical risk.

Performance Measurement 49

Performance Measurement Engineering Lean Software Developers 49

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. 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 done by active risk management, through probabalistic decision-making.

Technical Review 28

Technical Review Estimate 2005 Software Review 28

Wrike

JULY 29, 2023

By understanding the business’s strengths, weaknesses, opportunities, and threats, businesses can make informed decisions and develop strategies that leverage their strengths and mitigate potential risks. Goals and objectives: These are specific, measurable targets that the organization aims to achieve.

Technical Review 36

Technical Review Planning Underperforming Technical Team Development Team Review 36

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. Let's look at the thesis of Hayek in light of software development and the decisions that must be made when spending other people's money in the presence of uncertainty. IT Risk Management.

Software Developers 28

Software Developers Software Development Software Review Software 28

Herding Cats

JANUARY 14, 2017

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates or any other project attribute (in this post, cost, schedule, and technical performance parameters). A critical success factor for all project work is Risk Management.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. 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). The Cone is NOT the result of the project's past performance.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JUNE 9, 2018

Optimism bias - a cognitive bias that causes a person to believe that they are at a lesser risk of experiencing a negative event compared to others. With these business principles of software development and projects in general, we can ask and answer five principles of project success. A final Thought . Kirchler, D. Andersson, C.

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

DECEMBER 4, 2017

The technical measures are a set of attributes used to provide the supplier (developer) and the acquirer (customer) with insight into the progress of the definition and development of the technical solution, the ongoing assessment of the associated risks and issues, and the likelihood of meeting the critical objectives of the acquirer (customer).

2005 37

2005 Performance Measurement Closing Controlling 37

Herding Cats

JULY 17, 2017

Estimate to Complete (ETC), Estimate at Completion (EAC), Estimated Completion Date (ECD) are the life blood of our software intensive system of systems programs. The management of SISoS is really no different than the management of any other enterprise class software system. Association for the Advancement of Cost Engineering.

Estimate 34

Estimate Logistics Performance Measurement Governance 34

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. One chapter on the Principles of Risk Management and the second chapter on the Practices of Risk Management. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

JUNE 9, 2018

Optimism bias - a cognitive bias that causes a person to believe that they are at a lesser risk of experiencing a negative event compared to others. With these business principles of software development and projects in general, we can ask and answer five principles of project success. A final Thought . Kirchler, D. Andersson, C.

Transportation 28

Transportation Software Engineering Finance 2011 28

Herding Cats

MARCH 4, 2017

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. Abstracted from [3].

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

JUNE 7, 2018

That would mine all the User Stories are standalone pieces of software. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. Traditional risk models cannot model loops. Actual risks contain loops. Actual software process flows contain loops.

Underperforming Technical Team 32

Underperforming Technical Team SCRUM Software Engineering Risk Management 32

Herding Cats

MARCH 31, 2017

With execution underway, managing the risks of the project becomes our focus beyond the engineering work. Two Books in the Spectrum of Software Development. With all this in place - to whatever scale is appropriate for the problem at hand, we need the final pieces. Related articles. We've Been Doing This for 20 Years.

Process 53

Process Engineering Software Developers Software Development 53

Herding Cats

JUNE 4, 2017

No matter the engineering processes used to produce the outcomes from the project. Risk Management is How Adults Manage Projects - Tim Lister. No risk management plan with mitigations, the risks are still there, and we're not managing other people's money like adults. Estimating is part of risk management.

Estimate 39

Estimate Risk Management Risk Engineering 39

Herding Cats

JUNE 4, 2016

Technical Performance Measures. IT Risk Management. Software Engineering is a Verb. Related articles. Assessing Value Produced By Investments. Who's Budget is it Anyway? Architecture -Center ERP Systems in the Manufacturing Domain. Why Guessing is not Estimating and Estimating is not Guessing.

Software Engineering 28

Software Engineering Performance Measurement Finance Manufacturing 28

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. Thus, the common approach to "measure productivity" is to compare the estimates against what, in fact, happened.

Estimate 46

Estimate Software Review Underperforming Technical Team Technical Review 46

Wrike

NOVEMBER 7, 2018

Project Management Software & Tools. More than 90% of organizations perform some type of project postmortem or closeout retrospective. [9]. 64% of organizations say they frequently conduct risk management. [6]. How Project Success is Measured: 20% — Satisfied stakeholders. Managing small, low-risk projects.

2015 60

2015 Technical Review Underperforming Technical Team Software Review 60

Herding Cats

JUNE 7, 2018

That would mine all the User Stories are standalone pieces of software. Risk interaction within systems and subsystems, between functional and physical elements, can also be modeled with DSM. Traditional risk models cannot model loops. Actual risks contain loops. Actual software process flows contain loops.

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. Jeff, a big MPUG welcome back.

PMI 59

PMI Software Review Estimate Risk Management 59

Workamajig

JANUARY 11, 2021

Accept: A response to a project risk where the project manager accepts the risk and takes no action to evade it, i.e. 'accepting' the risk. This is usually in case of risks that are unlikely to occur or minor enough so as to not affect the project's outcome. All work is divided into short bursts called "sprints".

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Epicflow Blog

OCTOBER 8, 2019

is a process of detecting risks related to the time allowances for activities in particular or a project in general, with the width of estimates range indicating a respective level of risk. It contains all the details about the tasks a project team has to perform. . Control Risks . Activity Attributes . Activity List .

Software Review 45

Software Review Project Life Cycle Estimate Technical Review 45