LiquidPlanner

JANUARY 18, 2023

A blog article describing “fake Agile” may be resonating a bit too much for comfort. Agile came about in the world of software development precisely because people started to realize that the pace of change had become so fast that it was smarter to embrace that change and find ways to work within it than try to resist.

Fractional VPE 148

Fractional VPE Agile Software Review 2001 148

Scrum.org

AUGUST 18, 2023

In the realm of software development, principles of DevOps and a commitment to technical excellence can further enhance the process. Originating from lean manufacturing principles, VSM's relevance has expanded, becoming a cornerstone in fields such as software development.

SCRUM 160

SCRUM Software Review Technical Review Software Engineering 160

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. Software-intensive systems include: .

Software Developers 39

Software Developers Software Development Engineering Software 39

Herding Cats

OCTOBER 5, 2018

There is a discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately. In our domain of engineered systems, there is a broad range of problems, complex issues, approaches to solving problems. In all cases, we start our work with.

Estimate 40

Estimate Engineering Software Engineering Software Developers 40

Herding Cats

MARCH 23, 2017

In the estimating business, like many things in project management, there is confusion about principles, practices, and processes. A good estimation approach should provide estimates that are within 25% of the actual results, 75% of the time. Software Engineering Metrics and Models. Dunsmore and V.Y.

Estimate 32

Estimate Software Engineering Engineering Information Technology 32

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

Herding Cats

JANUARY 9, 2017

The idea of risk and its management and handling is a critical success factor for all software development. Peter Drucker (1975) Management (From The Principles of Software Engineering , Chapter 6, Tom Glib, 1988). Without these estimates, there is no risk management. Related articles. What is a Team?

Estimate 28

Estimate Risk 2010 Software Engineering 28

Herding Cats

NOVEMBER 3, 2016

Since all risk comes from uncertainty - reducible (Epistemic) and irreducible (Aleatory), estimating is a foundation of all we do. There is no discussion of the conjecture that estimates are a waste, estimates can't be done, estimates are evil, estimates must be stopped immediately. illities are a waste.

Estimate 28

Estimate Software Engineering Engineering Risk Management 28

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 200

2002 SCRUM 2007 2003 200

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 ? As more details get developed, the Cone converges to the actual value. Steve McConnell.

2012 48

2012 2007 2011 2010 48

Herding Cats

MAY 8, 2016

ways to make decisions with No Estimates. Uncertainty of course is present in all software development work both reducible and irreducible uncertainty. can we make a decision in the presence of Uncertainty without making an estimate of the impact or outcome of that decision? An estimate is. It's a fallacy.

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. For software development, there are many decisions to be made. What Feature to develop next ? Related articles. A broader definition is. IT Risk Management.

Software 51

Software Software Engineering Estimate Manufacturing 51

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. All estimates have precision and accuracy. Deciding how much precision and accuracy is needed for a credible estimate is critical to the success of that decision.

2003 46

2003 2014 2015 2011 46

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. Principle #2 - Shorten the Feedback Cycle .

Underperforming Technical Team 40

Underperforming Technical Team Software Engineering Estimate Software Developers 40

Herding Cats

DECEMBER 3, 2017

Seems there is still some confusion (intentional or accidental) about the Cone of Uncertainty and its purpose and its use in software development. Some feel that the cone does not provide any value for the work they do and does not match the reducing uncertainty in their estimates. 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

Herding Cats

SEPTEMBER 27, 2017

"Iterative Enhancement: A Practical Technique for Software Development," Victor Basil and Albert Turner, IEEE Transactions on Software Engineering , Vol. Related articles. Why Guessing is not Estimating and Estimating is not Guessing. 4, December 1975. IT Risk Management.

2003 38

2003 Software Engineering Manufacturing Engineering 38

Herding Cats

APRIL 14, 2018

Software development is a Value Creaton activity, but Value cannot be determined unless we know the cost to produce that value and when that value will be available for use by those who of paid for that Value. For software development, those scarce resources are people, time, and money. Microeconomics .

Process 45

Process Estimate Software Developers Software Development 45

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

SEPTEMBER 22, 2017

The #NoEstimates Manifesto - Actually restates Best Practice for estimating and making decisions with those estimates. . Deterministic estimates are point estimates and Point estimates without a Variance are of little value in the presence of uncertainty. Delivery Time over Development Time.

Estimate 50

Estimate 2017 Governance Government 50

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

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. requires making estimates) ? De Meyer, C.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

JUNE 12, 2018

Then conjecture that NOT estimating will fix that symptom. The notion of waterfall development on slide 9 as actually prohibited in our domain. The notion of waterfall development on slide 9 as actually prohibited in our domain. This is called Doing Stupid Things on Purpose (DSTOP). Not likely. Standish Number.

Underperforming Technical Team 28

Underperforming Technical Team Software Engineering Estimate Development Team Review 28

Binfire

APRIL 7, 2017

The Agile project management methodology has been used in the software development and IT industry for the past sixteen years, but recently it has gained wide acceptance by many number of industries and organizations. In 2001 a group of software engineers and scientists in IT industry got together and wrote Agile Manifesto.

Agile 100

Agile Technical Review Software Review Development Team Review 100

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

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. 40 - Estimation is a Problematic Practice of Companies Doing Dangerous Things. We develop these reference classes using Agile Function Points. Is this normal?

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

nTask

AUGUST 8, 2019

Its simplicity and ease of implementation has made it the most popular version of the systems development life cycle (SDLC) for software engineering and IT projects. Royce, often but mistakenly called the “father of Waterfall”, is accredited with the first formal description of the process in an article he wrote in 1970.

Software Review 97

Software Review 2019 Development Team Review Technical Review 97

Herding Cats

JANUARY 23, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. In all engineering worlds, from software engineering to bending metal for money, there is really nothing new under the sun. For software development starts with.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37

Herding Cats

DECEMBER 18, 2016

Software developers and the IT managers they work for operating in the future. Many of this practitioners view the future as an esoteric, abstract, impractical realm, But the future is where the value of the software is earned. I didn't know I should be estimating. Related articles.

Estimate 28

Estimate Software Engineering Software Developers Software Development 28

Workzone

JANUARY 18, 2023

Favro Gamers or rather game developers, you may want to check out Favro. It’s specifically built for technicl creatives—such as game developers, UX designers and software engineers. Their Kanban board stretches horizontally across to help you visualize what’s next in the product development cycle.

2023 52

2023 Software Review Lean Estimate 52

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

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). Related articles. Economics of Software Development.

Technical Review 28

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

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. Not a group that likes to get questions, by the way.

Estimate 39

Estimate Risk Management Finance Software Developers 39

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