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 likelihood of a failure for example. All estimates have precision and accuracy. First, let's establish a principle. One starting point is the value at risk.

2003 46

2003 2014 2015 2011 46

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

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. Signal processing is a domain of software development well suited to the paradigm of engineered systems. Matlab is one example. Related articles.

Software Developers 39

Software Developers Software Development Engineering Software 39

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. For example in "Software Engineering: An Idea Whose Time Has Come and Gone?" All estimates are evil.

Software Engineering 31

Software Engineering Estimate 2015 Engineering 31

Herding Cats

FEBRUARY 9, 2018

If, for example, a project manager believes a member of his or her team is a fast and effective worker, each time that team member works fast and effectively or is told by a colleague about the work that has been done fast and effectively, the project manager will consider his or her belief to be well-founded.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

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. Related articles.

Process 45

Process Estimate Software Developers Software Development 45

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 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). Below is another example of a Weight reduction attribute that has error bands.

Technical Review 28

Technical Review Software Review Underperforming Technical Team Risk Management 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

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

MPUG

MAY 14, 2021

Fletcher Hearns: And as an example, for resources, you don’t know resources name, you don’t know who’s going to be assigned to the project. I got junior software engineers, software engineers, senior software engineers. Fletcher Hearns: Here’s another fairly good example.

Performance Measurement 59

Performance Measurement Underperforming Technical Team Software Engineering Engineering 59

PM Basics

APRIL 24, 2018

So, I will bring more clarity to this topic and will show examples of SDLC below. When I googled “software development life cycle definition” I found different variants. If you want more details I have a separate article here: 3 Useful Applications Of Project Life Cycle Knowledge. Phases in Software Development.

Software Developers 67

Software Developers Software Development Software Review Software 67

PM Basics

FEBRUARY 19, 2020

Do you want to see a project budget example? We’ll review the project budget example in just a minute. I need accurate estimates. If you don’t understand it yet consider reading suggest articles. Moreover, in the project budget example below, we’ll be using work packages and deliverables to sum up costs.

Budget 82

Budget Software Review Estimate Risk Management 82

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 184

Agile Software Review Underperforming Technical Team Technical Review 184

Scrum.org

FEBRUARY 3, 2020

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). The article discusses possible scientific explanations for the success of a personal productivity approach called “ Getting Things Done ” (GTD; Allen, 2001).

2002 192

2002 SCRUM 2007 2003 192

Scrum.org

JUNE 13, 2022

After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses Scrum Developer anti-patterns, covering all Scrum Events and the Product Backlog artifact. Shall I notify you about articles like this one? Hence you may notice tickets queueing in the code-review-column, for example.

Underperforming Technical Team 138

Underperforming Technical Team SCRUM Technical Review Software Review 138

Scrum.org

MARCH 11, 2020

After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. Do you want to get this article in your inbox? Finally, the term Development Team seems to limit the role to technical people, for example, software engineers.

Development Team Review 212

Development Team Review Underperforming Technical Team Software Review Technical Review 212

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. The supposed evidence in the presentation, that estimating "does not work" starts with the Chaos Report. This is called Doing Stupid Things on Purpose (DSTOP).

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

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. Not likely.

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

nTask

AUGUST 8, 2019

We have gone an extra mile to illustrate various real life use cases and examples where waterfall is implemented, and how one can use nTask to further simplify that process – so on and so forth. What Dr. Royce was describing was a flawed model for software development as he argued for a model with multiple iterations or runs.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

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. The #NoEstimates Finale - Pat Richard wrote the blog I wanted to.

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

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. Fletcher Hearns: I have a couple examples here I’ll walk through.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

MPUG

OCTOBER 15, 2020

For example, last year, they audited a number of books into the ACP certification reference and they removed also a number of books. Even the engineers, hardware engineer, software engineer, mechanical engineer. Now you’re thinking, how about mechanical engineer I just said. A number of tools.

PMI 52

PMI Certification Software Review Technical Review 52

MPUG

JULY 16, 2021

For example, the very first tile here, how the customer explained it. For example, status meetings one to two weeks as opposed to a month because if you wait a month in between status meetings, then there’s a whole lot of water it’s gone under that dam between the meetings. Notice the example again.

Monitoring 52

Monitoring Controlling Underperforming Technical Team 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. People take a tool that can support Specification by Example and the first thing they do is try to write executable scripts. Are stakeholders involved in defining the examples? Automate what?

Software Review 78

Software Review Software Technical Review Development Team Review 78