ProjectManager.com

JANUARY 22, 2019

Famously, software engineer and author Tim Lister said that: “Risk management is how adults manage projects.” Plan our work to accommodate risks and contingencies. But in the even less-certain new world of large-scale software development, that was looking increasingly difficult. Employ the assets you deliver.

Underperforming Technical Team 417

Underperforming Technical Team Monitoring Controlling Software Engineering 417

Herding Cats

NOVEMBER 3, 2016

Risk Management is How Adults Manage Projects - Tim Lister. Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do. In our domain of engineered systems there is a broad range of problems, complex issues, approaches to solving problems.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

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

Planio

JUNE 8, 2022

Technical project managers have a unique insight into how products get built that allows them to collaborate better with development teams, identify technical risks or inefficiencies, and make smarter decisions about how new features will work (or not) within your product roadmap. How software systems are architected.

Technical Review 78

Technical Review Software Review Development Team Review Underperforming Technical Team 78

MPUG

FEBRUARY 19, 2024

This data includes emails, text messages, IM conversations, call center logs, customer feedback, user interview transcripts, blogs, videos, product reviews, replies in questionnaires, product requirements, status reports, risk assessments, dependency maps, and the countless meetings we all have throughout the year.

Generative AI 52

Generative AI 2024 Artificial Inteligence Software Review 52

Herding Cats

MARCH 11, 2017

What happens if you shift focus from "accurate estimation" to "reliably shipping by a date"? . If your project has no uncertainty, there is no need to estimate. The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty.

2003 46

2003 2014 2015 2011 46

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 ? 10 Deadly Sins of Software Estimation , Steve McConnell , Construx, 2002. Steve McConnell.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? What would be the evidence that we could make decisions in the presence of uncertanty without estimating the impacts and outcomes of those decisions? . Start here.

Estimate 28

Estimate Underperforming Technical Team Software Governance 28

Herding Cats

JUNE 9, 2017

The classic paper “ Software Engineering Economics,” Barry Boehm, IEEE Transactions on Software Engineering , Vol SE-10(1), 1984, pp. One model that is many times misunderstood by the agile community is the Cone of Uncertainty surrounding estimates as well as the technical and operational aspects of the project.

Software 51

Software Software Engineering Estimate Manufacturing 51

Herding Cats

JANUARY 7, 2017

Because of the limitations of resources, projects need to operate withing a world of limited resources, the uncertainties - both reducible and irreducible - that create risk, and the emerging attributes of all project work. This is the foundation for estimates. These estimates are critical to both developers and customers.

Software Developers 40

Software Developers Software Development Software Software Engineering 40

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. 37–48, 2007.

2012 29

2012 2007 2010 2006 29

Herding Cats

FEBRUARY 11, 2017

The real world is nothing but risk. Conventional approaches to forecasting with empirical data - the supposed No Estimated approach to estimating, hides this fact. Because in forecasting there is no place for uncertainty, which is why No Estimates advocates assert Forecasting is not estimating.

Estimate 28

Estimate Software Engineering Risk Management Engineering 28

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. 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. A final Thought . Kirchler, D.

Transportation 39

Transportation Software Engineering Finance 2011 39

Herding Cats

SEPTEMBER 27, 2017

"Iterative Enhancement: A Practical Technique for Software Development," Victor Basil and Albert Turner, IEEE Transactions on Software Engineering , Vol. Real-Time Software Engineering in Ada: Observations and Guidelines," Mark Borger, Mark, Klein, and Robert Veltre, technical Report, CMU/SEI-89-TR-022 , September 1989. .

2003 38

2003 Software Engineering Manufacturing Engineering 38

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. This letter states.

2007 34

2007 2012 2009 2010 34

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

Epicflow Blog

MAY 14, 2019

Perform Risk Management. Consider introducing risk management measures such as simulations and predictions to be ready for the bottlenecks that might compromise your projects in the future. For effective risk management, it might be reasonable to consider using a project management tool such as Epicflow.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

Herding Cats

MAY 11, 2017

I started my career as a Software Engineer , writing Fortran 77 signal processing algorithms to find and track missile launchers in the middle eastern desert. Software-intensive systems include: . Our daily lives depend on complex software-intensive systems, from banking to communications to transportation to medicine.

Software Developers 39

Software Developers Software Development Engineering Software 39

Herding Cats

JULY 29, 2017

This is called Software Engineering Economics. IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. Estimating Processes in Support of Economic Analysis. Estimating and Making Decisions in Presence of Uncertainty. Related articles.

Cadence 28

Cadence Software Engineering Estimate Manufacturing 28

Herding Cats

APRIL 14, 2018

For software development, those scarce resources are people, time, and money. Software engineering economics is a topic that addresses the elements of software project costs estimation and analysis and project benefit-cost ratio analysis. This is the foundation for estimates. IT Risk Management.

Process 45

Process Estimate Software Developers Software Development 45

Herding Cats

JANUARY 13, 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. Estimates of cost, schedule, technical performance on the left have a lower probability of being precise and accurate than estimates on the right.

Technical Review 28

Technical Review Software Review Estimate Software Engineering 28

Herding Cats

MAY 19, 2017

It is popular to claim we've never done this before, so how can we possibly estimate the cost and schedule. If it truly hasn't been done before, then the software project is likely to be an inventing new physics project. In that world, we still made estimates of the cost to design, build, and operate the experiment.

Estimate 36

Estimate Governance Government Software Engineering 36

Herding Cats

APRIL 13, 2018

Estimation locks down choices early through upfront t decision making, #NoEstimates preserves options. This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. Aligning Software Investment Decisions with the Markets ," Hakan Erdogmus. "

2008 32

2008 2002 Estimate Software Engineering 32

Herding Cats

JUNE 9, 2018

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. 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. A final Thought . Kirchler, D.

Transportation 28

Transportation Software Engineering Finance 2011 28

Herding Cats

MARCH 9, 2017

DeMacro made this post, which has been picked up by the agile community to mean estimating is a waste. . Implying there is no need to measure the project performance and by implication no need to estimate. This is the value at risk discussion. For example in "Software Engineering: An Idea Whose Time Has Come and Gone?"

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

Wrike

JUNE 3, 2015

Workers have to be paid for more time, so your estimated budget goes over. It’s important to accurately predict your timeline — and Jazmin Truesdale does that with excellent risk management: “Projects fail due to underestimated time. ” —Trevor Ewen, Senior Software Engineer, Neosavvy. It was a win-lose.

Technical Review 59

Technical Review Software Review Software Engineering Risk Management 59

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

JULY 28, 2017

This was my starting point for becoming a software engineer rather than a physicist, by the way. . You're bad at estimating - WHY? Estimating Processes in Support of Economic Analysis. Estimating and Making Decisions in Presence of Uncertainty. IT Risk Management. Stop talking and go find out why.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

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). Prentice-Hall, 1981. This is due to many reasons. So the question is? -

Technical Review 28

Technical Review 2005 Estimate Software Review 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). Prentice-Hall, 1981. This is due to many reasons. So the question is? -

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

DECEMBER 8, 2017

This can be the confidence in the estimate for any variable. The CoU is a build-to paradigm, where measures of the program's performance cumulative to date is used to inform the risk for future performance. This usually results in a project's actual costs far outrunning the optimistic estimates and creating a large overrun.

Performance Measurement 35

Performance Measurement Technical Review 2017 2008 35

Herding Cats

DECEMBER 18, 2016

For Reducible Uncertainties - redundancy, experiments, prototyping, fault tolerance, failure safe and a variety of other processes to protect the system when the uncertainty creates a risk or fault. . In the presence of Aleatory and Epistemic uncertanty, risk is created to the cost, schedule, and technical performance of the project.

Estimate 28

Estimate Software Engineering Software Developers Software Development 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

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). Estimates are needed but are subject to large level of uncertainty.

Technical Review 28

Technical Review Estimate 2005 Software Review 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

Binfire

APRIL 7, 2017

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. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto. Project Estimation.

Agile 100

Agile Technical Review Software Review Development Team Review 100

Herding Cats

NOVEMBER 18, 2017

1] Software Engineering Body of Knowledge, [link] . [2] IT Risk Management. Why Guessing is not Estimating and Estimating is not Guessing. . — George Bernard Shaw, Caesar and Cleopatra. [1] 2] " Aligning IT to Organizational Strategy ," . [3] 3] Capability-Based Planning , Chapter 32 TOGAF 9.1, Related articles.

2007 31

2007 Software Engineering Engineering Manufacturing 31