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

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

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

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

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. Closed Loop Stochastic Adaptive control in the presence of Evolving Uncertainty. This extended post covers.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Herding Cats

MAY 10, 2019

requires making estimates) ? This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

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.

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.

Technical Review 28

Technical Review 2005 Estimate Software Review 28

Herding Cats

MAY 11, 2019

requires making estimates) ? Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MARCH 4, 2017

Let's start with a clear and concise description of the problem of successfully managing projects in the presence of uncertainty: Accurate software cost and schedule estimations are essential for non-trivial software projects. As a software project progresses, more information about the project is known.

2010 28

2010 2007 Estimate Aerospace 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). Economics of Software Development. Estimating Probabilistic Outcomes?

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 28

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. Skills mismatches cost organizations billions of dollars worldwide.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Artificial Inteligence 52

MPUG

MAY 14, 2021

I got junior software engineers, software engineers, senior software engineers. I know I’m going to have a senior software engineer and I want him working on these tasks [inaudible 00:12:15] who that is. ” So, in this case, I see the junior software engineer is costing me $1.50

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

PM Basics

APRIL 24, 2018

Most of them you can close immediately because you have predefined processes and tools. In this case, project planning boils down to identifying project scope, estimates of time and costs, and setting milestones. In the end, you need requirements that software engineers will understand. However, here is what I suggest.

Software Developers 67

Software Developers Software Development Software Review Software 67

Scrum.org

FEBRUARY 4, 2022

Perhaps you’ve read many blog posts about how horrible SAFe is, or how useless estimation is, or what the optimal size of a team is. What if you recommend teams to stop estimation altogether and cause financial damage compared to when you wouldn’t have recommended this? You may have the practical experience to support your beliefs.

Agile 189

Agile Software Review Underperforming Technical Team Technical Review 189

ProjectManager.com

JANUARY 12, 2022

Nowadays, even non-PMP-certified workers are taking on work that closely resembles a traditional projects, and the desire to manage them better is growing every year. What to Expect: Sessions focus on agility, software engineering and lean business. AIPM National Conference.

2022 280

2022 Technical Review PMO Underperforming Technical Team 280

Herding Cats

JUNE 12, 2018

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. We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level. Estimates are data.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

PM Basics

FEBRUARY 19, 2020

I need accurate estimates. You can guess and make the high-level estimation that has a bullet-proof buffer. But here’s the truth: If you want accurate numbers, you need to do the bottom-up estimate. You estimate activities and tasks. Do you need a senior Android software engineer? Click To Tweet.

Budget 82

Budget Software Review Estimate Risk Management 82

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. Then conjecturing (here) that Not Estimating will somehow, through some unstated process of correction or prevention, fix the problem of when you are DSTOP. 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

Teamweek

OCTOBER 20, 2022

Takes place “behind closed doors” and is closely based on original specs. Close to half the projects experience scope creep. 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

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

Herding Cats

APRIL 4, 2019

It just closed the loop 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. But when some statement is made about risk, estimating, performance modeling, or the like - always ask for references. No References?

Risk Management 43

Risk Management Risk 2003 2011 43

MPUG

MAY 6, 2021

I came to my office today because I was having internet issues at home, and so I will ask for your indulgence because our office is actually quite close to a hospital. I actually got my degree in software engineering and moved up into project management like a lot of us did back in the day. By education and training.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

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. There are databases for Function Points .

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Paymo App

JULY 16, 2018

For some project planning tools, set other details such as workflow, billing method, hours estimate, and more. For instance, if you don’t have a technical background, reach out to your software engineers. Estimate costs. When it comes to estimation, you can’t really use project planning software accurately.

Software Review 52

Software Review Planning Software Technical Review 52

MPUG

JULY 16, 2021

I think that these are very close and there’s not a whole lot, I think difference between the two because really what you’re doing is you’re monitoring and you’re tracing the requirements. And key requirements sometimes called key performance indicators should be identified and marked as such, and monitored closely.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

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

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Two closely related conceptual errors appear to be quite common. First, there’s a tool-centric mentality about software-related work. The company wanted to automate their dispatching process.

Software Review 78

Software Review Software Technical Review Development Team Review 78