Herding Cats

SEPTEMBER 27, 2017

This of course is a misinformed and sometime intentionally misinformed idea used to cloud the conversation. Agile is certainty more common these days and has moved to Software Intensive System of Systems where I work, but IID has been around a long time. Why Guessing is not Estimating and Estimating is not Guessing.

2003 38

2003 Software Engineering Manufacturing Engineering 38

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. An empirical proof of effectiveness is, of course, a test suite. But there are software systems where testing is necessary but not sufficient. .

Software Developers 39

Software Developers Software Development Engineering Software 39

MPUG

MARCH 9, 2020

As a software engineer; however, I was able to easily understand MSP, and it did not take me long to create a schedule for my project. Try not to think about the dates, duration estimates, or any other task attributes in the beginning. Of course, I have just touched upon basic features in this article. Conclusion.

Defining 128

Defining Software Engineering Engineering Estimate 128

Herding Cats

JULY 28, 2017

As a graduate student (twice in two different fields) we always started the first semester with a design of experiments course. In this course, we learned about statistics beyond the physics and engineering (systems engineering) needs and how to sort out bad data from good data. You're bad at estimating - WHY?

Estimate 37

Estimate Engineering Software Engineering Manufacturing 37

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. And of course, those are biased, filtered are fed back into System One at a later date, creating more bias to the decision-making process in the future. A final Thought . 9, January 2011. [6]

Transportation 39

Transportation Software Engineering Finance 2011 39

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." This, of course, is a fallacy on all levels. The first thing to do is NOT fall for the fallacy that NOT Estimating will fix the behavior of the bad manager. Let's look at what an estimate is.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

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, of course, ignores the need to know how much of that $50M minus the $1M am I willing to loose?

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

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

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. And of course, those are biased, filtered are fed back into System One at a later date, creating more bias to the decision-making process in the future. A final Thought . 9, January 2011. [6]

Transportation 28

Transportation Software Engineering Finance 2011 28

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

Workzone

JANUARY 18, 2023

It’s specifically built for technicl creatives—such as game developers, UX designers and software engineers. Geared towards engineers, Planio has issue tracking, version control, help desk capabilities, wikis and chat capabilities. ProductPlan Feeling stuck when charting a course? Pricing: $6.80-$12.75/month

2023 52

2023 Software Review Lean Estimate 52

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

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

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 BLUE bars are the probabilistic ranges of the current estimate date.

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). The BLUE bars are the probabilistic ranges of the current estimate date.

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

JUNE 19, 2017

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. This is course is NOT the correct use of the Cone. Shrinking The Cone Of Uncertainty With Continuous Assessment For Software Team Dynamics In Design And Development,” Pongtip Aroonvatanaporn,” Ph.D.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

MPUG

MAY 14, 2021

Kyle: And welcome to Part 2 of MPUG’s Project Performance Measurement course. 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.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

Scrum.org

AUGUST 18, 2023

To delve deeper into how Scrum's principles can be amplified with Kanban, offering more metrics and transparency to track improvements and enhance the flow of value, consider our Professional Scrum With Kanban course. Value Stream Mapping (VSM) complements Scrum's emphasis on transparency.

SCRUM 158

SCRUM Software Review Technical Review Software Engineering 158

Scrum.org

FEBRUARY 3, 2020

Why our brain is not built for software engineering. Knowledge work’ refers to tasks that take place mostly in our minds, like predicting scope, setting up plannings, considering consequences of changes to complex systems, working out test cases and estimating complexity. This will affect all estimates and predictions.

2002 199

2002 SCRUM 2007 2003 199

LiquidPlanner

JANUARY 18, 2023

The most successful agile practitioners tend to continuously modify their practices to suit their current context (which of course is also constantly changing). No change in engineering practices. This one applies specifically to software engineering teams.) Software teams can expect to do some things differently.

Fractional VPE 148

Fractional VPE Agile Software Review 2001 148

Planio

DECEMBER 14, 2021

It requires you to properly scope projects , break them down into tasks , estimate time and effort , and know which teammates are best suited and available for each one. You need constant feedback from the people doing the work to understand whether you’re taking on too much work, improperly estimating tasks, or pushing the scope.

Underperforming Technical Team 97

Underperforming Technical Team Software Review Estimate Software Engineering 97

Scrum.org

JUNE 13, 2022

The term “Developer” seems to limit the role to technical people, for example, software engineers. Note: Of course, the Scrum Guide does not mention the ‘work item age.’ Too much estimating: The Developers even estimate sub-tasks. Read more : Estimates Are Useful, Just Ditch the Numbers.).

Underperforming Technical Team 147

Underperforming Technical Team SCRUM Technical Review Software Review 147

Scrum.org

MARCH 11, 2020

Finally, the term Development Team seems to limit the role to technical people, for example, software engineers. Too much estimating: The Development Team estimates sub-tasks. Note: Of course, the Scrum Guide does not mention the ‘work item age.’ That looks like accounting for the sake of accounting to me.

Development Team Review 221

Development Team Review Underperforming Technical Team Software Review Technical Review 221

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

SEPTEMBER 9, 2021

It also helps you to deliver the completed software to the end-user quickly and effectively. You can also perform an improved level of stakeholder management using software project management. Structure of a Software Project Management Team. Frontend Software Developer. Different Software Management Processes.

2021 157

2021 Software Review Software Software Developers 157

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. This, of course, is simply poor process improvement and a fallacy since without the root cause the symptom cannot be fixed and will return. Then conjecturing (here) that Not Estimating will somehow fix the problem of when you are DSTOP. Estimates are data.

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

MARCH 11, 2018

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." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

MPUG

MAY 6, 2021

Kyle: Hello, and welcome to part one of MPUGs Project Performance Measurement course. 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.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

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

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. This, of course, is simply poor process improvement and a fallacy, since without the root cause the symptom cannot be fixed and will return. TO DO in Rally, Remaining Estimate in Jira, and other fields in Team Foundation Server and VersionOne. Estimates are data.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

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

JANUARY 23, 2019

In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun. Rarely are software engineers working on science experiments. maybe a read of the resources of Estimating Agile Software Development may help. Almost impossible?

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

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

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. Then of course, Scrum Masters, Kanban Flow Masters They can also go for this certification.

PMI 52

PMI Certification Software Review Technical Review 52

MPUG

JULY 16, 2021

Of course, there are other aspects to this requirements planning that we talked about in the first presentation. The backlog is the list of prioritized and estimated user stories. And that’s a term used to describe the subtle way that requirements grow in perceptibly during the course of the project.

Monitoring 52

Monitoring Controlling Underperforming Technical Team Technical Review 52

Teamweek

NOVEMBER 9, 2022

Project tracking software helps you: Understand if you’re on track to meet task, milestone, and project deadlines Time tracking Compare estimated vs. actual efforts and costs Adjust plans quickly if you’re not on schedule or within the budget. And almost all such tools are built for software project teams.

Software Review 52

Software Review Software Technical Review Construction 52