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

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

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.

Process 45

Process Estimate Software Developers Software Development 45

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 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

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 28, 2017

This was my starting point for becoming a software engineer rather than a physicist, by the way. . Root Cause Analysis is a powerful tool for finding the cause of an observed symptom. You're bad at estimating - WHY? Estimating Processes in Support of Economic Analysis. IT Risk Management.

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

Herding Cats

NOVEMBER 18, 2017

The requirements process begins with the analysis and elicitation of the objectives and constraints of the organization needed to meet the strategic goals in the form of Capabilities. [1] 1] Software Engineering Body of Knowledge, [link] . [2] IT Risk Management. George Bernard Shaw, Caesar and Cleopatra. [1]

2007 31

2007 Software Engineering Engineering Manufacturing 31

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

JUNE 19, 2017

Uncertainty creates Risk. Risk management requires active reduction of risk. Of late, Cone of Uncertainty has become the mantra of No Estimates advocates claiming that data is needed BEFORE the Cone is of any use. These topics are connected in a simple manner. All project work is uncertain (probabilistic and statistical).

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

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

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

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

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

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

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

PM Basics

APRIL 24, 2018

In this case, project planning boils down to identifying project scope, estimates of time and costs, and setting milestones. Document Analysis. In the end, you need requirements that software engineers will understand. You may want to incorporate high-level feasibility analysis here. Mind Mapping. Wireframes.

Software Developers 67

Software Developers Software Development Software Review Software 67

Herding Cats

MARCH 11, 2018

Economics is a social science concerned chiefly with description and analysis of the production, distribution, and consumption of goods and services. 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 Developers 34

Software Developers Software Development Risk Management Risk 34

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

Herding Cats

FEBRUARY 23, 2016

The conjecture that we can make decisions in the presence of uncertainty without estimating the impacts of those decisions is without any principles that can be tested beyond personal anecdotes of I know people who spend other peoples money without providing estimates. We need to learn how to predict with credible methods.

Estimate 39

Estimate Risk Management Finance Software Developers 39

Teamweek

DECEMBER 8, 2023

The global economic consequences of this mismatch were estimated to be ~$8 trillion in unrealized GDP for the world economy in 2018. For instance, an individual having a software engineering degree might not be a great fit for a customer service role. Here’s an example of talent or skills gap analysis. More than 1.3

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

Scrum.org

JUNE 13, 2022

The term “Developer” seems to limit the role to technical people, for example, software engineers. Watering this quality level down to meet a—properly arbitrary—deadline imposed on the team puts the team’s success at risk as it introduces undone work and technical debt. So don’t waste your time on that.

Underperforming Technical Team 153

Underperforming Technical Team SCRUM Technical Review Software Review 153

Herding Cats

JUNE 12, 2018

Have you done a Root Cause Analysis? Then conjecture that NOT estimating will fix that symptom. Then conjecturing (here) that Not Estimating will somehow fix the problem of when you are DSTOP. The supposed evidence in the presentation, that estimating "does not work" starts with the Chaos Report.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

MPUG

MAY 6, 2021

I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. Individual contributor team, lead section, lead project manager, program manager, director of engineering. Are we doing good change and risk management? All projects have risks.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

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. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

nTask

AUGUST 8, 2019

We did an extensive analysis of various factors that influence waterfall project management. This helped us to simplify how nTask project management software can be used for solving such issues. Benington gave a presentation about the development of software for SAGE at Symposium on advanced programming methods for digital computers.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

JUNE 12, 2018

Have you done a Root Cause Analysis? If you haven't encountered the notion of Root Cause Analysis, start with the Apollo Root Cause Analysis method. Then conjecture that NOT estimating will fix that symptom. TO DO in Rally, Remaining Estimate in Jira, and other fields in Team Foundation Server and VersionOne.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Wrike

NOVEMBER 21, 2022

Gartner estimates that a third of organizations are currently applying AI across several business units, a figure that is only set to grow. customers is because it delivers the best artificial intelligence tools for project and task management, for a fraction of the cost of bespoke software engineering solutions.

Artificial Inteligence 36

Artificial Inteligence Software Review Technical Review 2030 36

Herding Cats

JANUARY 23, 2019

If you're not an expert, you're not going to recognize the possible solutions, risks, impediments, and opportunities for the problems you'll encounter in developing a solution that has never been developed before. In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

FEBRUARY 9, 2019

40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. A #Noestimates advocate makes the claim that having a ±10% accuracy for estimates of cost and duration is a dangerous thing. Define the probabilistic ranges of the work in a single point estimate manner. What is the Value at Risk for your Project?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

MPUG

JULY 16, 2021

The backlog is the list of prioritized and estimated user stories. Performing requirements traceability analysis is an important part of software engineering. When there’s a requirement with no associated work product, there is a risk that important components might be missed. What decisions could be made?

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

Herding Cats

NOVEMBER 7, 2016

Estimating is a learned skill, used for any purpose from every-day life to management of projects. When I left for the airport this morning to catch my flight to a customer site I estimated, given the conditions, how much time I need to get to my favorite parking spot at DIA. So when you hear we can't estimate you'll know better.

Estimate 64

Estimate 2006 2005 2013 64

MPUG

OCTOBER 15, 2020

For example, prioritizing the product backlog or refining the product backlog, doing an own value management with respect to the product backlog or estimating, or having the various project accounting principles with respect to product management. Even the engineers, hardware engineer, software engineer, mechanical engineer.

PMI 52

PMI Certification Software Review Technical Review 52

Teamweek

OCTOBER 20, 2022

For example, in Waterfall project management, the phases are: Requirement analysis Planning Execution Testing Delivery (or Deployment). When you’re leading an agency providing marketing, web development, branding, or software engineering—your success is defined by creativity. They also assign estimates to each task.

Agile 52

Agile Technical Review SCRUM Executing 52