Herding Cats

AUGUST 1, 2018

One chapter on the Principles of Risk Management and the second chapter on the Practices of Risk Management. Since reducible and irreducible uncertainties create risk, those uncertainties need to be reduced as the project proceeds for the probability of project success to increase. “The 37–48, 2007.

2012 29

2012 2007 2010 2006 29

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

Planio

JULY 9, 2020

Even software. Comfort knowing you’re always running the latest, most stable version of the software. If you’re looking for a new project management tool, this guide will run you through the basics of what Redmine is, why it’s a great choice for most software development teams, and how you can get it set up and optimized for you!

2006 88

2006 2007 Closing Agile 88

Herding Cats

JULY 24, 2017

Shipping on time, to specifications, and within budget might be meaningless if a competitor is shipping software that has a greater value to the market. It's suggested from observations, the Cone of Uncertainty (CoU) is not a valid model of how uncertainty behaves in software development projects. 37–48, 2007. .

2007 42

2007 2012 2006 2008 42

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 24, 2018

But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. Gano, Atlas Books, 2007. What factors lead to software project failure?”

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 11, 2018

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." Boehm, Barry W.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

JANUARY 22, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

JANUARY 17, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

FEBRUARY 4, 2017

Barry Boehm's work in “Software Engineering Economics”. Aleatory and Epistemic uncertainties, which create the risk to the success of the project. Other uncertainties that create risk include: Unrealistic performance expectation with missing Measures of Effectiveness and Measures of Performance. Prentice-Hall, 1981.

Technical Review 28

Technical Review Estimate 2005 Software Review 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. Risk Management is How Adults Manage Projects - Tim Lister.

2010 28

2010 2007 Estimate Aerospace 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. Uncertainty creates Risk. Risk management requires active reduction of risk. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. Service Integration and Management, aka SIAM, was developed in 2005.

2001 78

2001 2007 2024 Information Technology 78

Rebel’s Guide to PM

SEPTEMBER 26, 2016

The project and portfolio management (PPM) software market is changing. In this article we look at emerging software in the PPM space and discuss how its selection and implementation needs to be done in line with an overarching digital strategy. A tiny snapshot of the analysis that the different software tools went through.

Software Review 150

Software Review Software Technical Review PMI 150

Scrum.org

APRIL 7, 2022

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. Teams generally develop through a number of stages, although scientific models vary in which stages and in what order. So … stable teams or fluid teams? Courtney, H.

Underperforming Technical Team 180

Underperforming Technical Team 2007 2006 2009 180

Herding Cats

APRIL 4, 2019

In a recent exchange in social media, it was clear the notion of risk and the sources of risk, the consequences or risks and managing in the presence of risk was in very unclear, when it was conjectured , we can simply slice the work into small bits and REDUCE risk. . This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43

Epicflow Blog

JANUARY 12, 2021

Portfolio Office Manager (PfM) is an employee who administers projects and programs in a portfolio in terms of risk, benefit, and performance management and reports on the results to the portfolio director and often workes together with a portfolio office analyst. You can guess their main focus of work by their titles.

PMO 82

PMO 2007 Controlling Construction 82

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

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. 61, September 2004.

Estimate 40

Estimate Software Review Software 2012 40

Planio

JULY 22, 2020

Risk Up Front: Managing Projects in a Complex World. If you’re also interested in Agile project management, pair the PMBOK with the PMI’s new Agile Practice Guide or our own Guide on How to Pick the Software Development Process that’s Right For you. Risk Up Front: Managing Projects in a Complex World.

2020 148

2020 Underperforming Technical Team Technical Review Software Review 148

Herding Cats

NOVEMBER 5, 2018

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success. taken from [3]).

Software Review 34

Software Review Technical Review Estimate Software Developers 34

MPUG

OCTOBER 9, 2019

And so this is where agile kind of fits in and isn’t just necessarily only for software development. And remember, agile is kind of born out of the need for technical project management or in many cases, software development. But it is clearly not limited to just software.

Agile 40

Agile Technical Review Lean Underperforming Technical Team 40

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

MPUG

OCTOBER 24, 2019

Can we actually zero in on making sure we get to clarity, and the idea of producing value where we can actually see working software or a working solution, or doing some sort of a progressive elaboration of work and work that goes together. What are my risks? However, the idea is to quickly go, is this good enough?

Agile 40

Agile Technical Review Software Review Underperforming Technical Team 40